You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2015/12/03 18:36:11 UTC

[jira] [Updated] (AMBARI-14189) Log displays wrong text for various tasks of Express Upgrade

     [ https://issues.apache.org/jira/browse/AMBARI-14189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitry Lysnichenko updated AMBARI-14189:
----------------------------------------
    Attachment: AMBARI-14189.patch

> Log displays wrong text for various tasks of Express Upgrade
> ------------------------------------------------------------
>
>                 Key: AMBARI-14189
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14189
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: AMBARI-14189.patch
>
>
> Performed an Express Upgrade from 2.2.8 to 2.3.4
> It was observed that at multiple stages during EU, we print text as "Rolling Upgrade" instead of "Express Upgrade"
> Few examples where stdout shows as "Rolling Upgrade":
> "command_detail" : "Check Tez Tarball",
> This is a Rolling Upgrade, but keep the version unchanged
> "command_detail" : "Prepare HDFS"
> PREPARE rolling upgrade
> "command_detail" : "RESTART MAPREDUCE2/HISTORYSERVER",
> Because this is a Rolling Upgrade, will use version
> "command_detail" : "RESTART HIVE/HIVE_SERVER",
> Because this is a Rolling Upgrade, will use version
> "command_detail" : "Execute HDFS Finalize",
> Executing Rolling Upgrade finalize
> For a complete list, check attachment and "Find All" with entire word as "rolling"
> Note - This issue could cause confusion for Support and customers when they investigate some cases as we print the wrong upgrade type in logs



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