[
https://issues.apache.org/jira/browse/HADOOP-13773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626832#comment-15626832
]
Andrew Wang commented on HADOOP-13773:
--------------------------------------
Hi Ravi, precommit is multi-branch now, if you follow the naming convention of
e.g. HADOOP-13733.branch-2.001.patch. See:
https://wiki.apache.org/hadoop/HowToContribute#Naming_your_patch
The precommit bot will also detect the branch correctly for github PRs, though
if there's both a PR and a patch (as on this JIRA), the precommit bot will
always use the PR. When this has happened in the past, I've resorted to filing
a new JIRA to unstick precommit.
> wrong HADOOP_CLIENT_OPTS in hadoop-env on branch-2
> ---------------------------------------------------
>
> Key: HADOOP-13773
> URL: https://issues.apache.org/jira/browse/HADOOP-13773
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 2.6.1, 2.7.3
> Reporter: Fei Hui
> Assignee: Fei Hui
> Fix For: 2.8.0
>
> Attachments: HADOOP-13773.patch
>
>
> in conf/hadoop-env.sh,
> export HADOOP_CLIENT_OPTS="-Xmx512m $HADOOP_CLIENT_OPTS"
> when i set HADOOP_HEAPSIZE ,and run 'hadoop jar ...', jvm args is not work.
> i see, in bin/hadoop,
> exec "$JAVA" $JAVA_HEAP_MAX $HADOOP_OPTS $CLASS "$@"
> HADOOP_OPTS is behind JAVA_HEAP_MAX, so HADOOP_HEAPSIZE is not work.
> for example i run 'HADOOP_HEAPSIZE=1024 hadoop jar ...' , the java process is
> 'java -Xmx1024m ... -Xmx512m...', then Xmx512m is valid， and Xmx1024m is
> invalid
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
