[
https://issues.apache.org/jira/browse/AMBARI-19268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767451#comment-15767451
]
Hadoop QA commented on AMBARI-19268:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12844248/AMBARI-19268.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9765//console
This message is automatically generated.
> ulimit override missing from upgrade catalogs
> ---------------------------------------------
>
> Key: AMBARI-19268
> URL: https://issues.apache.org/jira/browse/AMBARI-19268
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.2.2
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19268.patch
>
>
> After upgrade from 2.0.0 hadoop-env doesn't contain:
> {noformat}
> {% if is_datanode_max_locked_memory_set %}
> # Fix temporary bug, when ulimit from conf files is not picked up, without
> full relogin.
> # Makes sense to fix only when runing DN as root
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -l {{datanode_max_locked_memory}}
> fi
> {% endif %}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
