[BOOKKEEPER-537] Handling session expire event

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.4.0
• Assignee: Sijie Guo
• Reporter: Sijie Guo
• Created: 08/Jan/13 03:29
• Updated: 16/May/16 21:47
• Resolved: 10/Apr/16 04:26

Description

This is a master jira to provide better session expire handling for both BOOKKEEPER and Hedwig.

This task could be divided into several tasks:

1) provide a reconnectable zookeeper client, which wrap the zookeeper client. when session is expired, it created a new zookeeper client to replace the expired one.

2) session handling for bookie server

3) session handling for bookkeeper client.

4) session handling for Hedwig. when session is expired, hedwig should disable ensemble change and ledger change. when the client is recovered from session expired state, hedwig enables ensemble change and ledger change, and it would try to reclaim its owned topic.

the works are available in https://github.com/sijie/bookkeeper/commits/retryable_zk_2. will try to generate the patches after 4.2.0 release.

Issue Links

• is depended upon by: BOOKKEEPER-628 Improve bookie registration interface
• is duplicated by: BOOKKEEPER-225 Handle session expires and disconnect events in BookKeeper
• is duplicated by: BOOKKEEPER-179 TODO: handle session disconnects and expires
• relates to: BOOKKEEPER-284 Review ZooKeeper usage in BookKeeper

Sub-Tasks

• reconnectable zookeeper client wrapper: Resolved
• handle session expire event in client: Resolved
• allow disabling ensemble change when session expired.: Resolved
• Make bookkeeper client use reconnectable zookeeper wrapper: Closed
• handle session expire event in bookie: Closed