[
https://issues.apache.org/jira/browse/BOOKKEEPER-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473437#comment-13473437
]
Hudson commented on BOOKKEEPER-418:
-----------------------------------
Integrated in bookkeeper-trunk #748 (See
[https://builds.apache.org/job/bookkeeper-trunk/748/])
BOOKKEEPER-418: Store hostname of locker in replication lock (ivank)
(Revision 1396536)
Result = SUCCESS
ivank :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/meta/ZkLedgerUnderreplicationManager.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/proto/DataFormats.java
* /zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/proto/DataFormats.proto
> Store hostname of locker in replication lock
> --------------------------------------------
>
> Key: BOOKKEEPER-418
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-418
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-418.diff
>
>
> This is a debugging shortcut. If a ledger isn't being processed for a long
> time, this allows us to find which host is trying to rereplicate, and go look
> at the logs there.
--
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
