[
https://issues.apache.org/jira/browse/BOOKKEEPER-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471702#comment-13471702
]
Uma Maheswara Rao G commented on BOOKKEEPER-418:
------------------------------------------------
I have looked at the patch. Patch looks good to me.
Generally in real clusters this would be fine. If we want to debug any issue in
Jenkins/CI then this information may not help as all will in same host.
But I also don't see any clean way to include port.
+1
> 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
