[jira] [Updated] (AMBARI-24483) Timeline v2 HBase Does Start After Upgrade Due to Missing System Queue

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot updated AMBARI-24483:
------------------------------------
    Labels: pull-request-available  (was: )

> Timeline v2 HBase Does Start After Upgrade Due to Missing System Queue
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-24483
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24483
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.7.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.1
>
>
> *During Upgrade*
> # If cluster is big i.e >50GB and each machines has minimum 10GB resources
> #* If *yarn-system* queue doesn't exist then we shall create a queue with *zero capacity*. 
> #* All the necessary setting for queue such as *queue-priority*, *queue-acls*, *disabling pre-emption* for this queue are set.
> #* ats-hbase app queue name also set to *yarn-system*
> #* But *do NOT* enable system service mode by default. Let upgrade happens in embedded mode successfully. 
> #* Post upgrade, admin can change flag to enable system_service mode if required by providing sufficient capacity to *yarn-system* queue. This step *need to be documented.*
> # If cluster is small
> #* Continue upgrade in embedded mode without creating a yarn-system queue. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)