[
https://issues.apache.org/jira/browse/HADOOP-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HADOOP-2373:
----------------------------------------
Attachment: SafeModeReport1.patch
> reportStatus(String msg, boolean rightNow) need to be synchronized to
> protect lastStatusReport.
reportStatus() is called by methods that are synchronized, so there is no need
to synchronize itself.
> timeInSafemode/1000 => String.format("%0.2d", timeInSafemode/1000.0).
This prints whole number of seconds, I do not think we want microseconds here.
> Similarly, use String.format(...) for other floating point output in
> getTurnOffTip().
I did that. The threshold is printed up to the fourth digit.
Two digits is probably not enough since the default has three: 0.999f
> Name node silently changes state
> --------------------------------
>
> Key: HADOOP-2373
> URL: https://issues.apache.org/jira/browse/HADOOP-2373
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Robert Chansler
> Assignee: Konstantin Shvachko
> Fix For: 0.17.0
>
> Attachments: SafeModeReport.patch, SafeModeReport1.patch
>
>
> 1. The name node should create a log message when entering the "extension"
> period of safe mode after achieving the minimal replication threshold.
> Logging state changes is a Good Idea. When diagnosing 2159, there is no
> evidence whether the name node is in the extension period or not.
> 2. When in safe mode, the name node should periodically explain _why_ it is
> still in safe mode. (2159 again)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
