ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17809) DataNode failed to start because of "small initial heap"
Date Wed, 20 Jul 2016 16:58:20 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-17809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386203#comment-15386203
] 

Hadoop QA commented on AMBARI-17809:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12819085/AMBARI-17809-branch-2.4.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:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7938//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7938//console

This message is automatically generated.

> DataNode failed to start because of "small initial heap"
> --------------------------------------------------------
>
>                 Key: AMBARI-17809
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17809
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17809-branch-2.4.patch
>
>
> dtnode_heapsize should end with "m" like
> {code}
>           "dtnode_heapsize" : "1024m",
> {code}
> but in the cluster it's 
> {code}
>           "dtnode_heapsize" : "1024",
> {code}
> stack_advisor failed with 
> {code}
> 20 Jul 2016 04:52:17,900  INFO [pool-17-thread-1] StackAdvisorRunner:71 -     advisor
script stderr: Traceback (most recent call last):
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 158, in <module>
>     main(sys.argv)
>   File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 109, in main
>     result = stackAdvisor.recommendConfigurations(services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", line 760,
in recommendConfigurations
>     calculation(configurations, clusterSummary, services, hosts)
>   File "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.5/services/stack_advisor.py",
line 46, in recommendOozieConfigurations
>     newAdminUsers = "{0},oozie-admin,{1}".format(oozieUser, falconUser)
> UnboundLocalError: local variable 'falconUser' referenced before assignment
> 20 Jul 2016 04:52:17,902 ERROR [pool-17-thread-1] ClusterConfigurationRequest:156 - An
exception occurred while doing configuration topology update: org.apache.ambari.server.controller.internal.ConfigurationTopologyException:
Configuration recommendation failed.
> {code}
> and 1024m hasn't been recommended for dtnode_heapsize



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

Mime
View raw message