[
https://issues.apache.org/jira/browse/BOOKKEEPER-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529201#comment-13529201
]
Flavio Junqueira commented on BOOKKEEPER-500:
---------------------------------------------
[~hustlmsp] You have marked this for 4.2.0, but I would say that whatever is
not a blocker should be moved to 4.3.0 or even 4.2.1 in the case of bugs. Is
this a blocker?
> Fencing doesn't work when restarting bookies.
> ---------------------------------------------
>
> Key: BOOKKEEPER-500
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-500
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-500.-testcase.diff
>
>
> Currently we just record fence state in memory. If the bookies are restarted,
> all fence states are gone. It would break the correctness that we guarantee
> about fencing.
> We should record the fence state in the file info to make it persistent.
> A test case added to produce this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
