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-16992) Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
Date Wed, 01 Jun 2016 23:47:59 GMT

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

Hadoop QA commented on AMBARI-16992:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12807519/AMBARI-16992-trunk-orig.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7126//console

This message is automatically generated.

> Recommend hawq_rm_nvcore_limit_perseg in HAWQ service advisor
> -------------------------------------------------------------
>
>                 Key: AMBARI-16992
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16992
>             Project: Ambari
>          Issue Type: Improvement
>          Components: stacks
>            Reporter: Matt
>            Assignee: Matt
>            Priority: Minor
>             Fix For: trunk, 2.4.0
>
>         Attachments: AMBARI-16992-trunk-orig.patch
>
>
> Set hawq_rm_nvcore_limit_perseg as the lowest cpu_count across all HAWQ hosts



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

Mime
View raw message