Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 14 Mar 2014 02:03:48 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12649213.1369349741051.65679.1394762628380@arcas>
In-Reply-To: <JIRA.12649213.1369349741051@arcas>
References: <JIRA.12649213.1369349741051@arcas>
Subject: [jira] [Updated] (HBASE-8604) improve reporting of incorrect peer
 address in replication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-8604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated HBASE-8604:
---------------------------------

    Fix Version/s:     (was: 0.94.19)
                   0.94.18

> 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.96.2, 0.98.1, 0.99.0, 0.94.18
>
>         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)