Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360505 - Improved handling for various ZooKeeper connection states
Summary: Improved handling for various ZooKeeper connection states
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: gyrex (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Gunnar Wagenknecht CLA
QA Contact:
URL: http://wiki.eclipse.org/Gyrex/Develop...
Whiteboard:
Keywords:
Depends on:
Blocks: 358210 360809 360811 360813
  Show dependency tree
 
Reported: 2011-10-11 04:03 EDT by Gunnar Wagenknecht CLA
Modified: 2018-03-19 11:59 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2011-10-11 04:03:28 EDT 
ZooKeeper differentiates between DISCONNECT and SESSION_EXPIRED. Gyrex currently handles both more or less the same. This situation should be improved.

We should handle DISCONNECT state more graceful and allow to recover from DISCONNECT. Only if SESSION_EXPIRED state is triggered we should really "disconnect" the node from the cloud.

We also need to allow cloud roles/listeners to handle the state individually. For example, preferences might want to continue to work. Worker might want to stop processing completely. Web applications might also stop working or continue?
Comment 1 Gunnar Wagenknecht CLA 2011-10-13 16:16:41 EDT 
I started documenting the current implementation as well as a proposed third state for the ZooKeeper gate.
Comment 2 Gunnar Wagenknecht CLA 2011-10-20 12:08:45 EDT 
Considering this one fixed. The new gate and cloud states have been added together with a suite of tests using a true ZK quorum.