SharePoint 2010 internal SharePoint load balancer send traffic to a server offline? and it causes sharepoint end point failuires

When an end point fails, a user will get the “Internal Server Error” exception, and the topology service will mark the end point “bad” for a configurable period of time (BadListPeriod). This time period is 10 minutes by default.

After “BadListPeriod” time has elapsed, the end point that had failed is marked “good” again, and a user may get another “Internal Server Error” exception if the server is still down. At this time, the particular server is taken out of rotation for “BadListPeriod” amount of time.

You can increase the “BadListPeriod” to the number of hours it will take to bring the server back online. This can be done using the following script that has been created and tested :

The above script sets the “BadListPeriod” to 10 hours, which means that after a user gets an error, we will take the endpoint out of rotation for 10 hours.

Set-SPTopologyServiceApplicationProxy ( BadListPeriod ) SharePoint 2010 end point failuires :

To prevent sharepoint from constantly going to a bad server for requests run the following commends

------------------EXAMPLE-----------------------

Set-SPTopologyServiceApplicationProxy 67877d63-bff4-4521-867a-ef4979ba07ce –BadListPeriod 1234

Specifies the time period that a node is kept in a bad list.
The type must be a valid value between 1 and 480 (in minutes).
The default value is 10.

or use script that i created

$proxy = Get-SPTopologyServiceApplicationProxy

$proxy.ExpireFailedEndPointsInterval = [System.TimeSpan]::FromHours(10)

$proxy.Update()

I did some additional testing and found the following two parameters (I’ve provided additional details below):

·        $topoProxy.ExpireFailedEndPointsInterval = [System.TimeSpan]::FromHours(10)

·        $SSA.TimeBeforeAbandoningQueryComponent = 10