Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 27 Jan 2014 10:40:40 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12691347.1390819085691.17682.1390819240314@arcas>
In-Reply-To: <JIRA.12691347.1390819085691@arcas>
References: <JIRA.12691347.1390819085691@arcas>
Subject: [jira] [Updated] (HBASE-10423) Report back the message of split or
 rollback failure to the master
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Harsh J updated HBASE-10423:
----------------------------

    Attachment: HBASE-10423.patch

> Report back the message of split or rollback failure to the master
> ------------------------------------------------------------------
>
>                 Key: HBASE-10423
>                 URL: https://issues.apache.org/jira/browse/HBASE-10423
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.96.0
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Trivial
>         Attachments: HBASE-10423.patch
>
>
> A failure in splitting and rolling back causes an RS to abort with the error logged. However, the abort message sent back to the Master does not carry the same message for traceability.
> It would be useful if the Master at least had the message part of the exception given that its log writes are fewer than the RSs, helping capture reasons even if the RS loses its logs since, or couldn't log.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)