You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2016/11/15 17:54:58 UTC

[jira] [Created] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

Dmitry Lysnichenko created AMBARI-18899:
-------------------------------------------

             Summary: Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart
                 Key: AMBARI-18899
                 URL: https://issues.apache.org/jira/browse/AMBARI-18899
             Project: Ambari
          Issue Type: Bug
            Reporter: Dmitry Lysnichenko
            Assignee: Dmitry Lysnichenko
         Attachments: AMBARI-18899.patch


I think not marking HDFS as restart required when Ambari upgrades is a good goal.

In general its a difficult to get it right for all services.
* hadoop.security.key.provider.path
* dfs.encryption.key.provider.uri

These two are removed by stack advisor when RANGER KMS does not exist. We should find out why it got added on Ambari upgrade. This seems like a bug to me.
* namenode_backup_dir




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