Reply
Moderator
joshtseng
Posts: 106
Registered: 04-04-2007
1

Re: Interceptor to steelhead failure timer

wan_optimizer,

 

Multiple keepalive messages are sent by the Interceptor to each Steelhead in the cluster at a frequency of one per second.  It takes three consecutive non-responses from any Steelhead for the Interceptor to declare that Steelhead dead.  So the entire process takes about three seconds before the Interceptor re-directs traffic from a failed Steelhead.

 

Note that keepalives are sent at multiple levels, including one from the kernel, as well as an application-level keepalive.  The kernel-level keepalive detects a dead box, while the application-level keepalive detects a situation where a Steelhead enters a zombie state, where the box is still alive but the sport optimization process is hung.

 

Note that this makes the Interceptor far more responsive than WCCP in its default configuration, where keepalives are sent every 10 seconds, and three consecutive non-responses are needed for WCCP to declare a cache engine dead (so the entire process takes more than 30 seconds).

 

Josh

Fry
wan_optimizer
Posts: 3
Registered: 10-12-2009
0
Accepted Solution

Interceptor to steelhead failure timer

I have a question on Interceptor to steelhead communication. If any steelhead appliance in a cluster fails,how interceptor knows about it and after how much time?Also do we have to put one steelhead appliance as standby in the cluster for failover?

 

Is there any heart beat mechansim like cisco WCCP between Intervceptor and steelhead? My customer is looking for high availability solution and concenred about this timer.

‬‪‬‪‬‪