[
https://issues.apache.org/jira/browse/AMBARI-9219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284614#comment-14284614
]
Hudson commented on AMBARI-9219:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit-docker #817 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/817/])
AMBARI-9219. HDFS should not need restart after adding second Hive component
(alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c9619f1a9aeee260a5a6e0de059cecd449437ba0)
* ambari-web/app/controllers/main/host/details.js
> 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
>
> Attachments: AMBARI-9219.patch, prop-host-switch.tiff
>
>
> 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)
