[
https://issues.apache.org/jira/browse/HADOOP-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426298#comment-16426298
]
Hudson commented on HADOOP-14855:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13927 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13927/])
HADOOP-14855. Hadoop scripts may errantly believe a daemon is still (szegedim:
rev e52539b46fb13db423490fe02d46e9fae72d72fe)
* (edit) hadoop-common-project/hadoop-common/src/main/bin/hadoop-functions.sh
> Hadoop scripts may errantly believe a daemon is still running, preventing it
> from starting
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-14855
> URL: https://issues.apache.org/jira/browse/HADOOP-14855
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.0.0-alpha4
> Reporter: Aaron T. Myers
> Assignee: Robert Kanter
> Priority: Major
> Fix For: 3.2.0
>
> Attachments: HADOOP-14855.001.patch, HADOOP-14855.002.patch
>
>
> I encountered a case recently where the NN wouldn't start, with the error
> message "namenode is running as process 16769. Stop it first." In fact the
> NN was not running at all, but rather another long-running process was
> running with this pid.
> It looks to me like our scripts just check to see if _any_ process is running
> with the pid that the NN (or any Hadoop daemon) most recently ran with. This
> is clearly not a fool-proof way of checking to see if a particular type of
> daemon is now running, as some other process could start running with the
> same pid since the daemon in question was previously shut down.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
