[jira] [Updated] (BOOKKEEPER-135) Fencing does not check the ledger masterPasswd

["Ivan Kelly (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-135:
----------------------------------

    Attachment: BOOKKEEPER-135.diff

new patch fixes the issue, and does some refactoring on the bookie side to try to make flow clearer.

This patch depends on BOOKKEEPER-152
                
> Fencing does not check the ledger masterPasswd
> ----------------------------------------------
>
>                 Key: BOOKKEEPER-135
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-135
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.1.0
>
>         Attachments: BOOKKEEPER-135.diff, BOOKKEEPER-135.diff
>
>
> When fencing, the ledger handle is not checked before the fencing is applied. Currently the openLedger does fail, on because it will addEntry and fail at that point, but by this stage, fencing has already been applied. The check should be earlier.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira