« Previous Next »

Thread: ARR v2 RC Monitoring and Management Form Failed Request Stats

Last post 10-29-2009 5:05 PM by JAltrichter. 12 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (13 items)

Sort Posts:

  • 10-14-2009, 11:07 PM

    ARR v2 RC Monitoring and Management Form Failed Request Stats

    I would like to clarify the data for the Failed Requests stat on the Monitoring and Management for Server Farms.  This stat is not currently documented on TechNet (http://technet.microsoft.com/en-us/library/dd443506(WS.10).aspx)

    I am assuming a failed request that is one that is passed to a node in the farm that does not return back to the ARR. I am further guessing the primary reasons would be: node dies, network fails, the operator fails to gracefully take a node offline, etc.

    Jim

  • 10-16-2009, 12:16 AM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Yes, you are right. 404 responses from the node will not be considered as "failed requests".

    CJ Pattekar
    Software Desgin Engg in Test
    IIS Product Unit
    Microsoft
  • 10-16-2009, 10:33 AM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Thanks
  • 10-16-2009, 12:49 PM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,343

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    What is considered failed request would depend on your failure definition - all connection errors will be treated as failed requests and any status codes configured in liveTrafficFailureCodes will be treated as failed requests.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 10-19-2009, 5:56 PM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Anil,

    Can you reference me to where the TrafficFailureCodes reside?  I do not see the the TrafficFailureCodes heading in the server configuration store files in  %Windows%\System32\inetsvr\config. 

    Jim

  • 10-19-2009, 6:35 PM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,343

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Look at %windir%\system32\inetsrv\config\schema\arr_schema.xml for the ARR schema.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 10-21-2009, 12:25 PM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    I found the TrafficFailureCodes reference, it is referencing codes "500-".

    Should I be able to find a 5xx code on the ARR server logs?  I have done some preliminary checking and have not seen any 5xx errors, during times when I know there have been failed requests.

    Jim

  • 10-21-2009, 12:51 PM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    The "failed requests" could be a result of "connection error" as well, like Anil mentioned.

    CJ Pattekar
    Software Desgin Engg in Test
    IIS Product Unit
    Microsoft
  • 10-21-2009, 3:10 PM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Ok, I have found a 500 error one of the content servers on the server farm.

    Can you tell me what happens to the request on the ARR when a content server in a server farm has a failed request?  Does the ARR re-submit the request to another node or does the fail go back the browser?

    Jim

  • 10-22-2009, 2:08 PM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,343

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 10-26-2009, 2:06 PM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Anil,

    Thanks, I have used the ARR freb tracing walkthrough before, and I agree it is very helpful for isolating a specific request. 

    However, the issue in my inquiry was was if ARR automatically retried a failed request to another node on the server farm so that the request failure would not go all the way back to the end user .  Looking at the logs in more detail, I can now see that this is not happening.  Has the ARR team ever considered a retry mechanism?

    Perhaps you could also shed some light on why the HTTP response codes are altered by ARR.  In the example below, a 500 response from a sever farm node was converted to a 400 (bad request) response to the client.

    (NODE) 2009-10-21 22:41:03 IP GET /App/Page.aspx Param1=xxx&X-ARR-LOG-ID=xxx 443 - OriginIP  Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 200 0 0 468
    (ARR ) 2009-10-21 22:41:05 IP GET /App/Page.aspx Param1=xxx&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=xxx 443 - OriginIP Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 200 0 0 1684
    (NODE) 2009-10-21 22:44:26 IP POST /App/Page.asp Param1=xxx&X-ARR-LOG-ID=xxx 443 - OriginIP  Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 500 0 64 128107
    (ARR ) 2009-10-21 22:44:26 IP POST /App/Page.aspx Param1=xxx&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=xxx 443 - OriginIP Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.0) 400 0 64 128108

    Thanks for your feedback.

     Jim

     

     

  • 10-26-2009, 3:34 PM In reply to

    • anilr
    • Top 10 Contributor
    • Joined on 05-23-2006, 10:13 PM
    • Redmond, WA
    • Posts 2,343

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    We have considered retrying the request but never implemented it after feedback from multiple people that they would not want to use it.

    As for the 400 in the ARR logs - if the client disconnects before receiving the complete response, ARR will log it as a 400 to signify that - the win32 status of 64 seems to match up with the client disconnecting before receiving the complete response.

    Anil Ruia
    Senior Software Design Engineer
    IIS Core Server
  • 10-29-2009, 5:05 PM In reply to

    Re: ARR v2 RC Monitoring and Management Form Failed Request Stats

    Thanks Anil.  I believe I understand the reason behind the 400 response now.

Page 1 of 1 (13 items)
Microsoft Communities