[
https://issues.apache.org/jira/browse/HADOOP-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16187463#comment-16187463
]
Elek, Marton commented on HADOOP-9902:
--------------------------------------
During the test of 3.0.0-beta1-RC0 I noticed that the HADOOP_LOG_DIR should
exist and be writable but the user of the namenode/datanode servers, which was
not the case with 2.7/2.8. I started the namenode/datanode with hdfs user until
now, but the owner of hadoop directory was the hadoop user. It is not working
with 3.0.0 without creating a logs directory with the hdfs user as the owner.
I need to create the HADOOP_LOG_DIR even if I use a custom log4j.properties
which doesn't use hadoop.log.dir variable.
May I suggest to add an additional line to the "incompatible changes. Something
like:
"HADOOP_LOG_DIR (which is ${HADOOP_HOME}/logs by default) should exist and
writable by the runtime user. (even if custom log4j configuration is used)"
> Shell script rewrite
> --------------------
>
> Key: HADOOP-9902
> URL: https://issues.apache.org/jira/browse/HADOOP-9902
> Project: Hadoop Common
> Issue Type: New Feature
> Components: scripts
> Affects Versions: 3.0.0-alpha1
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Labels: releasenotes
> Fix For: 3.0.0-alpha1
>
> Attachments: HADOOP-9902-10.patch, HADOOP-9902-11.patch,
> HADOOP-9902-12.patch, HADOOP-9902-13-branch-2.patch, HADOOP-9902-13.patch,
> HADOOP-9902-14.patch, HADOOP-9902-15.patch, HADOOP-9902-16.patch,
> hadoop-9902-1.patch, HADOOP-9902-2.patch, HADOOP-9902-3.patch,
> HADOOP-9902-4.patch, HADOOP-9902-5.patch, HADOOP-9902-6.patch,
> HADOOP-9902-7.patch, HADOOP-9902-8.patch, HADOOP-9902-9.patch,
> HADOOP-9902.patch, HADOOP-9902.txt, more-info.txt
>
>
> Umbrella JIRA for shell script rewrite. See more-info.txt for more details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
