[
https://issues.apache.org/jira/browse/HBASE-8604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920744#comment-13920744
]
Hadoop QA commented on HBASE-8604:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12632798/HBASE-8604.1.patch
against trunk revision .
ATTACHMENT ID: 12632798
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8899//console
This message is automatically generated.
> improve reporting of incorrect peer address in replication
> ----------------------------------------------------------
>
> Key: HBASE-8604
> URL: https://issues.apache.org/jira/browse/HBASE-8604
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Affects Versions: 0.94.6
> Reporter: Roman Shaposhnik
> Assignee: Rekha Joshi
> Priority: Minor
> Fix For: 0.94.19
>
> Attachments: HBASE-8604.1.patch
>
>
> I was running some replication code that incorrectly advertised the peer
> address for replication. HBase complained that the format of the record was
> NOT what it was expecting but it didn't include what it saw in the exception
> message. Including that string would help cutting down the time it takes to
> debug issues like that.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
