[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Attachment: AMBARI-17518.patch > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Attachment: (was: AMBARI-17518.patch) > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Status: Patch Available (was: Open) > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Status: Open (was: Patch Available) > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17459) remove spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property in HDP2.5 definition
[ https://issues.apache.org/jira/browse/AMBARI-17459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360368#comment-15360368 ] Hudson commented on AMBARI-17459: - SUCCESS: Integrated in Ambari-trunk-Commit #5212 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5212/]) AMBARI-17459. remove spark.driver.extraJavaOptions and (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bd5822724e7ab2c79c437ce303cb8ecd232905ec]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/SPARK/configuration/spark-defaults.xml > remove spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions > property in HDP2.5 definition > - > > Key: AMBARI-17459 > URL: https://issues.apache.org/jira/browse/AMBARI-17459 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > > These two properties are not used for Spark, set to empty is only for > backward compatibility. So removing these two configurations starting from > HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17041) Support password type for custom properties
[
https://issues.apache.org/jira/browse/AMBARI-17041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360366#comment-15360366
]
Matt commented on AMBARI-17041:
---
[~tctruong213]
According to this JIRA, it is assumed that all property-types are mutually
exclusive.
Would there be a scenario where a property is of multiple types?
> Support password type for custom properties
> ---
>
> Key: AMBARI-17041
> URL: https://issues.apache.org/jira/browse/AMBARI-17041
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Tuong Truong
>Assignee: Keta Patel
> Attachments: AMBARI-17041-trunk-Jun29.patch,
> AMBARI-17041-trunk.patch, add_property_pop_up.tiff,
> cluster_config_with_password_type_in_config_attributes_column.tiff,
> custom_properties_after_save.tiff, custom_property_password_type.tiff,
> custom_property_regular_type.tiff, schema_of_clusterconfig_table.tiff
>
>
> Currently, services can define properties in the XML configuration files that
> is flagged as type password:
>
> my.special.password
>
> PASSWORD
> Password to be masked
>
> and it will be masked properly in the UI as well as blueprint.
> Custom property should also support this option so that password can be added
> as custom property and treat accordingly.
> ==
> Proposed Design for the fix:
> ==
> At present only the key-value information of the service properties is stored
> in the DB ("clusterconfig" table in the "config_data" column).
> The "config_attributes" column stores only certain attributes like "final"
> indicating the list of properties set with the Final flag = true.
> The information about the property-type (i.e PASSWORD, USER, GROUP,
> ADDITIONAL_USER_PROPERTY, VALUE_FROM_PROPERTY_FILE, NOT_MANAGED_HDFS_PATH,
> etc) is extracted from the corresponding service's property file (e.g.
> hive-site.xml, core-site.xml, webhcat-env.xml, etc). These files contain
> information of the existing properties only. Custom Properties added by
> ambari user have no provision to store their additional attributes.
> Since, for this Jira we are concerned with only attribute for
> Custom Properties, we could add an additional field called "Property Type" in
> the "Add Property" pop-up which shows up on clicking "Add Property ..." in
> the Custom property section for a service. For now, only 2 options are shown
> in the drop-down list: NONE and PASSWORD .
> A few sample test properties are created using the new "Add Property" pop-up
> as can be seen in the following attachments.
> Attachments:
> "add_property_pop_up.tiff"
> "custom_property_password_type.tiff"
> "custom_property_regular_type.tiff"
> "custom_properties_after_save.tiff"
> The information for these Custom properties is stored in the
> DB in "clusterconfig" table, "config_attributes" column.
> The schema for "clusterconfig" table can be seen in the attachment:
> "schema_of_clusterconfig_table.tiff"
> The content of the "config_attributes" column with the
> information from the new Custom properties can be seen in the attachment:
> "cluster_config_with_password_type_in_config_attributes_column.tiff"
> Note: The fix so far is performed only for new Custom properties. The
> information for existing properties is extracted from the
> corresponding property xml files for the service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17241) Services should be able to reload configs without requiring restart
[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360365#comment-15360365
]
Matt commented on AMBARI-17241:
---
Thanks for your suggestions [~tctruong213]
>From your suggestion I infer that you would only show a button to the user
>saying 'Apply Configuration Changes'.
(i) if all configs that were changed does not require restart ... show no
warning, apply changes
(ii) if configs that were changed contains configs requiring restart and
configs not requiring restart ... show warning, restart service
(iii) if all configs that were changed requires restart ... show warning,
restart service
Please confirm if my understanding described above is correct. It would need
only some minor UI changes to the prototype I presented, to make it work that
way.
Just putting my thoughts on scenario (ii) above, where user changes some
configs, which need restart and some which don't.
Would there be a situation where user wants to apply the configurations, which
do not require restart, immediately, without affecting running jobs? And later
restart the service to apply other configs which were not applied before, after
the running jobs have been completed?
This action would apply the configs 'partially' - apply changes which do not
require restart first. From implementation perspective, this would be
challenging to implement - tracking if each config was applied or not is more
complex. Any thoughts on this [~tctruong213] whether users/customers require
this partial way of applying configs? This can also be an enhancement for this
JIRA, if required.
> Services should be able to reload configs without requiring restart
> ---
>
> Key: AMBARI-17241
> URL: https://issues.apache.org/jira/browse/AMBARI-17241
> Project: Ambari
> Issue Type: New Feature
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-17241-Design-Proposal.pdf
>
>
> The current implementation forces users to restart the service if any of the
> configurations have been updated.
> However some of the services support reloading the configuration parameters
> during run-time which does not require restart of the service.
> This behavior should be driven by metadata defined in configuration files.
> {code}
>
> foo-bar
> 0
> true
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-17241) Services should be able to reload configs without requiring restart
[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt updated AMBARI-17241:
--
Comment: was deleted
(was: Thanks for your suggestions [~tctruong213]
>From your suggestion I infer that you would only show a button to the user
>saying 'Apply Configuration Changes'.
(i) if all configs that were changed does not require restart ... show no
warning, apply changes
(ii) if configs that were changed contains configs requiring restart and
configs not requiring restart ... show warning, restart service
(iii) if all configs that were changed requires restart ... show warning,
restart service
Please confirm if my understanding described above is correct. It would need
only some minor UI changes to the prototype I presented, to make it work that
way.
Just putting my thoughts on scenario (ii) above, where user changes some
configs, which need restart and some which don't.
Would there be a situation where user wants to apply the configurations, which
do not require restart, immediately, without affecting running jobs? And later
restart the service to apply other configs which were not applied before, after
the running jobs have been completed?
This action would apply the configs 'partially' - apply changes which do not
require restart first. From implementation perspective, this would be
challenging to implement - tracking if each config was applied or not is more
complex. Any thoughts on this [~tctruong213] whether users/customers require
this partial way of applying configs? This can also be an enhancement for this
JIRA, if required.)
> Services should be able to reload configs without requiring restart
> ---
>
> Key: AMBARI-17241
> URL: https://issues.apache.org/jira/browse/AMBARI-17241
> Project: Ambari
> Issue Type: New Feature
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-17241-Design-Proposal.pdf
>
>
> The current implementation forces users to restart the service if any of the
> configurations have been updated.
> However some of the services support reloading the configuration parameters
> during run-time which does not require restart of the service.
> This behavior should be driven by metadata defined in configuration files.
> {code}
>
> foo-bar
> 0
> true
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17241) Services should be able to reload configs without requiring restart
[
https://issues.apache.org/jira/browse/AMBARI-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360364#comment-15360364
]
Matt commented on AMBARI-17241:
---
Thanks for your suggestions [~tctruong213]
>From your suggestion I infer that you would only show a button to the user
>saying 'Apply Configuration Changes'.
(i) if all configs that were changed does not require restart ... show no
warning, apply changes
(ii) if configs that were changed contains configs requiring restart and
configs not requiring restart ... show warning, restart service
(iii) if all configs that were changed requires restart ... show warning,
restart service
Please confirm if my understanding described above is correct. It would need
only some minor UI changes to the prototype I presented, to make it work that
way.
Just putting my thoughts on scenario (ii) above, where user changes some
configs, which need restart and some which don't.
Would there be a situation where user wants to apply the configurations, which
do not require restart, immediately, without affecting running jobs? And later
restart the service to apply other configs which were not applied before, after
the running jobs have been completed?
This action would apply the configs 'partially' - apply changes which do not
require restart first. From implementation perspective, this would be
challenging to implement - tracking if each config was applied or not is more
complex. Any thoughts on this [~tctruong213] whether users/customers require
this partial way of applying configs? This can also be an enhancement for this
JIRA, if required.
> Services should be able to reload configs without requiring restart
> ---
>
> Key: AMBARI-17241
> URL: https://issues.apache.org/jira/browse/AMBARI-17241
> Project: Ambari
> Issue Type: New Feature
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-17241-Design-Proposal.pdf
>
>
> The current implementation forces users to restart the service if any of the
> configurations have been updated.
> However some of the services support reloading the configuration parameters
> during run-time which does not require restart of the service.
> This behavior should be driven by metadata defined in configuration files.
> {code}
>
> foo-bar
> 0
> true
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16647) Move service advisor tests for HAWQ and PXF
[
https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360352#comment-15360352
]
Hadoop QA commented on AMBARI-16647:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12815929/AMBARI-16647.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 18 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7663//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7663//console
This message is automatically generated.
> Move service advisor tests for HAWQ and PXF
> ---
>
> Key: AMBARI-16647
> URL: https://issues.apache.org/jira/browse/AMBARI-16647
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk, 2.4.1
>
> Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch
>
>
> Currently the service advisor tests for HAWQ and PXF are under
> ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
> Move the tests to the service specific service_advisor files:
> ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py
> ambari-server/src/test/python/common-services/PXF/test_service_advisor.py
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360350#comment-15360350 ] Hudson commented on AMBARI-17491: - SUCCESS: Integrated in Ambari-trunk-Commit #5211 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5211/]) AMBARI-17491. Hive Database URL config updated by Ambari stack advisor (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=33423c71c68e46d171b1e602ca44e94745f39874]) * ambari-server/src/test/python/stacks/2.1/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch, AMBARI-17491_BE.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17459) remove spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions property in HDP2.5 definition
[ https://issues.apache.org/jira/browse/AMBARI-17459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-17459. Resolution: Fixed committed to trunk and branch-2.4 > remove spark.driver.extraJavaOptions and spark.yarn.am.extraJavaOptions > property in HDP2.5 definition > - > > Key: AMBARI-17459 > URL: https://issues.apache.org/jira/browse/AMBARI-17459 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Saisai Shao >Assignee: Saisai Shao > > These two properties are not used for Spark, set to empty is only for > backward compatibility. So removing these two configurations starting from > HDP 2.5. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360327#comment-15360327
]
Hudson commented on AMBARI-17543:
-
SUCCESS: Integrated in Ambari-trunk-Commit #5210 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5210/])
AMBARI-17543. Uninitialized variable in hive interactive code (smohanty)
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7117d092c9c9bbc68212366d6466d9fef2b18e35])
*
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-17543:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-16780) Move service advisor HAWQ and PXF tests from 2.3 and common stack_advisor folder to common-services folder
[ https://issues.apache.org/jira/browse/AMBARI-16780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain reassigned AMBARI-16780: - Assignee: Lav Jain > Move service advisor HAWQ and PXF tests from 2.3 and common stack_advisor > folder to common-services folder > -- > > Key: AMBARI-16780 > URL: https://issues.apache.org/jira/browse/AMBARI-16780 > Project: Ambari > Issue Type: Sub-task > Components: stacks >Reporter: Matt >Assignee: Lav Jain > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16758) Revisit HAWQ and PXF unit tests and refactor code
[
https://issues.apache.org/jira/browse/AMBARI-16758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lav Jain reassigned AMBARI-16758:
-
Assignee: Lav Jain
> Revisit HAWQ and PXF unit tests and refactor code
> -
>
> Key: AMBARI-16758
> URL: https://issues.apache.org/jira/browse/AMBARI-16758
> Project: Ambari
> Issue Type: Technical task
> Components: stacks
>Reporter: Matt
>Assignee: Lav Jain
>Priority: Minor
> Fix For: trunk
>
>
> Refactor HAWQ and PXF unit tests
> [~lavjain] notes:
> {code}
> ExecuteScript can be a separate function with command passed in as parameter.
> Similarily, common.stop_component can be refactored into a separate function
> with both test_stop_default and test_activate_hawq_standby calling it.
> If you want to go one step further, create a base class of
> TestHawqCommon(RMFTestCase) that defines the corresponding routines in
> common.py with TestHawqStandby(TestHawqCommon).
> assertResourceCalled can be defined using functools.partial
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF
[ https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-16647: -- Status: In Progress (was: Patch Available) > Move service advisor tests for HAWQ and PXF > --- > > Key: AMBARI-16647 > URL: https://issues.apache.org/jira/browse/AMBARI-16647 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: trunk, 2.4.0 >Reporter: Matt >Assignee: Lav Jain >Priority: Minor > Fix For: trunk, 2.4.1 > > Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch > > > Currently the service advisor tests for HAWQ and PXF are under > ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Move the tests to the service specific service_advisor files: > ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py > ambari-server/src/test/python/common-services/PXF/test_service_advisor.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF
[ https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-16647: -- Attachment: AMBARI-16647.v2.patch > Move service advisor tests for HAWQ and PXF > --- > > Key: AMBARI-16647 > URL: https://issues.apache.org/jira/browse/AMBARI-16647 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: trunk, 2.4.0 >Reporter: Matt >Assignee: Lav Jain >Priority: Minor > Fix For: trunk, 2.4.1 > > Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch > > > Currently the service advisor tests for HAWQ and PXF are under > ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Move the tests to the service specific service_advisor files: > ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py > ambari-server/src/test/python/common-services/PXF/test_service_advisor.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16647) Move service advisor tests for HAWQ and PXF
[ https://issues.apache.org/jira/browse/AMBARI-16647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-16647: -- Status: Patch Available (was: In Progress) > Move service advisor tests for HAWQ and PXF > --- > > Key: AMBARI-16647 > URL: https://issues.apache.org/jira/browse/AMBARI-16647 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: trunk, 2.4.0 >Reporter: Matt >Assignee: Lav Jain >Priority: Minor > Fix For: trunk, 2.4.1 > > Attachments: AMBARI-16647.patch, AMBARI-16647.v2.patch > > > Currently the service advisor tests for HAWQ and PXF are under > ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py > Move the tests to the service specific service_advisor files: > ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py > ambari-server/src/test/python/common-services/PXF/test_service_advisor.py -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360304#comment-15360304
]
Hadoop QA commented on AMBARI-17543:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12815926/AMBARI-17543.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7662//console
This message is automatically generated.
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi reassigned AMBARI-17491: -- Assignee: Vitaly Brodetskyi (was: Andrii Babiichuk) > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch, AMBARI-17491_BE.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi resolved AMBARI-17491. Resolution: Fixed Committed to trunk and branch-2.4 > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch, AMBARI-17491_BE.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360286#comment-15360286
]
Sumit Mohanty commented on AMBARI-17543:
{code}
--
Ran 261 tests in 6.922s
OK
--
Total run:1095
Total errors:0
Total failures:0
OK
[smohanty@HW12158 python (trunk)]$
{code}
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360284#comment-15360284
]
Vitaly Brodetskyi commented on AMBARI-17543:
+1
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-17543:
---
Status: Patch Available (was: Open)
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17543) Uninitialized variable in hive interactive code
[
https://issues.apache.org/jira/browse/AMBARI-17543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-17543:
---
Attachment: AMBARI-17543.patch
> Uninitialized variable in hive interactive code
> ---
>
> Key: AMBARI-17543
> URL: https://issues.apache.org/jira/browse/AMBARI-17543
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17543.patch
>
>
> Error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 190, in
> HiveServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
> line 86, in service_check
> params.hive_llap_principal, params.hive_server2_authentication,
> params.hive_transport_mode,
> AttributeError: 'module' object has no attribute 'hive_llap_principal'
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17543) Uninitialized variable in hive interactive code
Sumit Mohanty created AMBARI-17543:
--
Summary: Uninitialized variable in hive interactive code
Key: AMBARI-17543
URL: https://issues.apache.org/jira/browse/AMBARI-17543
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.4.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Priority: Critical
Fix For: 2.4.0
Error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
line 190, in
HiveServiceCheck().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/service_check.py",
line 86, in service_check
params.hive_llap_principal, params.hive_server2_authentication,
params.hive_transport_mode,
AttributeError: 'module' object has no attribute 'hive_llap_principal'
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17491: --- Attachment: AMBARI-17491_BE.patch > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch, AMBARI-17491_BE.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17491: --- Attachment: (was: AMBARI-17491.patch) > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-17491: --- Attachment: AMBARI-17491.patch > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch, AMBARI-17491.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-17491) Hive Database URL config updated by Ambari stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-17491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi reopened AMBARI-17491: > Hive Database URL config updated by Ambari stack advisor recommendation > --- > > Key: AMBARI-17491 > URL: https://issues.apache.org/jira/browse/AMBARI-17491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17491.patch > > > While removing service, Ambari should update only properties that are depend > on this service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17502) RU/EU Install packages fails on suse
[
https://issues.apache.org/jira/browse/AMBARI-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-17502:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4
> RU/EU Install packages fails on suse
>
>
> Key: AMBARI-17502
> URL: https://issues.apache.org/jira/browse/AMBARI-17502
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17502.patch
>
>
> No handlers could be found for logger "root"
> 2016-06-30 10:39:21,730 - Could not install packages. Error: Execution of
> '/usr/bin/zypper --quiet --non-interactiveverify --dry-run' returned 2.
> Unknown option '--non-interactiveverify'
> Unknown option '--dry-run'
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 166, in actionexecute
> ret_code = self.install_packages(package_list)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 400, in install_packages
> if not verifyDependencies():
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/packages_analyzer.py",
> line 309, in verifyDependencies
> code, out = rmf_shell.checked_call(cmd, sudo=True)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 71, in inner
> result = function(command, **kwargs)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 294, in _call
> raise Fail(err_msg)
> Fail: Execution of '/usr/bin/zypper --quiet --non-interactiveverify
> --dry-run' returned 2. Unknown option '--non-interactiveverify'
> Unknown option '--dry-run'
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 469, in
> InstallPackages().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 179, in actionexecute
> raise Fail("Failed to distribute repositories/install packages")
> resource_management.core.exceptions.Fail: Failed to distribute
> repositories/install packages
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17507) Provide an option not to log ambari-agent command output for user custom script action
[ https://issues.apache.org/jira/browse/AMBARI-17507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360054#comment-15360054 ] Hudson commented on AMBARI-17507: - SUCCESS: Integrated in Ambari-trunk-Commit #5209 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5209/]) AMBARI-17507. Provide an option not to log ambari-agent command output (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8d83ea62c689d556dd104fcb624ca4537a796b53]) * ambari-agent/src/test/python/ambari_agent/TestActionQueue.py * ambari-agent/src/main/python/ambari_agent/ActionQueue.py * ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java > Provide an option not to log ambari-agent command output for user custom > script action > -- > > Key: AMBARI-17507 > URL: https://issues.apache.org/jira/browse/AMBARI-17507 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17507.patch > > > Custom commands is a way to create a set of commands that can perform > specific actions on the cluster. Class of actions typically involve > initialization, setup, and cleanup - different than the > start/stop/configure/install etc. > By default all command output gets logged. It should be possible for the > command to indicate if the output should be logged if the command may output > PII information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17540) 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 v
[
https://issues.apache.org/jira/browse/AMBARI-17540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360032#comment-15360032
]
Hadoop QA commented on AMBARI-17540:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12815846/AMBARI-17540.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7661//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7661//console
This message is automatically generated.
> 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.
> --
>
> 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)
