[
https://issues.apache.org/jira/browse/HBASE-22731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902533#comment-16902533
]
Hudson commented on HBASE-22731:
--------------------------------
Results for branch branch-2.2
[build #498 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/498/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/498//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/498//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/498//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> Affects Versions: 2.2.0, 2.1.5
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Minor
> Fix For: 3.0.0, 2.2.1, 2.1.6
>
> Attachments: HBASE-22731.branch-2.001.patch,
> 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)
