You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2016/11/19 23:54:59 UTC

[jira] [Updated] (AMBARI-18943) If multiple HSI components are deployed then HSI start should not restart llap

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

Sumit Mohanty updated AMBARI-18943:
-----------------------------------
    Attachment: AMBARI-18943.patch

> 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)