[HBASE-22731] ReplicationSource and HBaseInterClusterReplicationEndpoint log messages should include a target Peer identifier

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2.0, 2.1.5
• Fix Version/s: 3.0.0-alpha-1, 2.2.1, 2.1.6
• Component/s: Replication
• Assignee: Wellington Chevreuil
• Reporter: Wellington Chevreuil
• Created: 24/Jul/19 16:07
• Updated: 07/Aug/19 23:14
• Resolved: 07/Aug/19 10:20

Description

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.