hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14042) Fix FATAL level logging in FSHLog where logged for non fatal exceptions
Date Wed, 08 Jul 2015 21:19:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14619383#comment-14619383
] 

Andrew Purtell commented on HBASE-14042:
----------------------------------------

Bogus precommit. Looks like a Camel UT was erroneously flagged as a zombie.

This patch only changes log levels. No unit tests needed. 

> Fix FATAL level logging in FSHLog where logged for non fatal exceptions
> -----------------------------------------------------------------------
>
>                 Key: HBASE-14042
>                 URL: https://issues.apache.org/jira/browse/HBASE-14042
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.13, 1.1.1, 1.0.1.1
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>
>         Attachments: HBASE-14042-0.98.patch, HBASE-14042.patch
>
>
> We have FATAL level logging in FSHLog where an IOException causes a log roll to be requested.
It isn't a fatal event. Drop the log level to WARN. (Could even be INFO.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message