[
https://issues.apache.org/jira/browse/HBASE-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-18874:
--------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Resolving again.
[~pankaj_kumar], please open new issue to backport to branch-1. Generally, we
don't want to reopen issues. Reopening issues complicates the issue lifecycle
making it hard for those who are following behind -- vendors, fellows trying to
debug related issue a year later -- to understand what happened inside the
scope of a JIRA. We have an informal rule where you can reopen if less than a
week or so has elapsed but even, then, better to open new issue. Also, the
fix-version on this issue is also 2.0.0-alpha-4. There is no branch-1 in the
fix versions list; another reason not to do the reopen Thanks..
> HMaster abort message will be skipped if Throwable is passed null
> -----------------------------------------------------------------
>
> Key: HBASE-18874
> URL: https://issues.apache.org/jira/browse/HBASE-18874
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Pankaj Kumar
> Assignee: Pankaj Kumar
> Priority: Minor
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18874-branch-1.patch, HBASE-18874.patch
>
>
> In HMaster class, we are logging abort message only in case when Throwable is
> not null,
> {noformat}
> if (t != null) LOG.fatal(msg, t);
> {noformat}
> We will miss the abort message in this case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
