[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&focusedCommentId=15305202#comment-15305202 ] Matt commented on AMBARI-16665: --- Committed to trunk: {code} commit 069cc49dae316f8bab776ad1e3acacd55d4a8cc1 Author: Matt Date: Fri May 27 23:07:53 2016 -0700 {code} Committed to branch-2.4: {code} commit dc340e8c6cb4fa6c062f805cc1917f62299a5f50 Author: Matt Date: Fri May 27 23:18:26 2016 -0700 {code} Marking as resolved. > 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.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.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] [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&focusedCommentId=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: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- 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&focusedCommentId=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&a=commit&h=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-16938) Deploy: UI: Hive_metastore not started
[ https://issues.apache.org/jira/browse/AMBARI-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-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&focusedCommentId=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&a=commit&h=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-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&focusedCommentId=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&a=commit&h=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-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&focusedCommentId=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-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&focusedCommentId=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 lo
[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] [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] [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&focusedCommentId=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] [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-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&focusedCommentId=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&a=commit&h=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&focusedCommentId=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&a=commit&h=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&a=commit&h=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-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] [Commented] (AMBARI-16908) Different repositories show same versions of services
[ https://issues.apache.org/jira/browse/AMBARI-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305059#comment-15305059 ] Hadoop QA commented on AMBARI-16908: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806725/AMBARI-16908.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-web. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7040//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7040//console This message is automatically generated. > Different repositories show same versions of services > - > > Key: AMBARI-16908 > URL: https://issues.apache.org/jira/browse/AMBARI-16908 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-16908.patch > > > Different repositories show same versions of services. The versions are from > the last installed repo. > The order of repo is incorrect in some scenarios. -- 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: 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&focusedCommentId=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-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&focusedCommentId=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.SQLExce
[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] [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-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] [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] [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&focusedCommentId=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&a=commit&h=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] [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&focusedCommentId=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&a=commit&h=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] [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] [Updated] (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' configs
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - 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. (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) > 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: Daniel Gergely >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) 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-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - Description: - 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. was: 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 . Otherwise read from services array. > 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: Daniel Gergely >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) 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-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - Description: 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 . Otherwise read from services array. was: 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' . Otherwise read from services array. > 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: Daniel Gergely >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > 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 > . Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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' configs
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - Description: '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' . Otherwise read from services array. was: 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. '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' > 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: Daniel Gergely >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > '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' > . Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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' configs
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - Description: 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' . Otherwise read from services array. was: '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' . Otherwise read from services array. > 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: Daniel Gergely >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16921.patch > > > 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' > . Otherwise read from services array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
[ https://issues.apache.org/jira/browse/AMBARI-13135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-13135: Description: The following options are recommended for HBase when ConcMarkSweepGC is used: {code} -XX:CMSInitiatingOccupancyFraction=50 -XX:+UseCMSInitiatingOccupancyOnly {code} The band for CMSInitiatingOccupancyFraction is [40, 60], depending on workload. This should be reflected in stack_advisor.py was: The following options are recommended for HBase when ConcMarkSweepGC is used: {code} -XX:CMSInitiatingOccupancyFraction=50 -XX:+UseCMSInitiatingOccupancyOnly {code} The band for CMSInitiatingOccupancyFraction is [40, 60], depending on workload. This should be reflected in stack_advisor.py > Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase > -- > > Key: AMBARI-13135 > URL: https://issues.apache.org/jira/browse/AMBARI-13135 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > The following options are recommended for HBase when ConcMarkSweepGC is used: > {code} > -XX:CMSInitiatingOccupancyFraction=50 > -XX:+UseCMSInitiatingOccupancyOnly > {code} > The band for CMSInitiatingOccupancyFraction is [40, 60], depending on > workload. > This should be reflected in stack_advisor.py -- 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 ] Swapan Shridhar updated AMBARI-16921: - Description: 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. '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' was: 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. > 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. > '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' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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' configs
[ https://issues.apache.org/jira/browse/AMBARI-16921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-16921: - 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 (was: Yarn minimum container size calculation problem in stack advisor) > 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: 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. > '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' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14849) Support HBase REST gateway
[ https://issues.apache.org/jira/browse/AMBARI-14849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14849: Description: Currently admin has to use command line to start HBase REST gateway. Support for starting REST gateway through Ambari should be added. This would make operations involving REST gateway more user friendly. was: Currently admin has to use command line to start HBase REST gateway. Support for starting REST gateway through Ambari should be added. This would make operations involving REST gateway more user friendly. > Support HBase REST gateway > -- > > Key: AMBARI-14849 > URL: https://issues.apache.org/jira/browse/AMBARI-14849 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > Currently admin has to use command line to start HBase REST gateway. > Support for starting REST gateway through Ambari should be added. > This would make operations involving REST gateway more user friendly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated AMBARI-16171: Attachment: AMBARI-16171.addendum.patch Looks like I goofed up the .009 with the python unit tests after my last rebase. Here's a small addendum to fix it up. > 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-16827) expose vm.overcommit_ratio on hawq-sysctl-env
[ https://issues.apache.org/jira/browse/AMBARI-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16827: Resolution: Fixed Status: Resolved (was: Patch Available) > 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 >Assignee: 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] [Updated] (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:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16917: Resolution: Fixed Assignee: bhuvnesh chaudhary Status: Resolved (was: Patch Available) > 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] [Assigned] (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:all-tabpanel ] bhuvnesh chaudhary reassigned AMBARI-16827: --- Assignee: bhuvnesh chaudhary > 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 >Assignee: 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] [Updated] (AMBARI-16941) Cluster install wizard hangs and cannot proceed if Knox is the only service selected for install
[ https://issues.apache.org/jira/browse/AMBARI-16941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-16941: Status: Patch Available (was: In Progress) > Cluster install wizard hangs and cannot proceed if Knox is the only service > selected for install > > > Key: AMBARI-16941 > URL: https://issues.apache.org/jira/browse/AMBARI-16941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-16941.patch > > > 1. Open Cluster Install Wizard and select Knox as the only service to install. > 2. On step6 of the wizard (Assign Slaves and Clients), you cannot click on > Next and proceed because of an error in the javascript code. -- 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: Description: 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] [Updated] (AMBARI-16941) Cluster install wizard hangs and cannot proceed if Knox is the only service selected for install
[ https://issues.apache.org/jira/browse/AMBARI-16941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-16941: Attachment: AMBARI-16941.patch > Cluster install wizard hangs and cannot proceed if Knox is the only service > selected for install > > > Key: AMBARI-16941 > URL: https://issues.apache.org/jira/browse/AMBARI-16941 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-16941.patch > > > 1. Open Cluster Install Wizard and select Knox as the only service to install. > 2. On step6 of the wizard (Assign Slaves and Clients), you cannot click on > Next and proceed because of an error in the javascript code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16941) Cluster install wizard hangs and cannot proceed if Knox is the only service selected for install
Sangeeta Ravindran created AMBARI-16941: --- Summary: Cluster install wizard hangs and cannot proceed if Knox is the only service selected for install Key: AMBARI-16941 URL: https://issues.apache.org/jira/browse/AMBARI-16941 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: trunk, 2.4.0 Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran 1. Open Cluster Install Wizard and select Knox as the only service to install. 2. On step6 of the wizard (Assign Slaves and Clients), you cannot click on Next and proceed because of an error in the javascript code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi resolved AMBARI-16171. --- Resolution: Fixed Committed patch 9 to trunk and branch-2.4 > 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 > 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 > > > 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] [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&focusedCommentId=15304963#comment-15304963 ] Hadoop QA commented on AMBARI-16665: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806690/AMBARI-16665.v2.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7038//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7038//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.branch24.v2.patch, AMBARI-16665.patch, AMBARI-16665.v2.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-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: Attachment: AMBARI-16940.patch > 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 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi updated AMBARI-16171: -- Fix Version/s: 2.4.1 > 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 > > > 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-16171) Changes to Phoenix QueryServer Kerberos configuration
[ https://issues.apache.org/jira/browse/AMBARI-16171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated AMBARI-16171: Attachment: AMBARI-16171.009.patch .009 is .007 plus changes to stack advisor to append configuration to hadoop.proxyuser.HTTP.hosts only when there are PQS hosts in the cluster. > 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 > 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 > > > 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] [Commented] (AMBARI-16908) Different repositories show same versions of services
[ https://issues.apache.org/jira/browse/AMBARI-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304938#comment-15304938 ] Zhe (Joe) Wang commented on AMBARI-16908: - +1 for the patch > Different repositories show same versions of services > - > > Key: AMBARI-16908 > URL: https://issues.apache.org/jira/browse/AMBARI-16908 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-16908.patch > > > Different repositories show same versions of services. The versions are from > the last installed repo. > The order of repo is incorrect in some scenarios. -- 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&focusedCommentId=15304926#comment-15304926 ] Josh Elser commented on AMBARI-16171: - For those following along, I did update reviewboard with a new patch. > 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 > 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 > > > 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] [Created] (AMBARI-16940) VDF: support for selecting enabled + default Stacks
Jaimin D Jetly created AMBARI-16940: --- Summary: 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 -- 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&focusedCommentId=15304918#comment-15304918 ] Hadoop QA commented on AMBARI-16927: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806630/AMBARI-16927.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-web. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7037//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7037//console This message is automatically generated. > 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] [Commented] (AMBARI-16930) Message text is missing in EU wizard screens that require manual intervention
[ https://issues.apache.org/jira/browse/AMBARI-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304894#comment-15304894 ] Hadoop QA commented on AMBARI-16930: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806644/AMBARI-16930.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-web. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7036//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7036//console This message is automatically generated. > Message text is missing in EU wizard screens that require manual intervention > - > > Key: AMBARI-16930 > URL: https://issues.apache.org/jira/browse/AMBARI-16930 > 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-16930.patch > > > *Steps* > # Install HDP 2.4.2.0 with Ambari 2.4.0.0 > # Start EU to 2.5.0.0 > Observed that in some of the screens that require manual intervention, the > message text is missing in the upper pane. This usually happens after hitting > 'Proceed' in the first message under an Upgrade Group. Subsequent messages do > not show up the text > Screenshots attached -- 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&focusedCommentId=15304881#comment-15304881 ] Weiqing Yang commented on AMBARI-16755: --- Thank you for the review. > 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-16922) Remove LogSearch dependency for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-16922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304870#comment-15304870 ] Hudson commented on AMBARI-16922: - FAILURE: Integrated in Ambari-trunk-Commit #4944 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4944/]) AMBARI-16922. Remove LogSearch dependency for Ranger (Mugdha Varadkar (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b30a7b5614b136b4ca267b5fd1d6ab920332c0e3]) * ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_features.json * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py * ambari-common/src/main/python/resource_management/libraries/functions/constants.py * ambari-common/src/main/python/resource_management/libraries/functions/stack_features.py * ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * ambari-server/src/main/resources/common-services/RANGER/0.6.0/metainfo.xml * ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_admin.py > 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-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&focusedCommentId=15304871#comment-15304871 ] Hudson commented on AMBARI-16906: - FAILURE: Integrated in Ambari-trunk-Commit #4944 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4944/]) AMBARI-16906 Express upgrade: Oozie failed to start when user name and (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a94a03f55605294e7aed061b9673c87c262d16f6]) * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py > 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] [Resolved] (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:all-tabpanel ] Alejandro Fernandez resolved AMBARI-16755. -- Resolution: Fixed Pushed to trunk, commit 048ef3fa61be82fdae795c6c466d60c053b1f8f2 branch-2.4, commit c0e8e43f095079784f6b72b2e3e6b926d806eb9c > 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-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&focusedCommentId=15304859#comment-15304859 ] Hadoop QA commented on AMBARI-12885: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806647/AMBARI-12885.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 36 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 Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7035//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7035//console This message is automatically generated. > 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-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:all-tabpanel ] Alejandro Fernandez updated AMBARI-16755: - Fix Version/s: 2.4.0 > 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] [Updated] (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:all-tabpanel ] Alejandro Fernandez updated AMBARI-16755: - Affects Version/s: 2.4.0 > 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] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-16887: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk and branch-2.4. > [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] [Updated] (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:all-tabpanel ] Weiqing Yang updated AMBARI-16755: -- Attachment: AMBARI-16755_2.patch > 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 >Reporter: Jeff Zhang >Assignee: Weiqing Yang > Attachments: AMBARI-16755-1.patch, AMBARI-16755_2.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Balázs Bence Sári updated AMBARI-16939: --- Status: Patch Available (was: Open) > '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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) > at > org.apache.ambari.server.upgrade.AbstractUpgrade
[jira] [Updated] (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:all-tabpanel ] Balázs Bence Sári updated AMBARI-16939: --- Attachment: (was: patch1-trunk.diff) > '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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) > at > org.apache.ambari.server.upgrade.AbstractUpg
[jira] [Updated] (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:all-tabpanel ] Balázs Bence Sári updated AMBARI-16939: --- Status: Open (was: Patch Available) > '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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) > at > org.apache.ambari.server.upgrade.AbstractUpgrade
[jira] [Updated] (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:all-tabpanel ] Balázs Bence Sári updated AMBARI-16939: --- Attachment: patch2-trunk.diff > '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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) > at > org.apache.ambari.server.upgrade.AbstractUpgradeCatalog
[jira] [Updated] (AMBARI-16908) Different repositories show same versions of services
[ https://issues.apache.org/jira/browse/AMBARI-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-16908: - Attachment: AMBARI-16908.patch > Different repositories show same versions of services > - > > Key: AMBARI-16908 > URL: https://issues.apache.org/jira/browse/AMBARI-16908 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-16908.patch > > > Different repositories show same versions of services. The versions are from > the last installed repo. > The order of repo is incorrect in some scenarios. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16908) Different repositories show same versions of services
[ https://issues.apache.org/jira/browse/AMBARI-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-16908: - Status: Patch Available (was: Open) > Different repositories show same versions of services > - > > Key: AMBARI-16908 > URL: https://issues.apache.org/jira/browse/AMBARI-16908 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-16908.patch > > > Different repositories show same versions of services. The versions are from > the last installed repo. > The order of repo is incorrect in some scenarios. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16908) Different repositories show same versions of services
[ https://issues.apache.org/jira/browse/AMBARI-16908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304757#comment-15304757 ] Xi Wang commented on AMBARI-16908: -- 27802 tests complete (29 seconds) 154 tests pending > Different repositories show same versions of services > - > > Key: AMBARI-16908 > URL: https://issues.apache.org/jira/browse/AMBARI-16908 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang > Labels: vdf > Fix For: 2.4.0 > > Attachments: AMBARI-16908.patch > > > Different repositories show same versions of services. The versions are from > the last installed repo. > The order of repo is incorrect in some scenarios. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Balázs Bence Sári updated AMBARI-16939: --- Status: Patch Available (was: In Progress) > '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: patch1-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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) > at > org.apache.ambari.server.upgrade.Abstract
[jira] [Comment Edited] (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&focusedCommentId=15304738#comment-15304738 ] Balázs Bence Sári edited comment on AMBARI-16939 at 5/27/16 8:43 PM: - Patch added. was (Author: bsari): Patch > '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: patch1-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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.
[jira] [Updated] (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:all-tabpanel ] Balázs Bence Sári updated AMBARI-16939: --- Attachment: patch1-trunk.diff Patch > '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: patch1-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 add foreign key constraint > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) > at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) > at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) > at > org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) > at > org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) > at > org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) > at > org.apache.ambari.server.upgrade.AbstractUpgrade
[jira] [Created] (AMBARI-16939) 'ambari-server upgrade' is failed : Error executing schema upgrade [upgrade from 2200 to 2400]
Balázs Bence Sári created AMBARI-16939: -- Summary: '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 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 add foreign key constraint at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:959) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3870) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2546) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2504) at com.mysql.jdbc.StatementImpl.executeInternal(StatementImpl.java:840) at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:740) at org.apache.ambari.server.orm.DBAccessorImpl.executeQuery(DBAccessorImpl.java:800) at org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:470) at org.apache.ambari.server.orm.DBAccessorImpl.addFKConstraint(DBAccessorImpl.java:435) at org.apache.ambari.server.upgrade.UpgradeCatalog240.createServiceComponentHistoryTable(UpgradeCatalog240.java:1375) at org.apache.ambari.server.upgrade.UpgradeCatalog240.executeDDLUpdates(UpgradeCatalog240.java:239) at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:656) at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:201) ... 1 more ERROR: Error executing schema upgrade, please check the server logs. ERROR: Ambari server upgrade failed. Please look at /var/log/ambari-server/ambari-server.log, for more details. ERROR: Exiting with exit code 11. REASON: Schema
[jira] [Updated] (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:all-tabpanel ] Jonathan Hurley updated AMBARI-16913: - Attachment: AMBARI-16913.patch > 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 need > 100's upon 100's of threads pulling in the same JMX data > This data should never be queried for directly as part of the incoming REST > requests. Instead, an autonomous pool of threads should be constantly > retrieving these point-in-time metrics and updating a cache. The cache is > then used to service all live REST requests. > - On the first request to a resource, a cache miss occurs and no data is > returned. I think this is acceptable since metrics take a few moments to > populate anyway right now. As the web client polls, the next request should > pickup the newly cached metrics. > - Only URLs which are being asked for by incoming REST requests should be > considered for retrieval. After sometime, if they haven't been requested, > then the headless threadpool can stop trying to update their data > - All JMX data will be parsed and stored in-memory, in an expiring cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Jonathan Hurley updated AMBARI-16913: - Status: Patch Available (was: Open) > 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 need > 100's upon 100's of threads pulling in the same JMX data > This data should never be queried for directly as part of the incoming REST > requests. Instead, an autonomous pool of threads should be constantly > retrieving these point-in-time metrics and updating a cache. The cache is > then used to service all live REST requests. > - On the first request to a resource, a cache miss occurs and no data is > returned. I think this is acceptable since metrics take a few moments to > populate anyway right now. As the web client polls, the next request should > pickup the newly cached metrics. > - Only URLs which are being asked for by incoming REST requests should be > considered for retrieval. After sometime, if they haven't been requested, > then the headless threadpool can stop trying to update their data > - All JMX data will be parsed and stored in-memory, in an expiring cache -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (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:all-tabpanel ] Sivaguru Kannan updated AMBARI-16915: - Description: 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. was: The Ambari change, This is in reference with your change, https://github.com/apache/ambari/commit/89fd30b40f3108bfcbcc73eb2d74c94a2ba14a7a 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. > 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] [Updated] (AMBARI-16938) Deploy: UI: Hive_metastore not started
[ https://issues.apache.org/jira/browse/AMBARI-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-16938: --- Description: 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} was: 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://172.22.104.161/hivedb' hiveuser PROTECTED com.mysql.jdbc.Driver'] {'path': ['/usr/sbin:/sbin:/usr/local/bin:/bin:/usr/bin'], 'tries': 5, 'try_sleep': 10} > 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] [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: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- 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: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16938) Deploy: UI: Hive_metastore not started
[ https://issues.apache.org/jira/browse/AMBARI-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-16938: --- Attachment: AMBARI-16938.patch > 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://172.22.104.161/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] [Updated] (AMBARI-16933) VDF should use package-version for the os, not the release
[ https://issues.apache.org/jira/browse/AMBARI-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-16933: --- Status: Patch Available (was: In Progress) > VDF should use package-version for the os, not the release > -- > > Key: AMBARI-16933 > URL: https://issues.apache.org/jira/browse/AMBARI-16933 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.4.0 > > Attachments: AMBARI-16933.patch > > > The aggregated VDF skips package-version as it is defined in the {{release}} > element. This is incorrect as it implies that information is consistent for > all repositories in the VDF. The element has been moved, so code needs to > account for that when formulating commands to the agent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16933) VDF should use package-version for the os, not the release
[ https://issues.apache.org/jira/browse/AMBARI-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-16933: --- Attachment: AMBARI-16933.patch > VDF should use package-version for the os, not the release > -- > > Key: AMBARI-16933 > URL: https://issues.apache.org/jira/browse/AMBARI-16933 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole > Fix For: 2.4.0 > > Attachments: AMBARI-16933.patch > > > The aggregated VDF skips package-version as it is defined in the {{release}} > element. This is incorrect as it implies that information is consistent for > all repositories in the VDF. The element has been moved, so code needs to > account for that when formulating commands to the agent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16938) Deploy: UI: Hive_metastore not started
[ https://issues.apache.org/jira/browse/AMBARI-16938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-16938: --- Status: Patch Available (was: Open) > 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://172.22.104.161/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] [Created] (AMBARI-16938) Deploy: UI: Hive_metastore not started
Vitaly Brodetskyi created AMBARI-16938: -- Summary: 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 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://172.22.104.161/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] [Updated] (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:all-tabpanel ] Sivaguru Kannan updated AMBARI-16915: - Status: Patch Available (was: Open) > 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 your change, > https://github.com/apache/ambari/commit/89fd30b40f3108bfcbcc73eb2d74c94a2ba14a7a > 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] [Updated] (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:all-tabpanel ] Sivaguru Kannan updated AMBARI-16915: - Attachment: AMBARI-16915_branch-2.4.patch > 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 your change, > https://github.com/apache/ambari/commit/89fd30b40f3108bfcbcc73eb2d74c94a2ba14a7a > 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] [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: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- 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, AMBARI-16875.patch > > > in case of member attribute value looks like this: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15304671#comment-15304671 ] Hudson commented on AMBARI-16851: - FAILURE: Integrated in Ambari-trunk-Commit #4943 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4943/]) AMBARI-16851. Cluster operator and cluster admin not allowed to install (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=055b63150cb934c11986c70850638064103ff7b0]) * ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * ambari-server/src/test/resources/custom_action_definitions/cust_action_definitions1.xml * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActionResourceProviderTest.java * ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java * ambari-server/src/test/java/org/apache/ambari/server/customactions/ActionDefinitionManagerTest.java * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionManager.java * ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinition.java * ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml * ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java * ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionSpec.java Revert "AMBARI-16851. Cluster operator and cluster admin not allowed to (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1529af0b5795ba9c6b9019b02fe08570b1857f1f]) * ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java * ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog240.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java * ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * ambari-server/src/main/resources/custom_action_definitions/system_action_definitions.xml * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ActionResourceProviderTest.java * ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionManager.java * ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java * ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RequestResourceProvider.java * ambari-server/src/test/java/org/apache/ambari/server/customactions/ActionDefinitionManagerTest.java * ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinition.java * ambari-server/src/test/resources/custom_action_definitions/cust_action_definitions1.xml * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionSpec.java * ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql AMBARI-16851. Cluster operator and cluster admin not allowed to install (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=87b0a24384fc592bd1c54b50e7095e849a6fc3a2]) * ambari-server/src/main/java/org/apache/ambari/server/customactions/ActionDefinitionManager.java * ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestResourceProviderTest.java * ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog240Test.java * amba
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15304674#comment-15304674 ] Hudson commented on AMBARI-16923: - FAILURE: Integrated in Ambari-trunk-Commit #4943 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4943/]) AMBARI-16923. Fix for getting the 'hive.llap.daemon.queue.name' config (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4eab7d053e8f6fae2f9a2230e9ac0c273db8d232]) * 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 > 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-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&focusedCommentId=15304673#comment-15304673 ] Hudson commented on AMBARI-16926: - FAILURE: Integrated in Ambari-trunk-Commit #4943 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4943/]) AMBARI-16926 Add ability to query all hosts using hostname=% through AMS (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66c6b06c3124702bfcb3c1de4bb9b2defa1a9d14]) * ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestPhoenixTransactSQL.java * ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/DefaultCondition.java > 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-16912) Oozie and Hive Server start fail during EU with missing DB class exception
[ https://issues.apache.org/jira/browse/AMBARI-16912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304672#comment-15304672 ] Hudson commented on AMBARI-16912: - FAILURE: Integrated in Ambari-trunk-Commit #4943 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4943/]) AMBARI-16912. Oozie and Hive Server start fail during EU with missing DB (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=78bde257f6f4a2fc48577a4b27c4b2aa70a339cd]) * ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py * ambari-server/src/main/python/ambari_server/dbConfiguration.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service_interactive.py * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py * ambari-server/src/main/python/ambari_server/serverSetup.py * ambari-server/src/main/python/ambari_server/serverUpgrade.py * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_service.py > Oozie and Hive Server start fail during EU with missing DB class exception > -- > > Key: AMBARI-16912 > URL: https://issues.apache.org/jira/browse/AMBARI-16912 > 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-16912.patch > > > Steps > Deploy HDP 2.4.0.0 cluster with Ambari 2.2.1.1 (Secure, HA cluster, mysql DB) > Upgrade Ambari to 2.4.0.0 > Perform Express Upgrade to HDP-2.5.0.0-555 > Result > Errors seen during start of Hive Server and Oozie -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16937) Make adding an Oozie Server available from Service Actions
Paul Codding created AMBARI-16937: - Summary: Make adding an Oozie Server available from Service Actions Key: AMBARI-16937 URL: https://issues.apache.org/jira/browse/AMBARI-16937 Project: Ambari Issue Type: New Feature Reporter: Paul Codding Fix For: 3.0.0 Components like HBase, and Storm have additional master component additions available from the Service Actions menu. For consistency purposes, the suggestion to add the ability to add an additional Ooze Server. Suggestion is "+ Add Oozie Server", just like we have for HBase "+ Add HBase Master". -- 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: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- 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: > ";;cn=myCn,dc=apache,dc=org", then sync stop working. > adding 2 new properties (to find the dn or the id of the member): > {{"authentication.ldap.sync.userMemberReplacePattern"}} > {{"authentication.ldap.sync.groupMemberReplacePattern"}} > These values are empty by default. > Example usage: > If we got this as ldapsearch response for group member > "member=";;cn=myCn,dc=apache,dc=org", > We need to define a regex which contains member group to specify the location > of the DN or id e.g.{{(?.\*)}} > authentication.ldap.sync.userMemberReplacePattern={{(?.\*);(?.\*);(?.\*)}} > Then the result will be: "cn=myCn,dc=apache,dc=org" > also added 2 another new properties for alternative solution: > {{"authentication.ldap.sync.userMemberFilter"}} > {{"authentication.ldap.sync.groupMemberFilter"}} > These values are also empty by default. > Example usage: > memberUid=mymemberId > then you can specify the filter for user sync: > {{"authentication.ldap.sync.userMemberFilter=(&(objectclass=posixaccount)(uid=\{member\}))"}} > That filter will be used (with the baseDN) for gather user with the memberUid: > {{(&(objectclass=posixaccount)(uid=mymemberid))}} -- 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_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, AMBARI-16437_trunk_02.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-16893) Ambari install failure due to zeppelin service install bug
[ https://issues.apache.org/jira/browse/AMBARI-16893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304658#comment-15304658 ] Hadoop QA commented on AMBARI-16893: {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12806655/AMBARI-16893-trunk%2B2.4-v2.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/7033//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7033//console This message is automatically generated. > Ambari install failure due to zeppelin service install bug > -- > > Key: AMBARI-16893 > URL: https://issues.apache.org/jira/browse/AMBARI-16893 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 > Environment: CentOS 6.6 >Reporter: Renjith Kamath > Fix For: 2.4.0 > > Attachments: AMBARI-16893-trunk+2.4-v1.patch, > AMBARI-16893-trunk+2.4-v2.patch > > > Service install fails on CentOS 6.6 with following error. Unable to run > setup_snapshot.sh > {code:title=stderr} > "Traceback (most recent call last): > File > \"/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py\", > line 233, in > Master().execute() > File > \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\", > line 254, in execute > method(env) > File > \"/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/master.py\", > line 66, in install > user=params.zeppelin_user) > 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 > '/var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/setup_snapshot.sh > /usr/hdp/current/zeppelin-server/lib c6401.ambari.apache.org 9083 10001 > c6401.ambari.apache.org 9995 True > /var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package > /usr/jdk64/jdk1.8.0_60 >> /var/log/zeppelin/zeppelin-setup.log' returned 126. > -bash: > /var/lib/ambari-agent/cache/common-services/ZEPPELIN/0.6.0.2.5/package/scripts/setup_snapshot.sh: > Permission denied", > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16936) BP deploy to put default password for hawq_password
[ https://issues.apache.org/jira/browse/AMBARI-16936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-16936: Attachment: AMBARI-16936.patch > BP deploy to put default password for hawq_password > --- > > Key: AMBARI-16936 > URL: https://issues.apache.org/jira/browse/AMBARI-16936 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-16936.patch > > > BP deploy to put default password for hawq_password -- This message was sent by Atlassian JIRA (v6.3.4#6332)