Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Minor
Fix Version/s: MOD_CLUSTER_1_0_10_GA_CP01, 1.1.3.Final
Affects Version/s: None
Component/s: None
Labels:
None

Steps to Reproduce:

Hide

Ask Bela
start a cluster on EC2 with at least 2 nodes use a sessionid application, kill the node with the JVMRoute corresponding to sessionid... The request will hang for a while until it is failed over to the other node.

Show
Ask Bela start a cluster on EC2 with at least 2 nodes use a sessionid application, kill the node with the JVMRoute corresponding to sessionid... The request will hang for a while until it is failed over to the other node.
Workaround Description:

Hide

Use nodeTimeout

Show
Use nodeTimeout
Estimated Difficulty:
Low

Description

Once stopping the EC2 the socket is closed so the cping doesn't wait for ping but connectiontimeout which default to nodeTimeout and/or server timeout.
That affects only the first request (per process) once the node has been cleaned.

Attachments

Activity

People

Assignee:: Michal Karm

Reporter:: Jean-Frederic Clere

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2011/03/31 4:12 AM

Updated:: 2014/08/08 6:28 AM

Resolved:: 2011/06/09 2:29 AM