Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360505

Summary:	Improved handling for various ZooKeeper connection states
Product:	z_Archived	Reporter:	Gunnar Wagenknecht <gunnar>
Component:	gyrex	Assignee:	Gunnar Wagenknecht <gunnar>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	andreas.mihm
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
URL:	http://wiki.eclipse.org/Gyrex/Development_Space/ZooKeeper_Interaction
Whiteboard:
Bug Depends on:
Bug Blocks:	358210, 360809, 360811, 360813

Description Gunnar Wagenknecht

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

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

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.