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-20640) Upgrade server-side actions should be performed only one time per group
Date Fri, 31 Mar 2017 11:09:41 GMT

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

Hadoop QA commented on AMBARI-20640:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12861354/AMBARI-20640.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 3 new or modified
test files.

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

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler 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/11253//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11253//console

This message is automatically generated.

> Upgrade server-side actions should be performed only one time per group
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-20640
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20640
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20640.patch
>
>
> Some server side actions, noteably config changes, should happen only one time.  there
are a couple of cases:
> {noformat}
>       <component name="MAPREDUCE2_CLIENT">
>         <pre-upgrade>
>           <task xsi:type="server_action" class="org.apache.ambari.server.serveraction.upgrades.FixLzoCodecPath">
>             <summary>Verifying LZO codec path for mapreduce</summary>
>           </task>
>         </pre-upgrade>
>       </component>
> {noformat}
> {noformat}
>       <component name="NODEMANAGER">
>         <pre-upgrade>
>           <task xsi:type="configure" id="hdp_2_5_0_0_add_spark2_yarn_shuffle"/>
>         </pre-upgrade>
>         <pre-downgrade/>
>         <upgrade>
>           <task xsi:type="restart-task" />
>         </upgrade>
>       </component>
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message