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

Swapan Shridhar updated AMBARI-17540:
-------------------------------------
    Summary: Validation check for HiveServer Interactive if remaining cluster 
capacity < 512 MB. Also (1). fix for setting visibility to FALSE for 'LLAP 
queue capacity' slider if 'llap' queue is in STOPPED state. (2). 
security_status fn. for Hive Server Interactive.  (was: Add a validation check 
for HiveServer Interactive if total remaining capacity in cluster is less than 
512 MB (a safeguard for Service Checks). Also, fix for setting visibility to 
FALSE for 'LLAP queue capacity' slider if 'llap' queue is in STOPPED state.)

> Validation check for HiveServer Interactive if remaining cluster capacity < 
> 512 MB. Also (1). fix for setting visibility to FALSE for 'LLAP queue 
> capacity' slider if 'llap' queue is in STOPPED state. (2). security_status 
> fn. for Hive Server Interactive.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17540
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17540
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Swapan Shridhar
>            Assignee: Swapan Shridhar
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17540.patch
>
>
> Added the following :
> - Validation check for HiveServer Interactive, if total remaining capacity in 
> cluster is less than 512 MB (a safeguard for Service Checks). 
> - Fix for setting visibility to FALSE for 'LLAP queue capacity' slider if 
> 'llap' queue is in STOPPED state.
> - security_status fn. for Hive Server Interactive updated.



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

Reply via email to