Bulk Operation

HELIX-134 Race condition between FINALIZE callbacks and Zk Callbacks

HELIX-134 Add stress test by simulating gc and network partition for the new HelixManager implementation

HELIX-134 Design and implement new api's for new HelixManager implementation

HELIX-134 Flapping detection

HELIX-134 Proper handling exception thrown by handleNewSessionAsParticipant() when an instance already exists

HELIX-134 handleNewSession() should wait on all left-over tasks to be cancelled successfully before start new session

HELIX-134 HelixManager#isLeader() should compare both instanceName and sessionId

HELIX-134 Take care of consecutive handleNewSession() and session expiry during handleNewSession()

HELIX-134 separate HelixManager implementation for participant, controller, and distributed controller

HELIX-134 Need to double check the logic to prevent 2 controllers to control the same cluster

HELIX-134 ZkHelixManager.handleNewSession() and ZkHelixManager.disconnect() need to be sync'ed

HELIX-134 StateModel stateTransitionMethod() and rest() are not synchronized on the partition

HELIX-134 race condition in ZkHelixManager.handleNewSession()

HELIX-134 ZkHelixManager.isLeader() should check session id in addition to instance name

HELIX-134 Possible race condition in ZkHelixManager.disconnect() during zk session expiry

HELIX-134 ZkHelixManager.handleNewSession() can happen when a liveinstance already exists