You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/10/12 22:58:05 UTC

[jira] [Commented] (AMBARI-13388) Update hbase-env config without removing custom changes

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

Hadoop QA commented on AMBARI-13388:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12766116/AMBARI-13388.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/3949//console

This message is automatically generated.

> Update hbase-env config without removing custom changes
> -------------------------------------------------------
>
>                 Key: AMBARI-13388
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13388
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server, ambari-upgrade
>    Affects Versions: 2.1.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13388.patch
>
>
> We faced with the problem when we need to update hbase-env during upgrade, but we can't remove users customizations.
> According to changes for MaxDirectMemorySize in hbase-env.



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