hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Foley (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-1943) fail to start datanode while start-dfs.sh is executed by root user
Date Thu, 10 Nov 2011 00:07:53 GMT

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

Matt Foley resolved HDFS-1943.
------------------------------

          Resolution: Fixed
       Fix Version/s: 0.20.205.1
    Target Version/s: 0.20.205.1, 0.22.0, 0.23.0  (was: 0.23.0, 0.22.0, 0.20.205.1)

Committed to branch-0.20-security and branch-0.20-security-205.
                
> fail to start datanode while start-dfs.sh is executed by root user
> ------------------------------------------------------------------
>
>                 Key: HDFS-1943
>                 URL: https://issues.apache.org/jira/browse/HDFS-1943
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.20.205.0, 0.22.0, 0.23.0
>            Reporter: Wei Yongjun
>            Assignee: Matt Foley
>            Priority: Blocker
>             Fix For: 0.20.205.1, 0.22.0, 0.23.0
>
>         Attachments: HDFS-1943-branch-0.20-security.patch, HDFS-1943.patch
>
>
> When start-dfs.sh is run by root user, we got the following error message:
> # start-dfs.sh
> Starting namenodes on [localhost ]
> localhost: namenode running as process 2556. Stop it first.
> localhost: starting datanode, logging to /usr/hadoop/hadoop-common-0.23.0-SNAPSHOT/bin/../logs/hadoop-root-datanode-cspf01.out
> localhost: Unrecognized option: -jvm
> localhost: Could not create the Java virtual machine.
> The -jvm options should be passed to jsvc when we starting a secure
> datanode, but it still passed to java when start-dfs.sh is run by root
> while secure datanode is disabled. This is a bug of bin/hdfs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message