[
https://issues.apache.org/jira/browse/HBASE-22731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900917#comment-16900917
]
Wellington Chevreuil edited comment on HBASE-22731 at 8/6/19 11:28 AM:
-----------------------------------------------------------------------
Ain't sure the #319 checkstyle issue was introduced by last patch, but am
fixing it anyway. The other was definitely introduced in this patch.
was (Author: wchevreuil):
Ain't sure the #319 checkstyle issue was introduced by last patch, but am
fixing it anyway.
> ReplicationSource and HBaseInterClusterReplicationEndpoint log messages
> should include a target Peer identifier
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-22731
> URL: https://issues.apache.org/jira/browse/HBASE-22731
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Minor
> Attachments: HBASE-22731.master.001.patch,
> HBASE-22731.master.002.patch, HBASE-22731.master.003.patch,
> HBASE-22731.master.004.patch, HBASE-22731.master.005.patch
>
>
> _ReplicationSource_ and _HBaseInterClusterReplicationEndpoint_ already
> include a good number of helpful DEBUG and TRACE log messages to help us
> troubleshooting typical replication problems, such as lags or mysteriously
> missing edits on target peer.
> However, for each configured peer, there will be an individual
> _ReplicationSource_/_HBaseInterClusterReplicationEndpoint_ pair running in
> parallel, in scenarios where we need to investigate issues within a source to
> an specific peer, we can't distinguish from which peer specific
> _ReplicationSource_/_HBaseInterClusterReplicationEndpoint._ For such cases it
> would be nice to have an identifier for specific peer the given
> _ReplicationSource_/_HBaseInterClusterReplicationEndpoint_ is related to.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
