You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2016/04/10 06:26:25 UTC
[jira] [Resolved] (BOOKKEEPER-705) handle session expire event in
client
[ https://issues.apache.org/jira/browse/BOOKKEEPER-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sijie Guo resolved BOOKKEEPER-705.
----------------------------------
Resolution: Won't Fix
I think it is already covered by
{code}
commit 92722ee9c34b069e23d1a87d7fc78256b8540268
Author: Sijie Guo <si...@apache.org>
Date: Tue Jan 26 13:11:04 2016 -0800
BOOKKEEPER-855: handle session expire event in bookie (sijie)
This change is to retry bookie registration when zookeeper session expired.
Author: Sijie Guo <si...@apache.org>
Reviewers: Ivan Kelly <iv...@apache.org>, Matteo Merli <mm...@apache.org>
Closes #1 from sijie/sijie/BOOKKEEPER-855
{code}
> handle session expire event in client
> -------------------------------------
>
> Key: BOOKKEEPER-705
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-705
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-client, bookkeeper-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.4.0
>
> Attachments: BOOKKEEPER-705.diff, BOOKKEEPER-705.v2.patch
>
>
> handling zookeeper session expire event in bookie server & bookie watcher.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)