ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-12349) Datanode failed to start when use non-default dfs.datanode.data.dir.mount.file or net.topology.script.file.name
Date Wed, 15 Jul 2015 16:16:04 GMT

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

Di Li updated AMBARI-12349:
---------------------------
    Attachment: AMBARI-12349.patch

> Datanode failed to start when use non-default dfs.datanode.data.dir.mount.file or net.topology.script.file.name
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-12349
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12349
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Weiwei Yang
>            Assignee: Di Li
>            Priority: Critical
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12349.patch
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> When configure hadoop from install wizard, set "File that stores mount point" or "net.topology.script.file.name"
to a non default location, e.g 
> /etc/hadoop1/conf/dfs_data_dir_mount.hist
> /etc/hadoop1/conf/topology_script.py
> install failed because datanode could not be start, with error message
> Applying File['/etc/hadoop1/conf/topology_mappings.data'] failed, parent directory /etc/hadoop1/conf
doesn't exist



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message