[jira] [Issue Comment Deleted] (AMBARI-6704) ambari-server setup with the jdbc options results setup completed but miss some steps and missleading
[
https://issues.apache.org/jira/browse/AMBARI-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vineet Goel updated AMBARI-6704:
Comment: was deleted
(was: I created a story in the team backlog and we will prioritize this
appropriately for investigation in the next few weeks.
https://www.pivotaltracker.com/story/show/109238982)
> ambari-server setup with the jdbc options results setup completed but miss
> some steps and missleading
> -
>
> Key: AMBARI-6704
> URL: https://issues.apache.org/jira/browse/AMBARI-6704
> Project: Ambari
> Issue Type: Bug
>Reporter: jun aoki
>Assignee: jun aoki
>Priority: Minor
> Attachments: AMBARI-6704.patch
>
>
> When executing ambari-server setup command with jdbc options, I get
> successfully setup but many things (like selinux and creating ambari user)
> are missing.
> {code}
> $ sudo ambari-server setup --jdbc-db=mysql --jdbc-driver aaa
> Using python /usr/bin/python2.6
> Setup ambari-server
> JDBC driver was successfully initialized .
> Ambari Server 'setup' completed successfully.
> {code}
> This should've kept going further
> {code}
> $ sudo ambari-server setup
> Using python /usr/bin/python2.6
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'enabled'
> SELinux mode is 'enforcing'
> Temporarily disabling SELinux
> WARNING: SELinux is set to 'permissive' mode and temporarily disabled.
> OK to continue [y/n] (y)?
> Ambari-server daemon is configured to run under user 'ambariuser'. Change
> this setting [y/n] (n)?
> ...
> {code}
> I can submit a patch in a short while.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16938) Deploy: UI: Hive_metastore not started
[
https://issues.apache.org/jira/browse/AMBARI-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305145#comment-15305145
]
Hadoop QA commented on AMBARI-16938:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806710/AMBARI-16938.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/7043//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7043//console
This message is automatically generated.
> Deploy: UI: Hive_metastore not started
> --
>
> Key: AMBARI-16938
> URL: https://issues.apache.org/jira/browse/AMBARI-16938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16938.patch
>
>
> Deploy ambari cluster using UI with hive for existing mysql setup
> Actual: Hive metastore is failing to start due to unable to connect to DB.
> 2016-05-26 00:20:15,442 - Execute['/usr/jdk64/jdk1.8.0_77/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/hive-metastore/lib/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification 'jdbc:mysql://host/hivedb'
> hiveuser PROTECTED com.mysql.jdbc.Driver']
> {'path': ['/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin'], 'tries': 5,
> 'try_sleep': 10}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16940) VDF: support for selecting enabled + default Stacks
[ https://issues.apache.org/jira/browse/AMBARI-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305139#comment-15305139 ] Hudson commented on AMBARI-16940: - FAILURE: Integrated in Ambari-trunk-Commit #4947 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4947/]) AMBARI-16940. VDF: support for selecting enabled + default Stacks. (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=03600fa75274c82cc89b025c51bb5d622d474711]) * ambari-web/karma.conf.js * ambari-web/app/models/repository.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html * ambari-web/app/styles/application.less * ambari-web/test/controllers/wizard/step1_test.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js * ambari-admin/src/main/resources/ui/admin-web/app/views/modals/publicRepoDisabled.html * ambari-web/app/templates/wizard/step1/public_option_disabled_window_body.hbs * ambari-web/test/utils/array_utils_test.js * ambari-web/app/models/stack_version/service_simple.js * ambari-web/app/controllers/wizard/step1_controller.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js * ambari-web/app/messages.js * ambari-web/app/routes/installer.js * ambari-admin/src/main/resources/ui/admin-web/app/index.html * ambari-web/app/controllers/wizard/step0_controller.js * ambari-web/app/controllers/wizard/step7_controller.js * ambari-admin/src/main/resources/ui/admin-web/app/views/modals/ConfirmationModal.html * ambari-web/app/views/wizard/step1_view.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/AddVersionModal.js * ambari-web/app/styles/common.less * ambari-web/test/views/common/host_progress_popup_body_view_test.js * ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css * ambari-web/app/mappers/stack_mapper.js * ambari-web/test/mixins/common/configs/config_recommendation_parser_test.js * ambari-web/app/models/stack.js * ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/ConfirmationModal.js * ambari-web/test/controllers/installer_test.js * ambari-web/app/controllers/wizard/step3_controller.js * ambari-web/app/templates/wizard/step1/vdf_upload.hbs * ambari-web/app/controllers/wizard/step4_controller.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsListCtrl.js * ambari-admin/src/main/resources/ui/admin-web/app/views/modals/AddVersionModal.html * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Utility.js * ambari-web/test/views/wizard/step1_view_test.js * ambari-web/app/assets/test/tests.js * ambari-web/app/controllers/installer.js * ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js * ambari-web/app/utils/array_utils.js * ambari-web/app/templates/wizard/step1.hbs > VDF: support for selecting enabled + default Stacks > --- > > Key: AMBARI-16940 > URL: https://issues.apache.org/jira/browse/AMBARI-16940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-16940.patch > > > The work revamps the UX for leveraging VDF(Version Definition File) feature > of ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16932) Atlas server start failed after Ambari upgrade due to missing solrCloudCli.sh script
[
https://issues.apache.org/jira/browse/AMBARI-16932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305140#comment-15305140
]
Hudson commented on AMBARI-16932:
-
FAILURE: Integrated in Ambari-trunk-Commit #4947 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4947/])
AMBARI-16932 - Atlas server start failed after Ambari upgrade due to
(tbeerbower:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d97f396d65f3eed069dc2e0d6ecdeee12aad8b78])
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py
*
ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py
* ambari-server/src/test/python/stacks/2.3/configs/default.json
* ambari-server/src/test/python/stacks/2.3/configs/secure.json
* ambari-server/src/test/python/stacks/2.5/configs/default.json
> Atlas server start failed after Ambari upgrade due to missing solrCloudCli.sh
> script
>
>
> Key: AMBARI-16932
> URL: https://issues.apache.org/jira/browse/AMBARI-16932
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> *Steps*
> # Deploy HDP-2.4.2.0 cluster with Ambari 2.2.2.0 (including Atlas)
> # Upgrade Ambari to 2.4.0.0
> # Stop and start all services
> *Result*
> Atlas Metadata server start fails with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 165, in
> MetadataServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 67, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 51, in configure
> metadata()
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 113, in metadata
> upload_conf_set('basic_configs', random_num)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 135, in upload_conf_set
> group=params.user_group)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
> line 48, in upload_configuration_to_zk
> group=group
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> JAVA_HOME=/usr/jdk64/jdk1.7.0_67 ;
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z
> os-r6-tgvuks-dgm10toeriedwngdha-r6-4.openstacklocal:2181,os-r6-tgvuks-dgm10toeriedwngdha-r6-3.openstacklocal:2181,os-r6-tgvuks-dgm10toeriedwngdha-r6-2.openstacklocal:2181None
> --upload-config -d
> /usr/lib/ambari-logsearch-solr/server/solr/configsets/basic_configs/conf -cs
> basic_configs -rt 5 -i 10' returned 127. -bash:
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh: No such file or
> directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16915) Storm Stack advisor should not make storm.topology.submission.notifier.plugin.class property required
[
https://issues.apache.org/jira/browse/AMBARI-16915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305136#comment-15305136
]
Hadoop QA commented on AMBARI-16915:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806707/AMBARI-16915_branch-2.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/7042//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7042//console
This message is automatically generated.
> Storm Stack advisor should not make
> storm.topology.submission.notifier.plugin.class property required
> -
>
> Key: AMBARI-16915
> URL: https://issues.apache.org/jira/browse/AMBARI-16915
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Sivaguru Kannan
> Attachments: AMBARI-16915_branch-2.4.patch
>
>
> The Ambari change, This is in reference with the change,
> https://github.com/apache/ambari/commit/89fd30b40f3108bfcbcc73eb2d74c94a2ba14a7a
> which accidentally made the storm.topology.submission.notifier.plugin
> property mandatory.
> If the storm defaults yaml config does not set the property a " " value is
> set for the property. This causes storm startup to fail with a Class Not
> Found exception when starting with Ambari.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16942) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' confi
[ https://issues.apache.org/jira/browse/AMBARI-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305182#comment-15305182 ] Hudson commented on AMBARI-16942: - FAILURE: Integrated in Ambari-trunk-Commit #4948 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4948/]) AMBARI-16942. Take into account reading 'hive.tez.container.size', (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7b60113d1c076e0eb905c443a61cd837e11e72c6]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py > Take into account reading 'hive.tez.container.size', > 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' > & 'tez.am.resource.memory.mb' configs from configurations if they are changed > in current Stack Advisor invocation. > - > > Key: AMBARI-16942 > URL: https://issues.apache.org/jira/browse/AMBARI-16942 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16942.patch > > > - While doing Hive Server interactive's LLAP related calculations, take into > account reading 'hive-site/hive.tez.container.size', > 'yarn-site/yarn.scheduler.minimum-allocation-mb', > 'yarn-site/yarn.nodemanager.resource.memory-mb' and > 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in > current Stack Advisor invocation. Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16875) LDAP sync cannot handle if the member attribute value is not DN or id
[
https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305187#comment-15305187
]
Hadoop QA commented on AMBARI-16875:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806711/AMBARI-16875.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7044//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7044//console
This message is automatically generated.
> LDAP sync cannot handle if the member attribute value is not DN or id
> -
>
> Key: AMBARI-16875
> URL: https://issues.apache.org/jira/browse/AMBARI-16875
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16875.patch
>
>
> in case of member attribute value looks like this:
>
[jira] [Commented] (AMBARI-16917) Use postgres database instead of template1 during service check in HAWQ
[ https://issues.apache.org/jira/browse/AMBARI-16917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305084#comment-15305084 ] Hudson commented on AMBARI-16917: - FAILURE: Integrated in Ambari-trunk-Commit #4946 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4946/]) AMBARI-16917: Use postgres database instead of template1 during service (bhuvnesh2703: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c726fa5b649d4e0d3f0b00436d34bd19ea3e9a9e]) * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_segment_registration_status.py * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawq_constants.py * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/utils.py * ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/alerts/alert_sync_status.py > Use postgres database instead of template1 during service check in HAWQ > --- > > Key: AMBARI-16917 > URL: https://issues.apache.org/jira/browse/AMBARI-16917 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16917.patch > > > Use postgres database instead of template1 during service check in HAWQ. > template1 database is used as a default template while creating new > databases, so anything in template1 gets carried over to the new database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305085#comment-15305085 ] Hudson commented on AMBARI-16171: - FAILURE: Integrated in Ambari-trunk-Commit #4946 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4946/]) AMBARI-16171. Changes to Phoenix QueryServer Kerberos configuration (sgunturi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7d6c539c66fa96441aeafb8a70f9a6a255a9eb38]) * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/kerberos.json * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java AMBARI-16171. Changes to Phoenix QueryServer Kerberos configuration - (sgunturi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c5526333d28fbdec006536b9815ff924096f9da6]) * ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > Changes to Phoenix QueryServer Kerberos configuration > - > > Key: AMBARI-16171 > URL: https://issues.apache.org/jira/browse/AMBARI-16171 > Project: Ambari > Issue Type: Improvement >Reporter: Josh Elser >Assignee: Josh Elser > Fix For: 2.4.1 > > Attachments: AMBARI-16171-stackadvisor-WIP.patch, > AMBARI-16171.001.patch, AMBARI-16171.002.patch, AMBARI-16171.003.patch, > AMBARI-16171.006.patch, AMBARI-16171.007.patch, AMBARI-16171.009.patch, > AMBARI-16171.addendum.patch > > > The up-coming version of Phoenix will contain some new functionality to > support Kerberos authentication of clients via SPNEGO with the Phoenix Query > Server (PQS). > Presently, Ambari will configure PQS to use the hbase service keytab which > will result in the SPNEGO authentication failing as the RFC requires that the > "primary" component of the Kerberos principal for the server is "HTTP". Thus, > we need to ensure that we switch PQS over to use the spnego.service.keytab as > the keytab and "HTTP/_HOST@REALM" as the principal. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16942) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' configs
[ https://issues.apache.org/jira/browse/AMBARI-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16942: - Resolution: Fixed Status: Resolved (was: Patch Available) > Take into account reading 'hive.tez.container.size', > 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' > & 'tez.am.resource.memory.mb' configs from configurations if they are changed > in current Stack Advisor invocation. > - > > Key: AMBARI-16942 > URL: https://issues.apache.org/jira/browse/AMBARI-16942 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16942.patch > > > - While doing Hive Server interactive's LLAP related calculations, take into > account reading 'hive-site/hive.tez.container.size', > 'yarn-site/yarn.scheduler.minimum-allocation-mb', > 'yarn-site/yarn.nodemanager.resource.memory-mb' and > 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in > current Stack Advisor invocation. Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16913) Web Client Requests Handled By Jetty Should Not Be Blocked By JMX Property Providers
[
https://issues.apache.org/jira/browse/AMBARI-16913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305131#comment-15305131
]
Hadoop QA commented on AMBARI-16913:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806720/AMBARI-16913.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 6 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest
org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7041//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7041//console
This message is automatically generated.
> Web Client Requests Handled By Jetty Should Not Be Blocked By JMX Property
> Providers
>
>
> Key: AMBARI-16913
> URL: https://issues.apache.org/jira/browse/AMBARI-16913
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16913.patch
>
>
> Incoming requests from the web client (or from any REST API) will eventually
> be routed to the property provider / subresource framework. It is here were
> any JMX data is queried for within the context of the REST request. In large
> clusters, these requests can backup quite easily (even with a massive
> threadpool), causing UX degradations in the web client:
> {code}
> Thread [qtp-ambari-client-38]
>
> JMXPropertyProvider(ThreadPoolEnabledPropertyProvider).populateResources(Set,
> Request, Predicate) line: 168
> JMXPropertyProvider.populateResources(Set, Request,
> Predicate) line: 156
> StackDefinedPropertyProvider.populateResources(Set, Request,
> Predicate) line: 200
> ClusterControllerImpl.populateResources(Type, Set, Request,
> Predicate) line: 155
> QueryImpl.queryForResources() line: 407
> QueryImpl.execute() line: 217
> ReadHandler.handleRequest(Request) line: 69
> GetRequest(BaseRequest).process() line: 145
> {code}
> Consider one of the calls made by the web client:
> {code}
> GET api/v1/clusters/c1/components/?
> ServiceComponentInfo/category=MASTER&
> fields=
> ServiceComponentInfo/service_name,
> host_components/HostRoles/display_name,
> host_components/HostRoles/host_name,
> host_components/HostRoles/state,
> host_components/HostRoles/maintenance_state,
> host_components/HostRoles/stale_configs,
> host_components/HostRoles/ha_state,
> host_components/HostRoles/desired_admin_state,
> host_components/metrics/jvm/memHeapUsedM,
> host_components/metrics/jvm/HeapMemoryMax,
> host_components/metrics/jvm/HeapMemoryUsed,
> host_components/metrics/jvm/memHeapCommittedM,
> host_components/metrics/mapred/jobtracker/trackers_decommissioned,
> host_components/metrics/cpu/cpu_wio,
> host_components/metrics/rpc/client/RpcQueueTime_avg_time,
> host_components/metrics/dfs/FSNamesystem/*,
> host_components/metrics/dfs/namenode/Version,
> host_components/metrics/dfs/namenode/LiveNodes,
> host_components/metrics/dfs/namenode/DeadNodes,
> host_components/metrics/dfs/namenode/DecomNodes,
> host_components/metrics/dfs/namenode/TotalFiles,
> host_components/metrics/dfs/namenode/UpgradeFinalized,
> host_components/metrics/dfs/namenode/Safemode,
> host_components/metrics/runtime/StartTime
> {code}
> This query is essentially saying that for every {{MASTER}}, get metrics from
> them. The problem is that in a large cluster, there could be 100 masters, yet
> the metrics being asked for are only for NameNode. As a result, the JMX
> endpoints for all 100 masters are queried - *live* - as part of the request.
> There are two inherent flaws with this approach:
> - Even with millisecond JMX response times, multiplying this by 100's and
> then adding parsing overhead causes a noticeable delay in the web client as
> the federated requests are blocking the main UX request
> - Although there is a threadpool which scales up to service these requests -
> that only really works for 1 user. With multiple users logged in, you'd
[jira] [Commented] (AMBARI-16942) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' confi
[
https://issues.apache.org/jira/browse/AMBARI-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305111#comment-15305111
]
Swapan Shridhar commented on AMBARI-16942:
--
commits
trunk:
{code}
commit 7b60113d1c076e0eb905c443a61cd837e11e72c6
Author: Swapan Shridhar
Date: Fri May 27 16:26:35 2016 -0700
AMBARI-16942. Take into account reading 'hive.tez.container.size',
'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' &
'tez.am.resource.memory.mb' configs from configurations if they are changed in
current Stack Advisor invocation.
{code}
branch-2.4:
{code}
commit 8f353c9a898d530b39ce91fd19081620d4c5f175
Author: Swapan Shridhar
Date: Fri May 27 19:13:33 2016 -0700
AMBARI-16942. Take into account reading 'hive.tez.container.size',
'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' &
'tez.am.resource.memory.mb' configs from configurations if they are changed in
current Stack Advisor invocation
{code}
> Take into account reading 'hive.tez.container.size',
> 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb'
> & 'tez.am.resource.memory.mb' configs from configurations if they are changed
> in current Stack Advisor invocation.
> -
>
> Key: AMBARI-16942
> URL: https://issues.apache.org/jira/browse/AMBARI-16942
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16942.patch
>
>
> - While doing Hive Server interactive's LLAP related calculations, take into
> account reading 'hive-site/hive.tez.container.size',
> 'yarn-site/yarn.scheduler.minimum-allocation-mb',
> 'yarn-site/yarn.nodemanager.resource.memory-mb' and
> 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in
> current Stack Advisor invocation. Otherwise read from services array.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16942) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' configs
[ https://issues.apache.org/jira/browse/AMBARI-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16942: - Status: Patch Available (was: In Progress) > Take into account reading 'hive.tez.container.size', > 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' > & 'tez.am.resource.memory.mb' configs from configurations if they are changed > in current Stack Advisor invocation. > - > > Key: AMBARI-16942 > URL: https://issues.apache.org/jira/browse/AMBARI-16942 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16942.patch > > > - While doing Hive Server interactive's LLAP related calculations, take into > account reading 'hive-site/hive.tez.container.size', > 'yarn-site/yarn.scheduler.minimum-allocation-mb', > 'yarn-site/yarn.nodemanager.resource.memory-mb' and > 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in > current Stack Advisor invocation. Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16932) Atlas server start failed after Ambari upgrade due to missing solrCloudCli.sh script
[
https://issues.apache.org/jira/browse/AMBARI-16932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-16932:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Atlas server start failed after Ambari upgrade due to missing solrCloudCli.sh
> script
>
>
> Key: AMBARI-16932
> URL: https://issues.apache.org/jira/browse/AMBARI-16932
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
>
> *Steps*
> # Deploy HDP-2.4.2.0 cluster with Ambari 2.2.2.0 (including Atlas)
> # Upgrade Ambari to 2.4.0.0
> # Stop and start all services
> *Result*
> Atlas Metadata server start fails with below error:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 165, in
> MetadataServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 257, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 67, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata_server.py",
> line 51, in configure
> metadata()
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 113, in metadata
> upload_conf_set('basic_configs', random_num)
> File
> "/var/lib/ambari-agent/cache/common-services/ATLAS/0.1.0.2.3/package/scripts/metadata.py",
> line 135, in upload_conf_set
> group=params.user_group)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/solr_cloud_util.py",
> line 48, in upload_configuration_to_zk
> group=group
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> JAVA_HOME=/usr/jdk64/jdk1.7.0_67 ;
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh -z
> os-r6-tgvuks-dgm10toeriedwngdha-r6-4.openstacklocal:2181,os-r6-tgvuks-dgm10toeriedwngdha-r6-3.openstacklocal:2181,os-r6-tgvuks-dgm10toeriedwngdha-r6-2.openstacklocal:2181None
> --upload-config -d
> /usr/lib/ambari-logsearch-solr/server/solr/configsets/basic_configs/conf -cs
> basic_configs -rt 5 -i 10' returned 127. -bash:
> /usr/lib/ambari-logsearch-solr-client/solrCloudCli.sh: No such file or
> directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16942) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' configs
Swapan Shridhar created AMBARI-16942: Summary: Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' configs from configurations if they are changed in current Stack Advisor invocation. Key: AMBARI-16942 URL: https://issues.apache.org/jira/browse/AMBARI-16942 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Swapan Shridhar Assignee: Swapan Shridhar Priority: Critical Fix For: 2.4.0 - While doing Hive Server interactive's LLAP related calculations, take into account reading 'hive-site/hive.tez.container.size', 'yarn-site/yarn.scheduler.minimum-allocation-mb', 'yarn-site/yarn.nodemanager.resource.memory-mb' and 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in current Stack Advisor invocation. Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16755) Add spark.driver.extraLibraryPath & spark.executor.extraLibraryPath to spark-defaults.conf
[ https://issues.apache.org/jira/browse/AMBARI-16755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304996#comment-15304996 ] Hudson commented on AMBARI-16755: - FAILURE: Integrated in Ambari-trunk-Commit #4945 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4945/]) AMBARI-16755. Add spark.driver.extraLibraryPath (Weiqing Yang via (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=048ef3fa61be82fdae795c6c466d60c053b1f8f2]) * ambari-server/src/main/resources/common-services/SPARK2/2.0.0/package/scripts/params.py * ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-defaults.xml * ambari-server/src/main/resources/common-services/SPARK/1.2.1/configuration/spark-defaults.xml * ambari-server/src/main/resources/common-services/SPARK2/2.0.0/configuration/spark2-thrift-sparkconf.xml * ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/params.py * ambari-server/src/main/resources/common-services/SPARK/1.5.2/configuration/spark-thrift-sparkconf.xml > Add spark.driver.extraLibraryPath & spark.executor.extraLibraryPath to > spark-defaults.conf > -- > > Key: AMBARI-16755 > URL: https://issues.apache.org/jira/browse/AMBARI-16755 > Project: Ambari > Issue Type: Improvement > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Weiqing Yang > Fix For: 2.4.0 > > Attachments: AMBARI-16755-1.patch, AMBARI-16755_2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16887) [AMS / Grafana] Metrics are staying flat for 1 minutes, causing rate calculations to be 0
[ https://issues.apache.org/jira/browse/AMBARI-16887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304995#comment-15304995 ] Hudson commented on AMBARI-16887: - FAILURE: Integrated in Ambari-trunk-Commit #4945 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4945/]) AMBARI-16887 : [AMS / Grafana] Metrics are staying flat for 1 minutes, (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=489a9c4b0835558669ab30b0cfda68b60c8a238c]) * ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecondTest.java * ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/PostProcessingUtil.java * ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/PostProcessingUtilTest.java * ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * ambari-metrics/ambari-metrics-common/pom.xml > [AMS / Grafana] Metrics are staying flat for 1 minutes, causing rate > calculations to be 0 > - > > Key: AMBARI-16887 > URL: https://issues.apache.org/jira/browse/AMBARI-16887 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16887.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-16921) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' config
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reassigned AMBARI-16921: Assignee: Swapan Shridhar (was: Daniel Gergely) > Take into account reading 'hive.tez.container.size', > 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' > & 'tez.am.resource.memory.mb' configs from configurations if they are changed > in current Stack Advisor invocation. > - > > Key: AMBARI-16921 > URL: https://issues.apache.org/jira/browse/AMBARI-16921 > Project: Ambari > Issue Type: Bug >Reporter: Daniel Gergely >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > - While doing Hive Server interactive's LLAP related calculations, take into > account reading 'hive-site/hive.tez.container.size', > 'yarn-site/yarn.scheduler.minimum-allocation-mb', > 'yarn-site/yarn.nodemanager.resource.memory-mb' and > 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in > current Stack Advisor invocation. Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16921) Incorrect reading of 'yarn minimum container size' property from services as it may have changed in current Stack Advisor invocation
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - Description: - idea is to take into account reading from configurations. If its not there then rad from services. (was: - While doing Hive Server interactive's LLAP related calculations, take into account reading 'hive-site/hive.tez.container.size', 'yarn-site/yarn.scheduler.minimum-allocation-mb', 'yarn-site/yarn.nodemanager.resource.memory-mb' and 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in current Stack Advisor invocation. Otherwise read from services array. ) Summary: Incorrect reading of 'yarn minimum container size' property from services as it may have changed in current Stack Advisor invocation (was: Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' configs from configurations if they are changed in current Stack Advisor invocation.) > Incorrect reading of 'yarn minimum container size' property from services as > it may have changed in current Stack Advisor invocation > > > Key: AMBARI-16921 > URL: https://issues.apache.org/jira/browse/AMBARI-16921 > Project: Ambari > Issue Type: Bug >Reporter: Daniel Gergely >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > - idea is to take into account reading from configurations. If its not there > then rad from services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16942) Take into account reading 'hive.tez.container.size', 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' & 'tez.am.resource.memory.mb' configs
[ https://issues.apache.org/jira/browse/AMBARI-16942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16942: - Attachment: AMBARI-16942.patch > Take into account reading 'hive.tez.container.size', > 'yarn.scheduler.minimum-allocation-mb', 'yarn.nodemanager.resource.memory-mb' > & 'tez.am.resource.memory.mb' configs from configurations if they are changed > in current Stack Advisor invocation. > - > > Key: AMBARI-16942 > URL: https://issues.apache.org/jira/browse/AMBARI-16942 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16942.patch > > > - While doing Hive Server interactive's LLAP related calculations, take into > account reading 'hive-site/hive.tez.container.size', > 'yarn-site/yarn.scheduler.minimum-allocation-mb', > 'yarn-site/yarn.nodemanager.resource.memory-mb' and > 'tez-interactive-site/tez.am.resource.memory.mb' if they are changed in > current Stack Advisor invocation. Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16437) Add conditional constraints for Kerberos identities to control when they are created
[
https://issues.apache.org/jira/browse/AMBARI-16437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16437:
--
Attachment: AMBARI-16437_trunk_03.patch
> Add conditional constraints for Kerberos identities to control when they are
> created
>
>
> Key: AMBARI-16437
> URL: https://issues.apache.org/jira/browse/AMBARI-16437
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.4.0
>
> Attachments: AMBARI-16437_trunk_01.patch,
> AMBARI-16437_trunk_02.patch, AMBARI-16437_trunk_03.patch
>
>
> Add conditional constraints for Kerberos identities to control when they are
> created. For example if Kerberos Identity should only be created (and
> distributed) for a component when some other component or service is
> installed.
> An example of this would be
> {code}
> {
> "name": "/HIVE/HIVE_SERVER/hive_server_hive",
> "principal": {
> "configuration":
> "hive-interactive-site/hive.llap.daemon.service.principal"
> },
> "keytab": {
> "configuration": "hive-interactive-site/hive.llap.daemon.keytab.file"
> },
> "when" : {
> "contains" : ["services", "HIVE"]
> }
> }
> {code}
> Note the "{{when}}" clause. This indicates that this identity should only be
> processed when the set of services contains "HIVE". An alternative to this
> would be to test the set of components for a certain component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16939) 'ambari-server upgrade' is failed : Error executing schema upgrade [upgrade from 2200 to 2400]
[
https://issues.apache.org/jira/browse/AMBARI-16939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305039#comment-15305039
]
Hadoop QA commented on AMBARI-16939:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806727/patch2-trunk.diff
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.stack.ConfigUpgradeValidityTest
org.apache.ambari.server.controller.internal.HostResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7039//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7039//console
This message is automatically generated.
> 'ambari-server upgrade' is failed : Error executing schema upgrade [upgrade
> from 2200 to 2400]
> --
>
> Key: AMBARI-16939
> URL: https://issues.apache.org/jira/browse/AMBARI-16939
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: patch2-trunk.diff
>
>
> STR:
> 1) Install old version
> 2) Try to Make ambari only upgrade
> Cluster: 172.22.123.240
> All logs:
> http://qelog.hortonworks.com/log/os-u14-xvenls-upg-sanity-u-2200/test-logs/ambari-upgrade-2.2.0.0/
> Actual result:
> 'ambari-server upgrade' is failed : Error executing schema upgrade [upgrade
> from 2200 to 2400]
> {code}
> 2016-05-19 04:50:31,348 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> Sending command []
> 2016-05-19 04:50:31,950 DEBUG
> com.hw.ambari.ui.util.cluster_managers.ProcessData.buildOutputAndErrorStreamData():
> stdin: is not a tty
> 2016-05-19 04:50:49,791 INFO
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Cannot
> add foreign key constraint
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:204)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:302)
> Caused by: java.sql.SQLException: Cannot
[jira] [Updated] (AMBARI-16940) VDF: support for selecting enabled + default Stacks
[ https://issues.apache.org/jira/browse/AMBARI-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16940: Description: The work revamps the UX for leveraging VDF(Version Definition File) feature of ambari. was: Tested ambari-web and ambari-admin view manually: Verified that unit tests for ambari-web and ambari-admin passes successfully ambari-web: 27900 tests complete (29 seconds) 154 tests pending ambari-admin: phantomJS 1.9.7 (Mac OS X): Executed 71 of 71 SUCCESS (0.467 secs / 0.454 secs) > VDF: support for selecting enabled + default Stacks > --- > > Key: AMBARI-16940 > URL: https://issues.apache.org/jira/browse/AMBARI-16940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-16940.patch > > > The work revamps the UX for leveraging VDF(Version Definition File) feature > of ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16940) VDF: support for selecting enabled + default Stacks
[ https://issues.apache.org/jira/browse/AMBARI-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16940: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on ReviewBoard. Patch committed to trunk and branch-2.4 > VDF: support for selecting enabled + default Stacks > --- > > Key: AMBARI-16940 > URL: https://issues.apache.org/jira/browse/AMBARI-16940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-16940.patch > > > Tested ambari-web and ambari-admin view manually: > Verified that unit tests for ambari-web and ambari-admin passes successfully > ambari-web: > 27900 tests complete (29 seconds) > 154 tests pending > ambari-admin: > phantomJS 1.9.7 (Mac OS X): Executed 71 of 71 SUCCESS (0.467 secs / 0.454 > secs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16940) VDF: support for selecting enabled + default Stacks
[ https://issues.apache.org/jira/browse/AMBARI-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-16940: Status: Patch Available (was: Open) > VDF: support for selecting enabled + default Stacks > --- > > Key: AMBARI-16940 > URL: https://issues.apache.org/jira/browse/AMBARI-16940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-16940.patch > > > Tested ambari-web and ambari-admin view manually: > Verified that unit tests for ambari-web and ambari-admin passes successfully > ambari-web: > 27900 tests complete (29 seconds) > 154 tests pending > ambari-admin: > phantomJS 1.9.7 (Mac OS X): Executed 71 of 71 SUCCESS (0.467 secs / 0.454 > secs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16940) VDF: support for selecting enabled + default Stacks
[ https://issues.apache.org/jira/browse/AMBARI-16940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305045#comment-15305045 ] Jaimin D Jetly commented on AMBARI-16940: - Tested ambari-web and ambari-admin view manually: Verified that unit tests for ambari-web and ambari-admin passes successfully ambari-web: 27900 tests complete (29 seconds) 154 tests pending ambari-admin: phantomJS 1.9.7 (Mac OS X): Executed 71 of 71 SUCCESS (0.467 secs / 0.454 secs) > VDF: support for selecting enabled + default Stacks > --- > > Key: AMBARI-16940 > URL: https://issues.apache.org/jira/browse/AMBARI-16940 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-16940.patch > > > Tested ambari-web and ambari-admin view manually: > Verified that unit tests for ambari-web and ambari-admin passes successfully > ambari-web: > 27900 tests complete (29 seconds) > 154 tests pending > ambari-admin: > phantomJS 1.9.7 (Mac OS X): Executed 71 of 71 SUCCESS (0.467 secs / 0.454 > secs) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16906) Express upgrade: Oozie failed to start when user name and group are none-default values
[
https://issues.apache.org/jira/browse/AMBARI-16906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303749#comment-15303749
]
Hadoop QA commented on AMBARI-16906:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806442/AMBARI-16906.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/7008//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7008//console
This message is automatically generated.
> Express upgrade: Oozie failed to start when user name and group are
> none-default values
> ---
>
> Key: AMBARI-16906
> URL: https://issues.apache.org/jira/browse/AMBARI-16906
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-16906.patch
>
>
> oozie_server_upgrade.py has hardcoded user name to oozie and group to hadoop.
> Both values should have been pulled from params.py
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16923) AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config Property Attributes updated if there is a change in 'capacity-scheduler'.
[ https://issues.apache.org/jira/browse/AMBARI-16923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16923: - Priority: Critical (was: Major) > AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config > Property Attributes updated if there is a change in 'capacity-scheduler'. > > > Key: AMBARI-16923 > URL: https://issues.apache.org/jira/browse/AMBARI-16923 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
[
https://issues.apache.org/jira/browse/AMBARI-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-16020:
--
Attachment: AMBARI-16020_2.patch
> Hive Metastore install failed since mysql-server not installed
> --
>
> Key: AMBARI-16020
> URL: https://issues.apache.org/jira/browse/AMBARI-16020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16020.patch, AMBARI-16020_2.patch
>
>
> STR:
> * Install Ambari 2.4.0.0-4686 on 3 hosts
> * Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
> other
> * Select option to install Hive with "New MySQL" database
> Failed installing Hive Metastore since MySQL service was not installed.
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
> launch YARN applications.
> Metastore connection URL:
> jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> *** schemaTool failed ***
> {code}
> I had to run this manually,
> {code}
> yum install mysql-server -y
> service mysqld start
> mysql -u root -p (password is empty string)
> mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
> IDENTIFIED BY 'admin' WITH GRANT OPTION;
> Query OK, 0 rows affected (0.00 sec)
> mysql> flush privileges;
> Query OK, 0 rows affected (0.00 sec)
> {code}
> and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16020) Hive Metastore install failed since mysql-server not installed
[
https://issues.apache.org/jira/browse/AMBARI-16020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-16020:
--
Status: Patch Available (was: Reopened)
> Hive Metastore install failed since mysql-server not installed
> --
>
> Key: AMBARI-16020
> URL: https://issues.apache.org/jira/browse/AMBARI-16020
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16020.patch, AMBARI-16020_2.patch
>
>
> STR:
> * Install Ambari 2.4.0.0-4686 on 3 hosts
> * Install HDP 2.5.0.0-58 with Hive Server on 1 host and Hive Metastore on the
> other
> * Select option to install Hive with "New MySQL" database
> Failed installing Hive Metastore since MySQL service was not installed.
> {code}
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 293, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-metastore/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED]' returned 1. WARNING: Use "yarn jar" to
> launch YARN applications.
> Metastore connection URL:
> jdbc:mysql://c6405.ambari.apache.org/hive?createDatabaseIfNotExist=true
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> *** schemaTool failed ***
> {code}
> I had to run this manually,
> {code}
> yum install mysql-server -y
> service mysqld start
> mysql -u root -p (password is empty string)
> mysql> CREATE USER 'hive'@'%' IDENTIFIED BY 'admin';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'%';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'localhost';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org';
> Query OK, 0 rows affected (0.00 sec)
> mysql> GRANT ALL PRIVILEGES ON *.* TO 'hive'@'c6405.ambari.apache.org'
> IDENTIFIED BY 'admin' WITH GRANT OPTION;
> Query OK, 0 rows affected (0.00 sec)
> mysql> flush privileges;
> Query OK, 0 rows affected (0.00 sec)
> {code}
> and then try the Start again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16923) AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config Property Attributes updated if there is a change in 'capacity-scheduler'.
[ https://issues.apache.org/jira/browse/AMBARI-16923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16923: - Summary: AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config Property Attributes updated if there is a change in 'capacity-scheduler'. (was: Fixing for getting the 'hive.llap.daemon.queue.name' config Property Attributes getting updated is there is a change in 'capacity-scheduler'. ) > AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config > Property Attributes updated if there is a change in 'capacity-scheduler'. > > > Key: AMBARI-16923 > URL: https://issues.apache.org/jira/browse/AMBARI-16923 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16896) It is possible to save service configs changes without applying config dependencies
[ https://issues.apache.org/jira/browse/AMBARI-16896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-16896: - Resolution: Fixed Status: Resolved (was: Patch Available) > It is possible to save service configs changes without applying config > dependencies > > > Key: AMBARI-16896 > URL: https://issues.apache.org/jira/browse/AMBARI-16896 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16896.patch > > > Warning popup about configuration dependencies appears with delay after > config changing. So user can save and confirm changes before appearing > warning popup about dependencies and without checking and applying them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16927) Canceling "Select HS2 Interactive" popup does not trigger recommendation call
Andrii Babiichuk created AMBARI-16927: - Summary: Canceling "Select HS2 Interactive" popup does not trigger recommendation call Key: AMBARI-16927 URL: https://issues.apache.org/jira/browse/AMBARI-16927 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.4.0 *STR:* # Deploy a cluster with hive service # Enable interactive query on hive service config page # This will trigger recommendation API call # This will aslo show "Select HiveServer2 Interactive" host popup # Click on cancel button shown on this popup # This will again disable interactive query *Expected Result:* When "Enable interactive query" config is changed from yes to no on lciking cancel button, recommendation API call should be again made *Actual Result:* No recommendation call is made and so incorrect recommendation remains and eventually gets saved by the user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16918) Create management-pack for Microsoft-R service
[
https://issues.apache.org/jira/browse/AMBARI-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304076#comment-15304076
]
Hadoop QA commented on AMBARI-16918:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806531/AMBARI-16918.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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
contrib/management-packs/microsoft-r_mpack.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7017//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7017//console
This message is automatically generated.
> Create management-pack for Microsoft-R service
> --
>
> Key: AMBARI-16918
> URL: https://issues.apache.org/jira/browse/AMBARI-16918
> Project: Ambari
> Issue Type: Task
> Components: contrib
>Affects Versions: 2.4.0
>Reporter: Srimanth Gunturi
>Assignee: Srimanth Gunturi
> Fix For: 2.4.1
>
> Attachments: AMBARI-16918.patch
>
>
> Create a management pack for Microsoft-R service using the design document at
> [https://issues.apache.org/jira/secure/attachment/12795046/ApacheAmbariManagementPacks.pdf]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16929) Automatically cleanup /var/run/ambari-server/stack-recommendations
[ https://issues.apache.org/jira/browse/AMBARI-16929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16929: - Attachment: AMBARI-16929.patch > Automatically cleanup /var/run/ambari-server/stack-recommendations > -- > > Key: AMBARI-16929 > URL: https://issues.apache.org/jira/browse/AMBARI-16929 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16929.patch > > > In clusters with many nodes and thousands of processes running > /var/run/ambari-server/stack-recommendations folder gets filled up and not > cleaned till ambari-server is restarted. > Disk is getting filled up causing space issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16929) Automatically cleanup /var/run/ambari-server/stack-recommendations
Andrew Onischuk created AMBARI-16929: Summary: Automatically cleanup /var/run/ambari-server/stack-recommendations Key: AMBARI-16929 URL: https://issues.apache.org/jira/browse/AMBARI-16929 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-16929.patch In clusters with many nodes and thousands of processes running /var/run/ambari-server/stack-recommendations folder gets filled up and not cleaned till ambari-server is restarted. Disk is getting filled up causing space issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16743) clean up import * for RANGER service
[
https://issues.apache.org/jira/browse/AMBARI-16743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304049#comment-15304049
]
Hadoop QA commented on AMBARI-16743:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806494/AMBARI-16743.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/7015//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7015//console
This message is automatically generated.
> clean up import * for RANGER service
>
>
> Key: AMBARI-16743
> URL: https://issues.apache.org/jira/browse/AMBARI-16743
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-agent, ambari-server
>Affects Versions: 2.1.0, 2.2.0, 2.4.0
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 3.0.0
>
> Attachments: AMBARI-16743.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16927) Canceling "Select HS2 Interactive" popup does not trigger recommendation call
[ https://issues.apache.org/jira/browse/AMBARI-16927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304044#comment-15304044 ] Aleksandr Kovalenko commented on AMBARI-16927: -- +1 for the patch > Canceling "Select HS2 Interactive" popup does not trigger recommendation call > - > > Key: AMBARI-16927 > URL: https://issues.apache.org/jira/browse/AMBARI-16927 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16927.patch > > > *STR:* > # Deploy a cluster with hive service > # Enable interactive query on hive service config page > # This will trigger recommendation API call > # This will aslo show "Select HiveServer2 Interactive" host popup > # Click on cancel button shown on this popup > # This will again disable interactive query > *Expected Result:* When "Enable interactive query" config is changed from yes > to no on lciking cancel button, recommendation API call should be again made > *Actual Result:* No recommendation call is made and so incorrect > recommendation remains and eventually gets saved by the user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16437) Add conditional constraints for Kerberos identities to control when they are created
[
https://issues.apache.org/jira/browse/AMBARI-16437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16437:
--
Attachment: AMBARI-16851_trunk_02.patch
> Add conditional constraints for Kerberos identities to control when they are
> created
>
>
> Key: AMBARI-16437
> URL: https://issues.apache.org/jira/browse/AMBARI-16437
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.4.0
>
> Attachments: AMBARI-16437_trunk_01.patch
>
>
> Add conditional constraints for Kerberos identities to control when they are
> created. For example if Kerberos Identity should only be created (and
> distributed) for a component when some other component or service is
> installed.
> An example of this would be
> {code}
> {
> "name": "/HIVE/HIVE_SERVER/hive_server_hive",
> "principal": {
> "configuration":
> "hive-interactive-site/hive.llap.daemon.service.principal"
> },
> "keytab": {
> "configuration": "hive-interactive-site/hive.llap.daemon.keytab.file"
> },
> "when" : {
> "contains" : ["services", "HIVE"]
> }
> }
> {code}
> Note the "{{when}}" clause. This indicates that this identity should only be
> processed when the set of services contains "HIVE". An alternative to this
> would be to test the set of components for a certain component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16437) Add conditional constraints for Kerberos identities to control when they are created
[
https://issues.apache.org/jira/browse/AMBARI-16437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-16437:
--
Attachment: (was: AMBARI-16851_trunk_02.patch)
> Add conditional constraints for Kerberos identities to control when they are
> created
>
>
> Key: AMBARI-16437
> URL: https://issues.apache.org/jira/browse/AMBARI-16437
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.4.0
>
> Attachments: AMBARI-16437_trunk_01.patch
>
>
> Add conditional constraints for Kerberos identities to control when they are
> created. For example if Kerberos Identity should only be created (and
> distributed) for a component when some other component or service is
> installed.
> An example of this would be
> {code}
> {
> "name": "/HIVE/HIVE_SERVER/hive_server_hive",
> "principal": {
> "configuration":
> "hive-interactive-site/hive.llap.daemon.service.principal"
> },
> "keytab": {
> "configuration": "hive-interactive-site/hive.llap.daemon.keytab.file"
> },
> "when" : {
> "contains" : ["services", "HIVE"]
> }
> }
> {code}
> Note the "{{when}}" clause. This indicates that this identity should only be
> processed when the set of services contains "HIVE". An alternative to this
> would be to test the set of components for a certain component.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Attachment: AMBARI-12885 Example.pdf > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v4.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16866) View Config-Non remote user able to edit queue settings in remote capacity schedular view
[ https://issues.apache.org/jira/browse/AMBARI-16866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-16866: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > View Config-Non remote user able to edit queue settings in remote capacity > schedular view > - > > Key: AMBARI-16866 > URL: https://issues.apache.org/jira/browse/AMBARI-16866 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: ambari-2.4.0 >Reporter: Gaurav Nagar >Assignee: Gaurav Nagar > Fix For: ambari-2.4.0 > > Attachments: AMBARI-16866_branch-2.4.patch > > > Remote Cluster -A1 > Views Cluster-A2 > Capacity scheduler view for A1 is configured in A2 > Created user1 in A2 with view user permission. user1 is not present in A1. > user1 is able to edit queue configs from the remote view -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16901) Add Service wizard: All kerberos related configurations shown on Configure Identities page should be made non-editable on configure services page
[ https://issues.apache.org/jira/browse/AMBARI-16901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304045#comment-15304045 ] Aleksandr Kovalenko commented on AMBARI-16901: -- +1 for the patch > Add Service wizard: All kerberos related configurations shown on Configure > Identities page should be made non-editable on configure services page > - > > Key: AMBARI-16901 > URL: https://issues.apache.org/jira/browse/AMBARI-16901 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16901.patch > > > If following conditions are met then config should be made non-editable on > configure->services page: > Cluster is kerberized > Kerberos is ambari managed meaning not manual > Config is stated as an identity in the kerberos descriptor posted to the > cluster (api/v1/clusters/c1/artifacts/kerberos_descriptor). Note that config > has to be an identity to be made non-editable. Note: Other configs mentioned > in the kerberos descriptor should not be made non-editable. Only configs > stated under identities array should be made non-editable. > Configs made non-editable due to satisfying above condition should have their > description appended with the text that "This config can be changed from > Kerberos page under Admin tab by privileged users." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16851) Cluster operator and cluster admin not allowed to install ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-16851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-16851: -- Attachment: AMBARI-16851_trunk_02.patch > Cluster operator and cluster admin not allowed to install ambari agent > -- > > Key: AMBARI-16851 > URL: https://issues.apache.org/jira/browse/AMBARI-16851 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: rbac > Fix For: 2.4.0 > > Attachments: AMBARI-16851_trunk_01.patch, AMBARI-16851_trunk_02.patch > > > Cluster operator and the cluster admin must be allowed to add/delete hosts > but install of agents using /bootstrap fails with 403 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16926) Add ability to query all hosts using hostname=% through AMS API.
[
https://issues.apache.org/jira/browse/AMBARI-16926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304023#comment-15304023
]
Dmytro Sen commented on AMBARI-16926:
-
Unit tests passed locally
{code]
[INFO] Reactor Summary:
[INFO]
[INFO] ambari-metrics . SUCCESS [ 1.041 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 4.226 s]
[INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 4.857 s]
[INFO] Ambari Metrics Flume Sink .. SUCCESS [ 2.434 s]
[INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 3.550 s]
[INFO] Ambari Metrics Storm Sink .. SUCCESS [ 1.208 s]
[INFO] Ambari Metrics Collector ... SUCCESS [04:05 min]
[INFO] Ambari Metrics Monitor . SUCCESS [ 1.147 s]
[INFO] Ambari Metrics Grafana . SUCCESS [ 29.393 s]
[INFO] Ambari Metrics Assembly SUCCESS [02:47 min]
[INFO]
[INFO] BUILD SUCCESS
{code}
> Add ability to query all hosts using hostname=% through AMS API.
>
>
> Key: AMBARI-16926
> URL: https://issues.apache.org/jira/browse/AMBARI-16926
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16926.patch
>
>
> Useful for Top N feature
> Add ability to query all hosts using hostname=%.my.com through AMS API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16428) Hive view : Upload table view throws exception but does not shows what is wrong with the submitted table creation.
[ https://issues.apache.org/jira/browse/AMBARI-16428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-16428: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch-2.4 > Hive view : Upload table view throws exception but does not shows what is > wrong with the submitted table creation. > -- > > Key: AMBARI-16428 > URL: https://issues.apache.org/jira/browse/AMBARI-16428 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.2 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.4.0 > > Attachments: AMBARI-16428_branch-2.4.patch, Screen Shot 2016-04-18 at > 2.52.37 PM.png, Screen Shot 2016-04-18 at 2.53.08 PM.png > > > For the following validation errors, Upload table view shows > HiveClientFormattedException > 1. Column datatype is set to char, but precision is not set. > 2. Table name is not valid (has characters like '-') > 3. Creating a table with duplicate table name. > 4. When column name is missing in xml tag > No validation error is shown in this case. > PFA screenshot. > For #3, When creating a table with duplicate name on hive query tab shows > proper error "Error while processing statement: FAILED: Execution Error, > return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. > AlreadyExistsException(message:Table data3 already exists)" > The same on Upload Table just shows "HiveClientFormattedException" > For#4 When column name is missing in the xml, hive view log shows exception " > java.lang.IllegalArgumentException: Missing name attribute in col > tag.java.lang.IllegalArgumentException: Missing name attribute in col tag." > But Upload table UI shows : > org.apache.ambari.view.hive.utils.ServiceFormattedException > at > org.apache.ambari.view.hive.resources.uploads.UploadService.uploadIntoTable(UploadService.java:282) > at > org.apache.ambari.view.hive.resources.uploads.UploadService.uploadFileFromStream(UploadService.java:401) > at > org.apache.ambari.view.hive.resources.uploads.UploadService.uploadFile(UploadService.java:212) > at sun.reflect.GeneratedMethodAccessor1233.invoke(Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16927) Canceling "Select HS2 Interactive" popup does not trigger recommendation call
[ https://issues.apache.org/jira/browse/AMBARI-16927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16927: -- Attachment: AMBARI-16927.patch > Canceling "Select HS2 Interactive" popup does not trigger recommendation call > - > > Key: AMBARI-16927 > URL: https://issues.apache.org/jira/browse/AMBARI-16927 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16927.patch > > > *STR:* > # Deploy a cluster with hive service > # Enable interactive query on hive service config page > # This will trigger recommendation API call > # This will aslo show "Select HiveServer2 Interactive" host popup > # Click on cancel button shown on this popup > # This will again disable interactive query > *Expected Result:* When "Enable interactive query" config is changed from yes > to no on lciking cancel button, recommendation API call should be again made > *Actual Result:* No recommendation call is made and so incorrect > recommendation remains and eventually gets saved by the user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16927) Canceling "Select HS2 Interactive" popup does not trigger recommendation call
[ https://issues.apache.org/jira/browse/AMBARI-16927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16927: -- Status: Patch Available (was: Open) 27859 tests complete (22 seconds) 154 tests pending > Canceling "Select HS2 Interactive" popup does not trigger recommendation call > - > > Key: AMBARI-16927 > URL: https://issues.apache.org/jira/browse/AMBARI-16927 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16927.patch > > > *STR:* > # Deploy a cluster with hive service > # Enable interactive query on hive service config page > # This will trigger recommendation API call > # This will aslo show "Select HiveServer2 Interactive" host popup > # Click on cancel button shown on this popup > # This will again disable interactive query > *Expected Result:* When "Enable interactive query" config is changed from yes > to no on lciking cancel button, recommendation API call should be again made > *Actual Result:* No recommendation call is made and so incorrect > recommendation remains and eventually gets saved by the user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Status: Open (was: Patch Available) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885.patch, Dynamic Stack Extensions - High > Level Design v4.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Attachment: (was: AMBARI-12885.patch) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885.patch, Dynamic Stack Extensions - High > Level Design v4.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16821) Improve TimelineMetricsCache eviction/flush logic using a cache library
[ https://issues.apache.org/jira/browse/AMBARI-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16821: Attachment: AMBARI-16821_2.patch > Improve TimelineMetricsCache eviction/flush logic using a cache library > --- > > Key: AMBARI-16821 > URL: https://issues.apache.org/jira/browse/AMBARI-16821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16821_1.patch, AMBARI-16821_2.patch > > > The TimelineMetricsCache implementation in the metrics sink side is currently > a ConcurrentSkipListMap. It is better to use pre built cache libraries like > Guava that offer more support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16821) Improve TimelineMetricsCache eviction/flush logic using a cache library
[ https://issues.apache.org/jira/browse/AMBARI-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16821: Status: Patch Available (was: Open) > Improve TimelineMetricsCache eviction/flush logic using a cache library > --- > > Key: AMBARI-16821 > URL: https://issues.apache.org/jira/browse/AMBARI-16821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16821_1.patch, AMBARI-16821_2.patch > > > The TimelineMetricsCache implementation in the metrics sink side is currently > a ConcurrentSkipListMap. It is better to use pre built cache libraries like > Guava that offer more support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16929) Automatically cleanup /var/run/ambari-server/stack-recommendations
[ https://issues.apache.org/jira/browse/AMBARI-16929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16929: - Status: Patch Available (was: Open) > Automatically cleanup /var/run/ambari-server/stack-recommendations > -- > > Key: AMBARI-16929 > URL: https://issues.apache.org/jira/browse/AMBARI-16929 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16929.patch > > > In clusters with many nodes and thousands of processes running > /var/run/ambari-server/stack-recommendations folder gets filled up and not > cleaned till ambari-server is restarted. > Disk is getting filled up causing space issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16928) Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade
Antonenko Alexander created AMBARI-16928: Summary: Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade Key: AMBARI-16928 URL: https://issues.apache.org/jira/browse/AMBARI-16928 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.4.0 STR: # Start Rolling upgrade # Try to navigate to "Service Accounts" and "Kerberos" tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-12885: Status: Patch Available (was: Open) > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v4.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16928) Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16928: - Status: Patch Available (was: Open) > Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade > --- > > Key: AMBARI-16928 > URL: https://issues.apache.org/jira/browse/AMBARI-16928 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-16928.patch > > > STR: > # Start Rolling upgrade > # Try to navigate to "Service Accounts" and "Kerberos" tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
[ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304114#comment-15304114 ] Tim Thorpe commented on AMBARI-12885: - [~mithmatt] I added a new patch which successfully applies over yesterday's trunk. I will test it again soon. I also added some instructions on how to set up an extension and run the REST API commands to hook everything up. It really isn't very complicated except for adding a new repo. Really that is something which should be added in the UI to simplify things but I'm not very familiar with the Ambari UI code. > Dynamic stack extensions - install and upgrade support for custom services > -- > > Key: AMBARI-12885 > URL: https://issues.apache.org/jira/browse/AMBARI-12885 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, ambari-server, ambari-web >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic > Stack Extensions - High Level Design v4.pdf > > > The purpose of this proposal is to facilitate adding custom services to an > existing stack. Ideally this would support adding and upgrading custom > services separately from the core services defined in the stack. In > particular we are looking at custom services that need to support several > different stacks (different distributions of Ambari). The release cycle of > the custom services may be different from that of the core stack; that is, a > custom service may be upgraded at a different rate than the core distribution > itself and may be upgraded multiple times within the lifespan of a single > release of the core distribution. > One possible approach to handling this would be dynamically extending a stack > (after install time). It would be best to extend the stack in packages where > a stack extension package can have one or more custom services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16928) Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-16928: - Attachment: AMBARI-16928.patch > Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade > --- > > Key: AMBARI-16928 > URL: https://issues.apache.org/jira/browse/AMBARI-16928 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-16928.patch > > > STR: > # Start Rolling upgrade > # Try to navigate to "Service Accounts" and "Kerberos" tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16928) Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304116#comment-15304116 ] Aleksandr Kovalenko commented on AMBARI-16928: -- +1 for the patch > Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade > --- > > Key: AMBARI-16928 > URL: https://issues.apache.org/jira/browse/AMBARI-16928 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-16928.patch > > > STR: > # Start Rolling upgrade > # Try to navigate to "Service Accounts" and "Kerberos" tab -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16821) Improve TimelineMetricsCache eviction/flush logic using a cache library
[ https://issues.apache.org/jira/browse/AMBARI-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16821: Status: Open (was: Patch Available) > Improve TimelineMetricsCache eviction/flush logic using a cache library > --- > > Key: AMBARI-16821 > URL: https://issues.apache.org/jira/browse/AMBARI-16821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.4.0 > > Attachments: AMBARI-16821_1.patch, AMBARI-16821_2.patch > > > The TimelineMetricsCache implementation in the metrics sink side is currently > a ConcurrentSkipListMap. It is better to use pre built cache libraries like > Guava that offer more support. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16921) Yarn minimum container size calculation problem in stack advisor
Daniel Gergely created AMBARI-16921: --- Summary: Yarn minimum container size calculation problem in stack advisor Key: AMBARI-16921 URL: https://issues.apache.org/jira/browse/AMBARI-16921 Project: Ambari Issue Type: Bug Reporter: Daniel Gergely Assignee: Daniel Gergely Priority: Blocker Stack advisor gets yarn minimum container size property from only the "services" input, but does not take into account the already calculated configurations. As a result memory size for hive interactive server is not correct, so it doesn't start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16875) LDAP sync cannot handle if the member attribute value is not DN or id
[ https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16875: -- Description: in case of member attribute value looks like this:
[jira] [Commented] (AMBARI-16665) Cache service advisors when stack advisor is loaded
[
https://issues.apache.org/jira/browse/AMBARI-16665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303810#comment-15303810
]
Hadoop QA commented on AMBARI-16665:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806449/AMBARI-16665.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:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7010//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7010//console
This message is automatically generated.
> Cache service advisors when stack advisor is loaded
> ---
>
> Key: AMBARI-16665
> URL: https://issues.apache.org/jira/browse/AMBARI-16665
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: trunk, 2.4.0
>Reporter: Matt
>Assignee: Lav Jain
> Fix For: trunk, 2.4.0
>
> Attachments: AMBARI-16665.branch24.patch, AMBARI-16665.patch
>
>
> With the current implementation, service advisors for the same service are
> loaded multiple times in the stack advisor.
> The service advisors should be cached when the stack advisor is loaded and
> used where necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16925) Config pages are corrupted for services failed to install
[ https://issues.apache.org/jira/browse/AMBARI-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-16925: --- Status: Patch Available (was: Open) Patch added > Config pages are corrupted for services failed to install > - > > Key: AMBARI-16925 > URL: https://issues.apache.org/jira/browse/AMBARI-16925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: ambari-server version: ambari-server-2.4.0.0-611 > ambari-server --hash: 1feda434390324d06a1af922328b3d1b4c788305 > HDP Stack: 2.5 > HDP Version: 2.5.0.0-582 > Ambari DB: :PostgreSQL_External > Oozie/Hive DB: PostgreSQL_External/PostgreSQL_External > Security:yes > Security Type:AD/AD > Blueprints: true > Umask: > JDK: OracleJDK8 > HA: no > OS: SUSE Linux Enterprise Server 11 > Ambari User: root > Agents User: root > MOTD enabled: false > Customized service users: false > Is tmp exec: false >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16925.patch > > > Deploy of cluster via blueprints was failed on installing of components. > After that services failed to install have corrupted configs pages. This can > block user because there can be situation when it is not possible to install > service without configs changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16925) Config pages are corrupted for services failed to install
[ https://issues.apache.org/jira/browse/AMBARI-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleg Nechiporenko updated AMBARI-16925: --- Attachment: AMBARI-16925.patch > Config pages are corrupted for services failed to install > - > > Key: AMBARI-16925 > URL: https://issues.apache.org/jira/browse/AMBARI-16925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: ambari-server version: ambari-server-2.4.0.0-611 > ambari-server --hash: 1feda434390324d06a1af922328b3d1b4c788305 > HDP Stack: 2.5 > HDP Version: 2.5.0.0-582 > Ambari DB: :PostgreSQL_External > Oozie/Hive DB: PostgreSQL_External/PostgreSQL_External > Security:yes > Security Type:AD/AD > Blueprints: true > Umask: > JDK: OracleJDK8 > HA: no > OS: SUSE Linux Enterprise Server 11 > Ambari User: root > Agents User: root > MOTD enabled: false > Customized service users: false > Is tmp exec: false >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16925.patch > > > Deploy of cluster via blueprints was failed on installing of components. > After that services failed to install have corrupted configs pages. This can > block user because there can be situation when it is not possible to install > service without configs changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16925) Config pages are corrupted for services failed to install
[ https://issues.apache.org/jira/browse/AMBARI-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303982#comment-15303982 ] Oleg Nechiporenko commented on AMBARI-16925: 27868 tests complete (31 seconds) 154 tests pending > Config pages are corrupted for services failed to install > - > > Key: AMBARI-16925 > URL: https://issues.apache.org/jira/browse/AMBARI-16925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: ambari-server version: ambari-server-2.4.0.0-611 > ambari-server --hash: 1feda434390324d06a1af922328b3d1b4c788305 > HDP Stack: 2.5 > HDP Version: 2.5.0.0-582 > Ambari DB: :PostgreSQL_External > Oozie/Hive DB: PostgreSQL_External/PostgreSQL_External > Security:yes > Security Type:AD/AD > Blueprints: true > Umask: > JDK: OracleJDK8 > HA: no > OS: SUSE Linux Enterprise Server 11 > Ambari User: root > Agents User: root > MOTD enabled: false > Customized service users: false > Is tmp exec: false >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16925.patch > > > Deploy of cluster via blueprints was failed on installing of components. > After that services failed to install have corrupted configs pages. This can > block user because there can be situation when it is not possible to install > service without configs changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14926) ambari cached hdfs.py conflicts with python hdfs lib resulting into monitoring errors
[
https://issues.apache.org/jira/browse/AMBARI-14926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-14926:
-
Fix Version/s: (was: 2.2.2)
2.4.0
> ambari cached hdfs.py conflicts with python hdfs lib resulting into
> monitoring errors
> -
>
> Key: AMBARI-14926
> URL: https://issues.apache.org/jira/browse/AMBARI-14926
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.0
> Environment: Linux CentOS 7 x86_64
>Reporter: matteo brancaleoni
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14926.patch
>
>
> On systems with datanode and journal node monitored by ambari-agent,
> if in the standard python path the hdfs lib is installed (
> https://pypi.python.org/pypi/hdfs/ ) it makes datanode + journalnode
> monitoring fail:
> * datanodes are seen up in global live datanodes
> * but the service is down into the host service list (restart will work, but
> are marked as stopped)
> looking into the logs I get:
> DEBUG 2016-02-04 16:54:49,160 PythonReflectiveExecutor.py:47 - Running
> command reflectively ['/usr/bin/python2',
>
> u'/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py',
> 'SECURITY_STATUS',
> --
> '/var/lib/ambari-agent/tmp']
> DEBUG 2016-02-04 16:54:49,170 PythonReflectiveExecutor.py:61 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 55, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
> line 30, in
> from utils import service
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py",
> line 37, in
> from zkfc_slave import ZkfcSlave
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py",
> line 21, in
> from hdfs import hdfs
> ImportError: cannot import name hdfs
> I think that ambari is including its cache files after the python path, so if
> an hdfs module is present into python path makes the scripts goes crazy.
> (basically using the system hdfs py module and not his own)
> maybe cache files path must be included before the python path or imported
> with local imports?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16896) It is possible to save service configs changes without applying config dependencies
[ https://issues.apache.org/jira/browse/AMBARI-16896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303967#comment-15303967 ] Aleksandr Kovalenko commented on AMBARI-16896: -- committed to trunk and branch-2.4 > It is possible to save service configs changes without applying config > dependencies > > > Key: AMBARI-16896 > URL: https://issues.apache.org/jira/browse/AMBARI-16896 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16896.patch > > > Warning popup about configuration dependencies appears with delay after > config changing. So user can save and confirm changes before appearing > warning popup about dependencies and without checking and applying them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16925) Config pages are corrupted for services failed to install
[ https://issues.apache.org/jira/browse/AMBARI-16925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303988#comment-15303988 ] Antonenko Alexander commented on AMBARI-16925: -- +1 for the patch > Config pages are corrupted for services failed to install > - > > Key: AMBARI-16925 > URL: https://issues.apache.org/jira/browse/AMBARI-16925 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: ambari-server version: ambari-server-2.4.0.0-611 > ambari-server --hash: 1feda434390324d06a1af922328b3d1b4c788305 > HDP Stack: 2.5 > HDP Version: 2.5.0.0-582 > Ambari DB: :PostgreSQL_External > Oozie/Hive DB: PostgreSQL_External/PostgreSQL_External > Security:yes > Security Type:AD/AD > Blueprints: true > Umask: > JDK: OracleJDK8 > HA: no > OS: SUSE Linux Enterprise Server 11 > Ambari User: root > Agents User: root > MOTD enabled: false > Customized service users: false > Is tmp exec: false >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16925.patch > > > Deploy of cluster via blueprints was failed on installing of components. > After that services failed to install have corrupted configs pages. This can > block user because there can be situation when it is not possible to install > service without configs changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16875) LDAP sync cannot handle if the member attribute value is not DN or id
[ https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16875: -- Attachment: AMBARI-16875.patch > LDAP sync cannot handle if the member attribute value is not DN or id > - > > Key: AMBARI-16875 > URL: https://issues.apache.org/jira/browse/AMBARI-16875 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16875.patch > > > in case of member attribute value looks like this: >
[jira] [Commented] (AMBARI-16902) Going back form review page to config page on Installer and ADW clears min/max recommendatoins
[ https://issues.apache.org/jira/browse/AMBARI-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303923#comment-15303923 ] Hudson commented on AMBARI-16902: - FAILURE: Integrated in Ambari-trunk-Commit #4939 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4939/]) AMBARI-16902 Going back form review page to config page on Installer and (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e362aa994382f7af6382751192c27eb2c1d2d570]) * ambari-web/app/controllers/wizard.js * ambari-web/app/routes/add_service_routes.js * ambari-web/app/routes/installer.js * ambari-web/app/controllers/installer.js * ambari-web/app/controllers/wizard/step3_controller.js > Going back form review page to config page on Installer and ADW clears > min/max recommendatoins > -- > > Key: AMBARI-16902 > URL: https://issues.apache.org/jira/browse/AMBARI-16902 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-16902.patch > > > On Installer and ADW, when going back from review page to config page configs > min/max values are being restored to default stack value -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16910) Hive Server Interactive. Change the timeout to 120 secs for LLAP alert command.
[ https://issues.apache.org/jira/browse/AMBARI-16910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16910: - Resolution: Fixed Status: Resolved (was: Patch Available) > Hive Server Interactive. Change the timeout to 120 secs for LLAP alert > command. > --- > > Key: AMBARI-16910 > URL: https://issues.apache.org/jira/browse/AMBARI-16910 > 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-16910.patch > > > - Right now the timeout is 15 secs for LLAP alert. > - Reason to increase: Right now the command timeouts, because 15 secs is > less for it to complete depending on the cluster. > - Further, modified the messages displayed as part of alert. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16910) Hive Server Interactive. Change the timeout to 120 secs for LLAP alert command.
[
https://issues.apache.org/jira/browse/AMBARI-16910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303922#comment-15303922
]
Swapan Shridhar commented on AMBARI-16910:
--
trunk commit :
{code}
commit 08d70f5939459493c480fa6d6736f4be7226bf73
Author: Swapan Shridhar
Date: Thu May 26 12:50:44 2016 -0700
AMBARI-16910. Hive Server Interactive. Change the timeout to 120 secs for
LLAP alert command.
{code}
branch-2.4:
{code}
commit 04e23a4cfa60528deb164028ebafb06fdcdadbde
Author: Swapan Shridhar
Date: Thu May 26 19:59:34 2016 -0700
AMBARI-16910. Hive Server Interactive. Change the timeout to 120 secs for
LLAP alert command.
{code}
> Hive Server Interactive. Change the timeout to 120 secs for LLAP alert
> command.
> ---
>
> Key: AMBARI-16910
> URL: https://issues.apache.org/jira/browse/AMBARI-16910
> 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-16910.patch
>
>
> - Right now the timeout is 15 secs for LLAP alert.
> - Reason to increase: Right now the command timeouts, because 15 secs is
> less for it to complete depending on the cluster.
> - Further, modified the messages displayed as part of alert.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-16924) Invalid syntax of Oracle DDL for cluster_handle in viewinstance
[
https://issues.apache.org/jira/browse/AMBARI-16924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha resolved AMBARI-16924.
--
Resolution: Fixed
committed to trunk and branch-2.4
> Invalid syntax of Oracle DDL for cluster_handle in viewinstance
> ---
>
> Key: AMBARI-16924
> URL: https://issues.apache.org/jira/browse/AMBARI-16924
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: 2.4.0
>
> Attachments: AMBARI-16924_branch-2.4.patch
>
>
> exceptions in ambari-server.log:
> {code}
> 27 May 2016 08:01:01,326 ERROR [qtp-ambari-client-27] ReadHandler:94 - Caught
> a runtime exception executing a query
> javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
> Persistence Services - 2.6.2.v20151217-774c696):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or
> view does not exist
> Error Code: 942
> Call: SELECT view_instance_id, alter_names, cluster_handle, cluster_type,
> DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven,
> resource_id, short_url FROM viewinstance
> Query: ReadAllQuery(name="allViewInstances" referenceClass=ViewInstanceEntity
> sql="SELECT view_instance_id, alter_names, cluster_handle, cluster_type,
> DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven,
> resource_id, short_url FROM viewinstance")
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
> at
> org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
> at
> org.apache.ambari.server.orm.dao.ViewInstanceDAO.findAll(ViewInstanceDAO.java:92)
> at
> org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
> at
> org.apache.ambari.server.security.authorization.ClusterInheritedPermissionHelper.getViewPrivilegesWithClusterPermission(ClusterInheritedPermissionHelper.java:187)
> at
> org.apache.ambari.server.controller.internal.UserPrivilegeResourceProvider.getResources(UserPrivilegeResourceProvider.java:208)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:512)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:464)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:437)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:69)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
> at
> org.apache.ambari.server.api.services.UserService.getUser(UserService.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>
[jira] [Updated] (AMBARI-16868) Insert Statement in Hive View is giving error in Kerberised cluster.
[
https://issues.apache.org/jira/browse/AMBARI-16868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-16868:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk and branch-2.4
> Insert Statement in Hive View is giving error in Kerberised cluster.
>
>
> Key: AMBARI-16868
> URL: https://issues.apache.org/jira/browse/AMBARI-16868
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: ambari-2.4.0
>Reporter: Gaurav Nagar
>Assignee: Gaurav Nagar
> Fix For: ambari-2.4.0
>
> Attachments: AMBARI-16868_branch-2.4.patch
>
>
> Statement : INSERT INTO TABLE testtable61
> values('name','name0','secondname0');
> {code}
> Error Generated :
> INFO : Tez session hasn't been created yet. Opening session
> ERROR : Failed to execute tez graph.
> org.apache.hadoop.security.AccessControlException: Permission denied:
> user=${username}, access=WRITE, inode="/user/${username}":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1794)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:4004)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1102)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:630)
> at
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16901) Add Service wizard: All kerberos related configurations shown on Configure Identities page should be made non-editable on configure services page
[ https://issues.apache.org/jira/browse/AMBARI-16901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16901: -- Attachment: AMBARI-16901.patch > Add Service wizard: All kerberos related configurations shown on Configure > Identities page should be made non-editable on configure services page > - > > Key: AMBARI-16901 > URL: https://issues.apache.org/jira/browse/AMBARI-16901 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16901.patch > > > If following conditions are met then config should be made non-editable on > configure->services page: > Cluster is kerberized > Kerberos is ambari managed meaning not manual > Config is stated as an identity in the kerberos descriptor posted to the > cluster (api/v1/clusters/c1/artifacts/kerberos_descriptor). Note that config > has to be an identity to be made non-editable. Note: Other configs mentioned > in the kerberos descriptor should not be made non-editable. Only configs > stated under identities array should be made non-editable. > Configs made non-editable due to satisfying above condition should have their > description appended with the text that "This config can be changed from > Kerberos page under Admin tab by privileged users." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16901) Add Service wizard: All kerberos related configurations shown on Configure Identities page should be made non-editable on configure services page
[ https://issues.apache.org/jira/browse/AMBARI-16901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16901: -- Status: Patch Available (was: Open) 27859 tests complete (21 seconds) 154 tests pending > Add Service wizard: All kerberos related configurations shown on Configure > Identities page should be made non-editable on configure services page > - > > Key: AMBARI-16901 > URL: https://issues.apache.org/jira/browse/AMBARI-16901 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16901.patch > > > If following conditions are met then config should be made non-editable on > configure->services page: > Cluster is kerberized > Kerberos is ambari managed meaning not manual > Config is stated as an identity in the kerberos descriptor posted to the > cluster (api/v1/clusters/c1/artifacts/kerberos_descriptor). Note that config > has to be an identity to be made non-editable. Note: Other configs mentioned > in the kerberos descriptor should not be made non-editable. Only configs > stated under identities array should be made non-editable. > Configs made non-editable due to satisfying above condition should have their > description appended with the text that "This config can be changed from > Kerberos page under Admin tab by privileged users." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16926) Add ability to query all hosts using hostname=% through AMS API.
[ https://issues.apache.org/jira/browse/AMBARI-16926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-16926: Attachment: AMBARI-16926.patch > Add ability to query all hosts using hostname=% through AMS API. > > > Key: AMBARI-16926 > URL: https://issues.apache.org/jira/browse/AMBARI-16926 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16926.patch > > > Useful for Top N feature > Add ability to query all hosts using hostname=%.my.com through AMS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[
https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304004#comment-15304004
]
Hadoop QA commented on AMBARI-16827:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806505/AMBARI-16827-2.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/7013//console
This message is automatically generated.
> expose vm.overcommit_ratio on hawq-sysctl-env
> -
>
> Key: AMBARI-16827
> URL: https://issues.apache.org/jira/browse/AMBARI-16827
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: bhuvnesh chaudhary
> Attachments: AMBARI-16827-2.patch, AMBARI-16827.patch
>
>
> vm.overcommit_ratio is used for calculation of hawq_rm_memory_limit_perseg.
> So, expose it on the UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16900) Delete Host message is incorrect, suggests all Clients will be deleted from cluster
[ https://issues.apache.org/jira/browse/AMBARI-16900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303812#comment-15303812 ] Andrii Tkach commented on AMBARI-16900: --- committed to trunk and branch-2.4 > Delete Host message is incorrect, suggests all Clients will be deleted from > cluster > --- > > Key: AMBARI-16900 > URL: https://issues.apache.org/jira/browse/AMBARI-16900 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16900.patch, Screen Shot 2016-05-20 at 4.34.35 > PM.png, Screen Shot 2016-05-20 at 4.35.24 PM.png > > > STR: > # Installed Ambari 2.2.2.0-460 (08c6c18907d8f35cce55eeaf9123db19fe34ce10) on > 3 hosts > # Installed HDP 2.3.4.0-3485 with HDFS, YARN, MR, Pig, Tez, Sqoop, and ZK, > with clients on all hosts > # Added an extra host (c6404.ambari.apache.org) and only installed clients on > it. > # Stopped ambari agent on c6404.ambari.apache.org and visited its host page > to attempt to deleted > Upon refreshing the page, would sometimes see the first screenshot, other > times would see the 2nd screenshot, which suggests that Ambari is also going > to delete the clients since only that host contains it, which is incorrect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16900) Delete Host message is incorrect, suggests all Clients will be deleted from cluster
[ https://issues.apache.org/jira/browse/AMBARI-16900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16900: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Delete Host message is incorrect, suggests all Clients will be deleted from > cluster > --- > > Key: AMBARI-16900 > URL: https://issues.apache.org/jira/browse/AMBARI-16900 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16900.patch, Screen Shot 2016-05-20 at 4.34.35 > PM.png, Screen Shot 2016-05-20 at 4.35.24 PM.png > > > STR: > # Installed Ambari 2.2.2.0-460 (08c6c18907d8f35cce55eeaf9123db19fe34ce10) on > 3 hosts > # Installed HDP 2.3.4.0-3485 with HDFS, YARN, MR, Pig, Tez, Sqoop, and ZK, > with clients on all hosts > # Added an extra host (c6404.ambari.apache.org) and only installed clients on > it. > # Stopped ambari agent on c6404.ambari.apache.org and visited its host page > to attempt to deleted > Upon refreshing the page, would sometimes see the first screenshot, other > times would see the 2nd screenshot, which suggests that Ambari is also going > to delete the clients since only that host contains it, which is incorrect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16922) Remove LogSearch dependency for Ranger
Mugdha Varadkar created AMBARI-16922: Summary: Remove LogSearch dependency for Ranger Key: AMBARI-16922 URL: https://issues.apache.org/jira/browse/AMBARI-16922 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Priority: Critical Fix For: 2.4.0 Remove LogSearch dependency for Ranger -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16921) Yarn minimum container size calculation problem in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gergely updated AMBARI-16921: Attachment: AMBARI-16921.patch > Yarn minimum container size calculation problem in stack advisor > > > Key: AMBARI-16921 > URL: https://issues.apache.org/jira/browse/AMBARI-16921 > Project: Ambari > Issue Type: Bug >Reporter: Daniel Gergely >Assignee: Daniel Gergely >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > Stack advisor gets yarn minimum container size property from only the > "services" input, but does not take into account the already calculated > configurations. > As a result memory size for hive interactive server is not correct, so it > doesn't start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16921) Yarn minimum container size calculation problem in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gergely updated AMBARI-16921: Fix Version/s: 2.4.0 > Yarn minimum container size calculation problem in stack advisor > > > Key: AMBARI-16921 > URL: https://issues.apache.org/jira/browse/AMBARI-16921 > Project: Ambari > Issue Type: Bug >Reporter: Daniel Gergely >Assignee: Daniel Gergely >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > Stack advisor gets yarn minimum container size property from only the > "services" input, but does not take into account the already calculated > configurations. > As a result memory size for hive interactive server is not correct, so it > doesn't start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16921) Yarn minimum container size calculation problem in stack advisor
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gergely updated AMBARI-16921: Status: Patch Available (was: Open) > Yarn minimum container size calculation problem in stack advisor > > > Key: AMBARI-16921 > URL: https://issues.apache.org/jira/browse/AMBARI-16921 > Project: Ambari > Issue Type: Bug >Reporter: Daniel Gergely >Assignee: Daniel Gergely >Priority: Blocker > Attachments: AMBARI-16921.patch > > > Stack advisor gets yarn minimum container size property from only the > "services" input, but does not take into account the already calculated > configurations. > As a result memory size for hive interactive server is not correct, so it > doesn't start. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16924) Invalid syntax of Oracle DDL for cluster_handle in viewinstance
Gaurav Nagar created AMBARI-16924:
-
Summary: Invalid syntax of Oracle DDL for cluster_handle in
viewinstance
Key: AMBARI-16924
URL: https://issues.apache.org/jira/browse/AMBARI-16924
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Gaurav Nagar
Assignee: Gaurav Nagar
Fix For: 2.4.0
exceptions in ambari-server.log:
{code}
27 May 2016 08:01:01,326 ERROR [qtp-ambari-client-27] ReadHandler:94 - Caught a
runtime exception executing a query
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse
Persistence Services - 2.6.2.v20151217-774c696):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00942: table or view
does not exist
Error Code: 942
Call: SELECT view_instance_id, alter_names, cluster_handle, cluster_type,
DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven,
resource_id, short_url FROM viewinstance
Query: ReadAllQuery(name="allViewInstances" referenceClass=ViewInstanceEntity
sql="SELECT view_instance_id, alter_names, cluster_handle, cluster_type,
DESCRIPTION, ICON, ICON64, LABEL, name, view_name, VISIBLE, xml_driven,
resource_id, short_url FROM viewinstance")
at
org.eclipse.persistence.internal.jpa.QueryImpl.getDetailedException(QueryImpl.java:382)
at
org.eclipse.persistence.internal.jpa.QueryImpl.executeReadQuery(QueryImpl.java:260)
at
org.eclipse.persistence.internal.jpa.QueryImpl.getResultList(QueryImpl.java:473)
at
org.apache.ambari.server.orm.dao.ViewInstanceDAO.findAll(ViewInstanceDAO.java:92)
at
org.apache.ambari.server.orm.AmbariLocalSessionInterceptor.invoke(AmbariLocalSessionInterceptor.java:53)
at
org.apache.ambari.server.security.authorization.ClusterInheritedPermissionHelper.getViewPrivilegesWithClusterPermission(ClusterInheritedPermissionHelper.java:187)
at
org.apache.ambari.server.controller.internal.UserPrivilegeResourceProvider.getResources(UserPrivilegeResourceProvider.java:208)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141)
at
org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:512)
at
org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:464)
at
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:437)
at
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:217)
at
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:69)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
at
org.apache.ambari.server.api.services.UserService.getUser(UserService.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
[jira] [Updated] (AMBARI-16923) AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config Property Attributes updated if there is a change in 'capacity-scheduler'.
[ https://issues.apache.org/jira/browse/AMBARI-16923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16923: - Status: Patch Available (was: Open) > AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config > Property Attributes updated if there is a change in 'capacity-scheduler'. > > > Key: AMBARI-16923 > URL: https://issues.apache.org/jira/browse/AMBARI-16923 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16923.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16923) AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config Property Attributes updated if there is a change in 'capacity-scheduler'.
[ https://issues.apache.org/jira/browse/AMBARI-16923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16923: - Attachment: AMBARI-16923.patch > AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config > Property Attributes updated if there is a change in 'capacity-scheduler'. > > > Key: AMBARI-16923 > URL: https://issues.apache.org/jira/browse/AMBARI-16923 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16923.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16917) Use postgres database instead of template1 during service check in HAWQ
[
https://issues.apache.org/jira/browse/AMBARI-16917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304002#comment-15304002
]
Hadoop QA commented on AMBARI-16917:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12806511/AMBARI-16917.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/7012//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7012//console
This message is automatically generated.
> Use postgres database instead of template1 during service check in HAWQ
> ---
>
> Key: AMBARI-16917
> URL: https://issues.apache.org/jira/browse/AMBARI-16917
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Affects Versions: 2.4.0
>Reporter: bhuvnesh chaudhary
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-16917.patch
>
>
> Use postgres database instead of template1 during service check in HAWQ.
> template1 database is used as a default template while creating new
> databases, so anything in template1 gets carried over to the new database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16875) LDAP sync cannot handle if the member attribute value is not DN or id
[ https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16875: -- Description: in case of member attribute value looks like this:
[jira] [Updated] (AMBARI-16875) LDAP sync cannot handle if the member attribute value is not DN or id
[ https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16875: -- Description: in case of member attribute value looks like this:
[jira] [Updated] (AMBARI-16922) Remove LogSearch dependency for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-16922: - Attachment: AMBARI-16922.patch > Remove LogSearch dependency for Ranger > -- > > Key: AMBARI-16922 > URL: https://issues.apache.org/jira/browse/AMBARI-16922 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16922.patch > > > Remove LogSearch dependency for Ranger -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16922) Remove LogSearch dependency for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-16922: - Status: Patch Available (was: In Progress) > Remove LogSearch dependency for Ranger > -- > > Key: AMBARI-16922 > URL: https://issues.apache.org/jira/browse/AMBARI-16922 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16922.patch > > > Remove LogSearch dependency for Ranger -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16919) Handle the scenario when 'capacity-scheduler' is passed-in as dictionary to Stack Advisor and services['configurations']["capacity-scheduler"]["properties"]["capacity
[
https://issues.apache.org/jira/browse/AMBARI-16919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303925#comment-15303925
]
Swapan Shridhar commented on AMBARI-16919:
--
trunk:
{code}
commit 59364bc87d0ad3c6fa16918329d40230b34646c8
Author: Swapan Shridhar
Date: Thu May 26 18:47:21 2016 -0700
AMBARI-16919. Handle the scenario when 'capacity-scheduler' is passed-in as
dictionary to Stack Advisor and
services['configurations'][capacity-scheduler][properties][capacity-scheduler]
is null.
{code}
branch-2.4:
{code}
commit c2e741e5257bcd39b7cdf9aa68159d4e5307b394
Author: Swapan Shridhar
Date: Thu May 26 20:00:37 2016 -0700
AMBARI-16919. Handle the scenario when 'capacity-scheduler' is passed-in as
dictionary to Stack Advisor and
services['configurations'][capacity-scheduler][properties][capacity-scheduler]
is null.
{code}
> Handle the scenario when 'capacity-scheduler' is passed-in as dictionary to
> Stack Advisor and
> services['configurations']["capacity-scheduler"]["properties"]["capacity-scheduler"]
> is null.
> ---
>
> Key: AMBARI-16919
> URL: https://issues.apache.org/jira/browse/AMBARI-16919
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-16919.patch
>
>
> AMBARI-16888 handled the scenario when capacity-scheduler is passed in as
> dictionary and
> services['configurations']["capacity-scheduler"]["properties"]["capacity-scheduler"]
> set as value = "null".
> {code}
> "capacity-scheduler" : {
> "properties" : {
> "capacity-scheduler" : "null",
> "yarn.scheduler.capacity.root.accessible-node-labels" : "*",
> "yarn.scheduler.capacity.maximum-am-resource-percent" : "1",
> "yarn.scheduler.capacity.root.acl_administer_queue" : "*",
> "yarn.scheduler.capacity.queue-mappings-override.enable" :
> 'false',
> "yarn.scheduler.capacity.root.default.capacity" : "100",
> "yarn.scheduler.capacity.root.default.user-limit-factor" : "1",
> "yarn.scheduler.capacity.root.queues" : "default",
> "yarn.scheduler.capacity.root.capacity" : "100",
> "yarn.scheduler.capacity.root.default.acl_submit_applications" :
> "*",
> "yarn.scheduler.capacity.root.default.maximum-capacity" : "100",
> "yarn.scheduler.capacity.node-locality-delay" : "40",
> "yarn.scheduler.capacity.maximum-applications" : "1",
> "yarn.scheduler.capacity.root.default.state" : "RUNNING"
> }
> },
> {code}
> But. there can be another scenario where passed-in 'capacity-scheduler' is
> like :
> {code}
> "capacity-scheduler" : {
> "properties" : {
> "capacity-scheduler" : null,
> "yarn.scheduler.capacity.root.accessible-node-labels" : "*",
> "yarn.scheduler.capacity.maximum-am-resource-percent" : "1",
> "yarn.scheduler.capacity.root.acl_administer_queue" : "*",
> "yarn.scheduler.capacity.queue-mappings-override.enable" :
> 'false',
> "yarn.scheduler.capacity.root.default.capacity" : "100",
> "yarn.scheduler.capacity.root.default.user-limit-factor" : "1",
> "yarn.scheduler.capacity.root.queues" : "default",
> "yarn.scheduler.capacity.root.capacity" : "100",
> "yarn.scheduler.capacity.root.default.acl_submit_applications" :
> "*",
> "yarn.scheduler.capacity.root.default.maximum-capacity" : "100",
> "yarn.scheduler.capacity.node-locality-delay" : "40",
> "yarn.scheduler.capacity.maximum-applications" : "1",
> "yarn.scheduler.capacity.root.default.state" : "RUNNING"
> }
> },
> {code}
> Here,
> services['configurations']["capacity-scheduler"]["properties"]["capacity-scheduler"]
> is itself 'null'.
> We get into reading capacity-scheduler configs as key-value only if we dont
> find configs passed in as single '\n' string at level
> services['configurations']["capacity-scheduler"]["properties"]["capacity-scheduler"]:
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-14926) ambari cached hdfs.py conflicts with python hdfs lib resulting into monitoring errors
[
https://issues.apache.org/jira/browse/AMBARI-14926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-14926:
-
Fix Version/s: 2.2.2
> ambari cached hdfs.py conflicts with python hdfs lib resulting into
> monitoring errors
> -
>
> Key: AMBARI-14926
> URL: https://issues.apache.org/jira/browse/AMBARI-14926
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.0
> Environment: Linux CentOS 7 x86_64
>Reporter: matteo brancaleoni
>Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-14926.patch
>
>
> On systems with datanode and journal node monitored by ambari-agent,
> if in the standard python path the hdfs lib is installed (
> https://pypi.python.org/pypi/hdfs/ ) it makes datanode + journalnode
> monitoring fail:
> * datanodes are seen up in global live datanodes
> * but the service is down into the host service list (restart will work, but
> are marked as stopped)
> looking into the logs I get:
> DEBUG 2016-02-04 16:54:49,160 PythonReflectiveExecutor.py:47 - Running
> command reflectively ['/usr/bin/python2',
>
> u'/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py',
> 'SECURITY_STATUS',
> --
> '/var/lib/ambari-agent/tmp']
> DEBUG 2016-02-04 16:54:49,170 PythonReflectiveExecutor.py:61 - Reflective
> command failed with exception:
> Traceback (most recent call last):
> File
> "/usr/lib/python2.6/site-packages/ambari_agent/PythonReflectiveExecutor.py",
> line 55, in run_file
> imp.load_source('__main__', script)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode.py",
> line 30, in
> from utils import service
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py",
> line 37, in
> from zkfc_slave import ZkfcSlave
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/zkfc_slave.py",
> line 21, in
> from hdfs import hdfs
> ImportError: cannot import name hdfs
> I think that ambari is including its cache files after the python path, so if
> an hdfs module is present into python path makes the scripts goes crazy.
> (basically using the system hdfs py module and not his own)
> maybe cache files path must be included before the python path or imported
> with local imports?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-16909) VDF builder script and XSD should be updated for package-version changes
[
https://issues.apache.org/jira/browse/AMBARI-16909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole resolved AMBARI-16909.
Resolution: Fixed
> VDF builder script and XSD should be updated for package-version changes
>
>
> Key: AMBARI-16909
> URL: https://issues.apache.org/jira/browse/AMBARI-16909
> Project: Ambari
> Issue Type: Bug
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.4.0
>
>
> The {{package-version}} element should belong with the {{os}} element such
> that we can send that information to agents effectively when multiple OS are
> defined in the XML.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-16926) Add ability to query all hosts using hostname=% through AMS API.
Dmytro Sen created AMBARI-16926: --- Summary: Add ability to query all hosts using hostname=% through AMS API. Key: AMBARI-16926 URL: https://issues.apache.org/jira/browse/AMBARI-16926 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.4.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.4.0 Useful for Top N feature Add ability to query all hosts using hostname=%.my.com through AMS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16902) Going back form review page to config page on Installer and ADW clears min/max recommendatoins
[ https://issues.apache.org/jira/browse/AMBARI-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-16902: -- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and branch 2.4 > Going back form review page to config page on Installer and ADW clears > min/max recommendatoins > -- > > Key: AMBARI-16902 > URL: https://issues.apache.org/jira/browse/AMBARI-16902 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-16902.patch > > > On Installer and ADW, when going back from review page to config page configs > min/max values are being restored to default stack value -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16925) Config pages are corrupted for services failed to install
Oleg Nechiporenko created AMBARI-16925: -- Summary: Config pages are corrupted for services failed to install Key: AMBARI-16925 URL: https://issues.apache.org/jira/browse/AMBARI-16925 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Environment: ambari-server version: ambari-server-2.4.0.0-611 ambari-server --hash: 1feda434390324d06a1af922328b3d1b4c788305 HDP Stack: 2.5 HDP Version: 2.5.0.0-582 Ambari DB: :PostgreSQL_External Oozie/Hive DB: PostgreSQL_External/PostgreSQL_External Security:yes Security Type:AD/AD Blueprints: true Umask: JDK: OracleJDK8 HA: no OS: SUSE Linux Enterprise Server 11 Ambari User: root Agents User: root MOTD enabled: false Customized service users: false Is tmp exec: false Reporter: Oleg Nechiporenko Assignee: Oleg Nechiporenko Priority: Blocker Fix For: 2.4.0 Deploy of cluster via blueprints was failed on installing of components. After that services failed to install have corrupted configs pages. This can block user because there can be situation when it is not possible to install service without configs changing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16875) LDAP sync cannot handle if the member attribute value is not DN or id
[ https://issues.apache.org/jira/browse/AMBARI-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-16875: -- Attachment: (was: AMBARI-16875.patch) > LDAP sync cannot handle if the member attribute value is not DN or id > - > > Key: AMBARI-16875 > URL: https://issues.apache.org/jira/browse/AMBARI-16875 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16875.patch > > > in case of member attribute value looks like this: >
