Bug 460911 - NodeStates for Service of all nodes are removed from zookeeper when one node goes offline
Summary: NodeStates for Service of all nodes are removed from zookeeper when one node ...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: gyrex (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-26 05:20 EST by Jürgen Albert CLA
Modified: 2018-03-19 11:59 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Albert CLA 2015-02-26 05:20:53 EST
If e.g. two nodes publish a state for one service the following entries will be written to the zookeeper

/<somePrefixPaht>/example.service.pid/node1
/<somePrefixPaht>/example.service.pid/node2

If e.g. node1 goes offline (e.g. via console command "cloud setOffline") the service state of node2 will be removed too.

A first guess is, that the example.service.pid zookeeper node is ephemeral, which causes the node to be removed if the creator is goes offline. Thus the child of node2 will be removed too. 

A solution could be, that the service pid node should be created as persistent node. On the other hand a kind of shared ephemeral mode would be nice, but I havn't found something like this.