You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2015/01/20 19:36:35 UTC

[jira] [Created] (AMBARI-9219) HDFS should not need restart after adding second Hive component

Antonenko Alexander created AMBARI-9219:
-------------------------------------------

             Summary: HDFS should not need restart after adding second Hive component
                 Key: AMBARI-9219
                 URL: https://issues.apache.org/jira/browse/AMBARI-9219
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.0.0
            Reporter: Antonenko Alexander
            Assignee: Antonenko Alexander
            Priority: Critical
             Fix For: 2.0.0


1) I added a second Hive Metastore, which also updates the proxyuser for hcat to core-site
2) this requires a restart to NN and SNN, which is OK
3) then I went to add a second HiveServer2, that again updates the proxyuser, just switches the order of the existing hosts in the property.
4) that property change should not have happened. There is no reason to force another restart when the host list is not actually changing. So on property update, we should not make the change if the host list is effectively the same.

See screen shot.



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