[
https://issues.apache.org/jira/browse/AMBARI-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682065#comment-15682065
]
Hudson commented on AMBARI-18943:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #369 (See
[https://builds.apache.org/job/Ambari-branch-2.5/369/])
AMBARI-18943. If multiple HSI components are deployed then HSI start (smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=795dd1f814b8bf342a53c5a6c15ff60d568c2980])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit) ambari-server/src/test/python/stacks/2.5/HIVE/test_hive_server_int.py
* (add) ambari-server/src/test/python/stacks/2.5/configs/hsi_ha.json
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_interactive.py
> If multiple HSI components are deployed then HSI start should not restart llap
> ------------------------------------------------------------------------------
>
> Key: AMBARI-18943
> URL: https://issues.apache.org/jira/browse/AMBARI-18943
> Project: Ambari
> Issue Type: Bug
> Components: stacks
> Affects Versions: 2.5.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18943.patch
>
>
> When HSI component is started, it destroys the llap app and then starts it.
> However, if multiple HSI instances are deployed then when an instance is
> started (due to fail over of another instance) then it should be checked if
> llap is running and if it is then it should not be restarted.
> Multiple HSI instances are deployed only in an active-passive scenario to
> enable fail over. As llap app is an YARN app, it automatically supports
> failover. So not forcing a restart of llap is a requirement when HSI is
> deployed in an active-passive mode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
