hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3918) EditLogTailer shouldn't log WARN when other node is in standby mode
Date Fri, 21 Sep 2012 02:33:07 GMT

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

Todd Lipcon updated HDFS-3918:
------------------------------

    Attachment: hdfs-3918.txt

Attached patch cleans up the logs.

I now see the following:

12/09/20 19:30:36 INFO ha.EditLogTailer: Triggering log roll on remote NameNode todd-w510/127.0.0.1:8022
12/09/20 19:30:36 INFO ha.EditLogTailer: Skipping log roll. Remote node is not in Active state:
Operation category JOURNAL is not supported in state standby

                
> EditLogTailer shouldn't log WARN when other node is in standby mode
> -------------------------------------------------------------------
>
>                 Key: HDFS-3918
>                 URL: https://issues.apache.org/jira/browse/HDFS-3918
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-3918.txt
>
>
> If both nodes are in standby mode, each will be trying to roll the others' logs, which
results in errors like:
> Unable to trigger a roll of the active NN 
> org.apache.hadoop.ipc.StandbyException: Operation category JOURNAL is not supported in
state standby
> We should catch this specific exception and not log it at WARN level, since it's expected
behavior.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message