You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2018/10/05 20:21:00 UTC
[jira] [Commented] (HADOOP-15794) 3.1.1 cannot start on mac os
[ https://issues.apache.org/jira/browse/HADOOP-15794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640307#comment-16640307 ]
Jonathan Eagles commented on HADOOP-15794:
------------------------------------------
[~yishuihanxiao], this part of the code is parsing the output of
{code}
df -k -P <volume>
{code}
where volume is each of the local edit dirs namenode configured for the namenode as well as the extra checked dirs. This could possibly be affected if the output of df is 'aliased' on the namenode user's account or perhaps others issues where the df output is output on multiple lines.
Could you post an example output for the df -k -P <volume> (substituting <volume for the edit log dirs>)command for the namenode user on the affected system?
> 3.1.1 cannot start on mac os
> ----------------------------
>
> Key: HADOOP-15794
> URL: https://issues.apache.org/jira/browse/HADOOP-15794
> Project: Hadoop Common
> Issue Type: Bug
> Components: common
> Affects Versions: 3.1.1
> Environment: mac os, jdk 1.8, hadoop 3.1.1
> Reporter: yishuihanxiao
> Priority: Major
>
> After start 3.1.1 on mac os, the namenode cannot start, sounds the check
> {color:#82aaff}Volume failed. the detail error stacktrace as follwoing:
> {color}
> {color:#6a9955}2018-09-26{color} {color:#6a9955}17:01:41,929{color} {color:#ce9178}ERROR{color} {color:#569cd6}org.apache.hadoop.hdfs.server.namenode.NameNode{color}{color:#d4d4d4}: Failed to start namenode.{color}
> {color:#ce9178}java.io.IOException{color}{color:#d4d4d4}: Could not parse line: Filesystem {color}{color:#569cd6}1024{color}{color:#d4d4d4}-blocks Used Available Capacity Mounted on{color}
> {color:#ce9178} at org.apache.hadoop.fs.DF.parseOutput(DF.java:195){color}
> {color:#ce9178} at org.apache.hadoop.fs.DF.getFilesystem(DF.java:76){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker$CheckedVolume.<init>(NameNodeResourceChecker.java:69){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker.addDirToCheck(NameNodeResourceChecker.java:165){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNodeResourceChecker.<init>(NameNodeResourceChecker.java:134){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startCommonServices(FSNamesystem.java:1155){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNode.startCommonServices(NameNode.java:788){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:714){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:937){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:910){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1643){color}
> {color:#ce9178} at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1710){color}
> {color:#6a9955}2018-09-26{color} {color:#6a9955}17:01:41,931{color} {color:#b5cea8}INFO{color} {color:#569cd6}org.apache.hadoop.util.ExitUtil{color}{color:#d4d4d4}: Exiting with status {color}{color:#569cd6}1{color}{color:#d4d4d4}: {color}{color:#ce9178}java.io.IOException{color}{color:#d4d4d4}: Could not parse line: Filesystem {color}{color:#569cd6}1024{color}{color:#d4d4d4}-blocks Used Available Capacity Mounted on{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org