Review Request 37040: Malformed Alert Data Can Prevent Alerts From Reporting
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37040/ --- Review request for Ambari, Alejandro Fernandez and Sid Wagle. Bugs: AMBARI-12622 https://issues.apache.org/jira/browse/AMBARI-12622 Repository: ambari Description --- If there is malformed template text in an alert definition, it will prevent alerts from being reported correctly. Diffs - ambari-agent/src/main/python/ambari_agent/AlertSchedulerHandler.py c41397d ambari-agent/src/main/python/ambari_agent/alerts/base_alert.py 9151796 ambari-agent/src/main/python/ambari_agent/alerts/metric_alert.py 6bcdacd ambari-agent/src/test/python/ambari_agent/TestAlerts.py 7b64445 Diff: https://reviews.apache.org/r/37040/diff/ Testing --- mvn clean test Thanks, Jonathan Hurley
[jira] [Updated] (AMBARI-12622) Malformed Alert Data Can Prevent Alerts From Reporting
[
https://issues.apache.org/jira/browse/AMBARI-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-12622:
-
Attachment: AMBARI-12622.patch
Malformed Alert Data Can Prevent Alerts From Reporting
--
Key: AMBARI-12622
URL: https://issues.apache.org/jira/browse/AMBARI-12622
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12622.patch
If there is malformed template text in an alert definition, it will prevent
alerts from being reported correctly:
{code}
INFO 2015-07-23 14:10:15,209 scheduler.py:287 - Adding job tentatively -- it
will be properly scheduled when the scheduler starts
INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:318 - [AlertScheduler]
Scheduling datanode_process with UUID 43536b17-596a-4f7d-87e6-c9034b2b99bc
INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:134 - [AlertScheduler]
Starting ambari_agent.apscheduler.scheduler.Scheduler object at 0x10ea910;
currently running: False
INFO 2015-07-23 14:10:17,219 hostname.py:87 - Read public hostname
'cn105-10.l42scl.hortonworks.com' using socket.getfqdn()
INFO 2015-07-23 14:11:15,271 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1
--hiveconf hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/',
'/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:11:15,274 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:12:15,277 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:12:15,284 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1
--hiveconf hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/',
'/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user':
'ambari-qa', 'timeout': 30}
ERROR 2015-07-23 14:12:15,293 scheduler.py:520 - Job
28cad184-0e94-4b19-af31-56ab2c1d0a74 (trigger: interval[0:02:00], next run
at: 2015-07-23 14:14:15.207467) raised an exception
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/ambari_agent/apscheduler/scheduler.py,
line 512, in _run_job
retval = job.func(*job.args, **job.kwargs)
File
/usr/lib/python2.6/site-packages/ambari_agent/AlertSchedulerHandler.py,
line 114, in lambda
return lambda: alert_def.collect()
File /usr/lib/python2.6/site-packages/ambari_agent/alerts/base_alert.py,
line 153, in collect
data['text'] = res_base_text.format(*res[1])
ValueError: Unknown format code 'd' for object of type 'float'
INFO 2015-07-23 14:13:15,264 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1
--hiveconf hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/',
'/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:13:15,272 logger.py:66 - Execute['! beeline -u
Re: Review Request 37003: Add Data Visualization to Hive View
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37003/ --- (Updated Aug. 3, 2015, 3:33 p.m.) Review request for Ambari and Yusaku Sako. Changes --- Fixed build error. Bugs: AMBARI-12615 https://issues.apache.org/jira/browse/AMBARI-12615 Repository: ambari Description --- Refer to the description in AMBARI-12615 Diffs (updated) - ambari-web/app/views/main/views/details.js e90cb20 contrib/views/hive/pom.xml 39f6848 contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/browser/HiveBrowserService.java a0d44f5 contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/JobService.java 526f13f contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/ResultsPaginationController.java 18152ad contrib/views/hive/src/main/resources/ui/hive-web/.jshintrc c1fe863 contrib/views/hive/src/main/resources/ui/hive-web/app/components/visualization-tabs-widget.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/query-tabs.js 4f5176c contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/visualization-ui.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/initializers/i18n.js af5e3a7 contrib/views/hive/src/main/resources/ui/hive-web/app/templates/components/visualization-tabs-widget.hbs PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/templates/visualization-ui.hbs PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/utils/constants.js e4e445a contrib/views/hive/src/main/resources/ui/hive-web/app/views/visualization-ui.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/bower.json 37ea901 Diff: https://reviews.apache.org/r/37003/diff/ Testing --- Tested manually with different datasets of different size. Tested switching to visualization tab with multiple SQL tabs having different queries. Tested switching between the two visualization tabs multiple times. Tested with upto 3 rows in the resultset with all possible combinations of scale and chart types. Tested with Google Chrome, Safari, Firefox and Internet Explorer 10. Tested end to end with Ambari Web and Hive View. Existing Ambari Web unit tests pass. 6482 tests complete (22 seconds) 94 tests pending [INFO] [INFO] --- apache-rat-plugin:0.11:check (default) @ ambari-web --- [INFO] 51 implicit excludes (use -debug for more details). [INFO] Exclude: .idea/** [INFO] Exclude: package.json [INFO] Exclude: public/** [INFO] Exclude: public-static/** [INFO] Exclude: app/assets/** [INFO] Exclude: vendor/** [INFO] Exclude: node_modules/** [INFO] Exclude: node/** [INFO] Exclude: npm-debug.log [INFO] 1169 resources included (use -debug for more details) Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. Compiler warnings: WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.' Warning: org.apache.xerces.parsers.SAXParser: Feature 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 1169 licence. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 49.809s [INFO] Finished at: Fri Jul 31 18:39:11 PDT 2015 [INFO] Final Memory: 12M/439M [INFO] Thanks, Vivek Ratnavel Subramanian
[jira] [Updated] (AMBARI-12594) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
[ https://issues.apache.org/jira/browse/AMBARI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-12594: Attachment: (was: AMBARI-12594.2.patch) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- Key: AMBARI-12594 URL: https://issues.apache.org/jira/browse/AMBARI-12594 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 2.1.1 Attachments: AMBARI-12594.2.patch, AMBARI-12594.patch RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12594) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
[ https://issues.apache.org/jira/browse/AMBARI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-12594: Attachment: AMBARI-12594.2.patch RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- Key: AMBARI-12594 URL: https://issues.apache.org/jira/browse/AMBARI-12594 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 2.1.1 Attachments: AMBARI-12594.2.patch, AMBARI-12594.patch RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36943: RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/ --- (Updated Aug. 3, 2015, 3:52 p.m.) Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, and Nate Cole. Changes --- Moved to Script.is_hdp_stack_greater_or_equal, adjusted unit tests, retested RU with latest changes Summary (updated) - RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Bugs: AMBARI-12594 https://issues.apache.org/jira/browse/AMBARI-12594 Repository: ambari Description --- RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Diffs (updated) - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py d599b8c ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 3dda481 ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py 37dcb20 Diff: https://reviews.apache.org/r/36943/diff/ Testing --- OK -- Total run:808 Total errors:0 Total failures:0 OK Performing tests on live cluster Thanks, Dmitro Lisnichenko
[jira] [Commented] (AMBARI-12619) ambari agent return exit code 0 even when start action fails
[ https://issues.apache.org/jira/browse/AMBARI-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651925#comment-14651925 ] Hudson commented on AMBARI-12619: - SUCCESS: Integrated in Ambari-branch-2.1 #309 (See [https://builds.apache.org/job/Ambari-branch-2.1/309/]) AMBARI-12619. ambari agent return exit code 0 even when start action fails (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=c75d58868c0ffc4a7a2835a76dbc888372979a49) * ambari-agent/etc/init.d/ambari-agent ambari agent return exit code 0 even when start action fails Key: AMBARI-12619 URL: https://issues.apache.org/jira/browse/AMBARI-12619 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 When service ambari-agent start fails, the exit code should be non-zero. The script (/etc/init.d/ambari-agent) currently returns 0 no matter what. We use the exit code in our agent to determine whether we need to retry starting up ambari-agent or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12621) FE: Going to a service heatmap makes a call to old heatmap first
[ https://issues.apache.org/jira/browse/AMBARI-12621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651933#comment-14651933 ] Andrii Babiichuk commented on AMBARI-12621: --- +1 for the patch FE: Going to a service heatmap makes a call to old heatmap first Key: AMBARI-12621 URL: https://issues.apache.org/jira/browse/AMBARI-12621 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.2 Attachments: AMBARI-12621.patch I went to HDFS heatmaps which loaded in 10s. Then I went to HBase heatmaps, but the first call was still to the Datanode heatmaps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12621) FE: Going to a service heatmap makes a call to old heatmap first
Andrii Tkach created AMBARI-12621: - Summary: FE: Going to a service heatmap makes a call to old heatmap first Key: AMBARI-12621 URL: https://issues.apache.org/jira/browse/AMBARI-12621 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.2 I went to HDFS heatmaps which loaded in 10s. Then I went to HBase heatmaps, but the first call was still to the Datanode heatmaps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12621) FE: Going to a service heatmap makes a call to old heatmap first
[ https://issues.apache.org/jira/browse/AMBARI-12621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-12621: -- Attachment: AMBARI-12621.patch FE: Going to a service heatmap makes a call to old heatmap first Key: AMBARI-12621 URL: https://issues.apache.org/jira/browse/AMBARI-12621 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.2 Attachments: AMBARI-12621.patch I went to HDFS heatmaps which loaded in 10s. Then I went to HBase heatmaps, but the first call was still to the Datanode heatmaps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12621) FE: Going to a service heatmap makes a call to old heatmap first
[ https://issues.apache.org/jira/browse/AMBARI-12621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651930#comment-14651930 ] Andrii Tkach commented on AMBARI-12621: --- 6701 tests complete (12 seconds) 94 tests pending FE: Going to a service heatmap makes a call to old heatmap first Key: AMBARI-12621 URL: https://issues.apache.org/jira/browse/AMBARI-12621 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.1.2 Attachments: AMBARI-12621.patch I went to HDFS heatmaps which loaded in 10s. Then I went to HBase heatmaps, but the first call was still to the Datanode heatmaps. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12595) Blueprint deployments should refresh configuration on all commands
[ https://issues.apache.org/jira/browse/AMBARI-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652049#comment-14652049 ] Hudson commented on AMBARI-12595: - SUCCESS: Integrated in Ambari-branch-2.1 #310 (See [https://builds.apache.org/job/Ambari-branch-2.1/310/]) AMBARI-12595. Blueprint deployments should refresh configuration on all commands. (rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d03bc09e41e30b4f108ad83b9b239d7bf9d140bd) * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java Blueprint deployments should refresh configuration on all commands -- Key: AMBARI-12595 URL: https://issues.apache.org/jira/browse/AMBARI-12595 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Robert Nettleton Assignee: Robert Nettleton Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12595.patch Original Estimate: 4h Remaining Estimate: 4h During Blueprint deployments of large clusters, there are intermittent failures where configuration appears to not be sychronized with the rest of the cluster. This can cause un-resolved configuration to be sent down to a node, and this will subsequently cause install and start failures. When a Blueprint deployment is in process, the AmbariManagementController implementation should force a refresh on the config if each ExecutionCommand prior to sending it down to the cluster nodes. I'm working on a fix for this, and will be submitting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12620) Wrong 'Affected components' list shown
[ https://issues.apache.org/jira/browse/AMBARI-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652050#comment-14652050 ] Hudson commented on AMBARI-12620: - SUCCESS: Integrated in Ambari-branch-2.1 #310 (See [https://builds.apache.org/job/Ambari-branch-2.1/310/]) AMBARI-12620. Wrong 'Affected components' list shown (alexantonenko) (hiveww: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=0a2df914919c320f4104b751aadb854948192515) * ambari-web/app/mappers/component_config_mapper.js Wrong 'Affected components' list shown -- Key: AMBARI-12620 URL: https://issues.apache.org/jira/browse/AMBARI-12620 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12620.patch On deployed cluster: Change 'NodeManager Java heap size' property. Save changes. Check affected components. 'ATS' and 'ResourceManager' shown as affected, but not 'NodeManager' Also it shows '2 hosts affected'. But if I do 'Restart All Affected'. All components of YARN on all hosts are restarted. Same for 'DataNode maximum Java heap size' only 'NameNode' and 'SNameNode' shown as affected. But restart affects all hosts and all HDFS components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 37060: Ambari does not allow hard limit for hdfs daemons to be modified
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37060/ --- Review request for Ambari, Alejandro Fernandez, Mahadev Konar, and Sumit Mohanty. Bugs: AMBARI-12626 https://issues.apache.org/jira/browse/AMBARI-12626 Repository: ambari Description --- Template example: src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 The open files limit is hardcoded. User has to set this manually for running NN and then edit this file and restart. Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml d33cfda ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py c53508b ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 d58a6f5 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml 64653b5 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py 35b896f ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hive.conf.j2 8b7f8bd ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml 14ae20b ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml c16c3ac ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py 4443476 ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/mapreduce.conf.j2 b996645 ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/yarn.conf.j2 3bd7a45 Diff: https://reviews.apache.org/r/37060/diff/ Testing --- Manually verified Thanks, Sid Wagle
[jira] [Commented] (AMBARI-12572) Config versions shows not all versions after save
[ https://issues.apache.org/jira/browse/AMBARI-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652818#comment-14652818 ] Hudson commented on AMBARI-12572: - SUCCESS: Integrated in Ambari-trunk-Commit #3212 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3212/]) AMBARI-12572-2. Config versions shows not all versions after save.(xiwang) (xiwang: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=45e8ca90c5645e2d3cbd41c9e733227aeb2e8f69) * ambari-web/app/mappers/service_config_version_mapper.js Config versions shows not all versions after save - Key: AMBARI-12572 URL: https://issues.apache.org/jira/browse/AMBARI-12572 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12572-2.patch, AMBARI-12572-2.patch, AMBARI-12572.patch, AMBARI-12572.patch, Screen Shot 2015-07-24 at 2.04.29 PM.png 1. Go to service conf tab. 2. Add or change some properties. 3. Save config version. 4. Only current and previous version are shown. see attached. All versions appear after refreshing the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12572) Config versions shows not all versions after save
[ https://issues.apache.org/jira/browse/AMBARI-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652815#comment-14652815 ] Hudson commented on AMBARI-12572: - SUCCESS: Integrated in Ambari-branch-2.1 #314 (See [https://builds.apache.org/job/Ambari-branch-2.1/314/]) AMBARI-12572-2. Config versions shows not all versions after save.(xiwang) (xiwang: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=bc7b803208e0249b7c549fa7023f03129b26511f) * ambari-web/app/mappers/service_config_version_mapper.js Config versions shows not all versions after save - Key: AMBARI-12572 URL: https://issues.apache.org/jira/browse/AMBARI-12572 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12572-2.patch, AMBARI-12572-2.patch, AMBARI-12572.patch, AMBARI-12572.patch, Screen Shot 2015-07-24 at 2.04.29 PM.png 1. Go to service conf tab. 2. Add or change some properties. 3. Save config version. 4. Only current and previous version are shown. see attached. All versions appear after refreshing the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 37059: Ambari 2.0 - 2.1 LDAP: error code 12
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37059/ --- Review request for Ambari and Robert Levas. Bugs: AMBARI-12627 https://issues.apache.org/jira/browse/AMBARI-12627 Repository: ambari Description --- LDAP result pagination works well for large amounts of users needing to be synchronized from Active Directory, which is the common LDAP implementation. For those using ODSEE 11g, however, it's unsupported. For this reason, it would be beneficial to make this pagination option configurable. For turning off ldap search results pagination add authentication.ldap.pagination.enabled=false into ambari.properties file Diffs - ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java 50fc6a6 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java 059a228 ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java df314f1 ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java 1d8fca1 Diff: https://reviews.apache.org/r/37059/diff/ Testing --- in progress Thanks, Dmytro Sen
[jira] [Created] (AMBARI-12627) Ambari 2.0 - 2.1 LDAP: error code 12
Dmytro Sen created AMBARI-12627: --- Summary: Ambari 2.0 - 2.1 LDAP: error code 12 Key: AMBARI-12627 URL: https://issues.apache.org/jira/browse/AMBARI-12627 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 LDAP result pagination works well for large amounts of users needing to be synchronized from Active Directory, which is the common LDAP implementation. For those using ODSEE 11g, however, it's unsupported. For this reason, it would be beneficial to make this pagination option configurable. For turning off ldap search results pagination add authentication.ldap.pagination.enabled=false into ambari.properties file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 37060: Ambari does not allow hard limit for hdfs daemons to be modified
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37060/ --- (Updated Aug. 4, 2015, 12:32 a.m.) Review request for Ambari, Alejandro Fernandez, Mahadev Konar, and Sumit Mohanty. Changes --- Removed dup. Bugs: AMBARI-12626 https://issues.apache.org/jira/browse/AMBARI-12626 Repository: ambari Description --- Template example: src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 The open files limit is hardcoded. User has to set this manually for running NN and then edit this file and restart. Diffs (updated) - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml d33cfda ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py c53508b ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 d58a6f5 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml 64653b5 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py 35b896f ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hive.conf.j2 8b7f8bd ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml 14ae20b ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml c16c3ac ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py 4443476 ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/mapreduce.conf.j2 b996645 ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/yarn.conf.j2 3bd7a45 Diff: https://reviews.apache.org/r/37060/diff/ Testing --- Manually verified Thanks, Sid Wagle
[jira] [Commented] (AMBARI-12374) Unable to Start NameNode in HA Mode On HDP 2.0
[
https://issues.apache.org/jira/browse/AMBARI-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652872#comment-14652872
]
Vincent.He commented on AMBARI-12374:
-
1. I tried the patch, it does not work for me, I still get same issues when I
start MapReduce history server. (My HDFS and YARN are in good state).
2. For comments Siddharth Wagle added a comment - 23/Jul/15 01:31 , is the a
correct patch?
3. How can I validate the NameNode service resturned, I tried following
commands, there is no output, any other parameters I need to add? Do we have a
sameple command to validate what's the data been returned now?
curl -s
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
curl -s
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
thanks in advance for your great help.
Unable to Start NameNode in HA Mode On HDP 2.0
--
Key: AMBARI-12374
URL: https://issues.apache.org/jira/browse/AMBARI-12374
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12374.patch
When starting an HA NameNode cluster on HDP 2.0, the following error is seen:
{code}
2015-07-07 16:02:56,371 - Getting jmx metrics from NN failed. URL:
http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
2015-07-07 16:02:56,396 - Getting jmx metrics from NN failed. URL:
http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 316, in module
NameNode().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 216, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 81, in start
namenode(action=start, rolling_restart=rolling_restart, env=env)
File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py,
line 89, in thunk
return fn(*args, **kwargs)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 141, in namenode
create_hdfs_directories(is_active_namenode_cmd)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 198, in create_hdfs_directories
only_if=check
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 390, in action_create_on_execute
self.action_delayed(create)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 387, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 239, in action_delayed
main_resource.resource.security_enabled, main_resource.resource.logoutput)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 126, in __init__
security_enabled, run_user)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py,
line 113, in get_property_for_active_namenode
raise Fail(There is no active namenodes.)
resource_management.core.exceptions.Fail: There is no active namenodes.
{code}
Although the NameNode does actually start, a failure is recorded in the
request, stopping the rest of the cluster from coming up. This probably
because the JMX properties for Active and Standby NameNode are different in
HDP 2.0 vs HDP 2.1+:
{code:title=active jmx}
{
name : Hadoop:service=NameNode,name=FSNamesystem,
Failed to enabled HA with Ambari 2.1 and HDP 2.3
All, I tried to enabled HDFS NameNode HA with Ambari 2.1 and HDP 2.3, I failed to enable this, I did some search, the error I have is different from this issue, https://issues.apache.org/jira/browse/AMBARI-12374, but the error message I got is similar, is this a known issue? Seems some code causing active NameNode address can not be retrieved? Any issue to track this? Is there a hot fix on this? thanks Error message: 2015-08-03 02:09:35,420 - Getting jmx metrics from NN failed. URL: http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus Traceback (most recent call last): File /usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py, line 40, in get_value_from_jmx data_dict = json.loads(data) File /usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py, line 307, in loads return _default_decoder.decode(s) File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line 335, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line 353, in raw_decode raise ValueError(No JSON object could be decoded) ValueError: No JSON object could be decoded 2015-08-03 02:09:35,494 - Getting jmx metrics from NN failed. URL: http://h02.bigdata.lenovo.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus Traceback (most recent call last): File /usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py, line 40, in get_value_from_jmx data_dict = json.loads(data) File /usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py, line 307, in loads return _default_decoder.decode(s) File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line 335, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line 353, in raw_decode raise ValueError(No JSON object could be decoded) ValueError: No JSON object could be decoded Traceback (most recent call last): File /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py, line 168, in module HistoryServer().execute() File /usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py, line 218, in execute method(env) File /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py, line 91, in start self.configure(env) # FOR SECURITY File /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py, line 55, in configure yarn(name=historyserver) File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py, line 89, in thunk return fn(*args, **kwargs) File /var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py, line 72, in yarn recursive_chmod=True File /usr/lib/python2.6/site-packages/resource_management/core/base.py, line 157, in __init__ self.env.run() File /usr/lib/python2.6/site-packages/resource_management/core/environment.py, line 152, in run self.run_action(resource, action) File /usr/lib/python2.6/site-packages/resource_management/core/environment.py, line 118, in run_action provider_action() File /usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py, line 390, in action_create_on_execute self.action_delayed(create) File /usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py, line 387, in action_delayed self.get_hdfs_resource_executor().action_delayed(action_name, self) File /usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py, line 239, in action_delayed main_resource.resource.security_enabled, main_resource.resource.logoutput) File /usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py, line 126, in __init__ security_enabled, run_user) File /usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py, line 113, in get_property_for_active_namenode raise Fail(There is no active namenodes.) resource_management.core.exceptions.Fail: There is no active namenodes. Vincent (Dashuang) He
[jira] [Updated] (AMBARI-12627) Ambari 2.0 - 2.1 LDAP: error code 12
[ https://issues.apache.org/jira/browse/AMBARI-12627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-12627: Attachment: AMBARI-12627.patch Ambari 2.0 - 2.1 LDAP: error code 12 - Key: AMBARI-12627 URL: https://issues.apache.org/jira/browse/AMBARI-12627 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12627.patch LDAP result pagination works well for large amounts of users needing to be synchronized from Active Directory, which is the common LDAP implementation. For those using ODSEE 11g, however, it's unsupported. For this reason, it would be beneficial to make this pagination option configurable. For turning off ldap search results pagination add authentication.ldap.pagination.enabled=false into ambari.properties file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12374) Unable to Start NameNode in HA Mode On HDP 2.0
[
https://issues.apache.org/jira/browse/AMBARI-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652913#comment-14652913
]
Vincent.He commented on AMBARI-12374:
-
I did more try,
1. Seems the error is not related to patch as I did these call, I can get the
data (had a typo before when I executed),
[root@h02 patch]# curl -s
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
{
beans : [ {
name : Hadoop:service=NameNode,name=NameNodeStatus,
modelerType : org.apache.hadoop.hdfs.server.namenode.NameNode,
State : standby,
NNRole : NameNode,
HostAndPort : h03.bigdata.com:8020,
SecurityEnabled : false,
LastHATransitionTime : 1438594046119
} ]
}
[root@h02 patch]# curl -s
http://h02.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
{
beans : [ {
name : Hadoop:service=NameNode,name=NameNodeStatus,
modelerType : org.apache.hadoop.hdfs.server.namenode.NameNode,
State : active,
NNRole : NameNode,
HostAndPort : h02.bigdata.com:8020,
SecurityEnabled : false,
LastHATransitionTime : 1438594046591
} ]
}
[root@h02 patch]# curl -s
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
{
beans : [ {
name : Hadoop:service=NameNode,name=FSNamesystem,
modelerType : FSNamesystem,
tag.Context : dfs,
tag.HAState : standby,
tag.Hostname : h03.bigdata.com,
MissingBlocks : 0,
MissingReplOneBlocks : 0,
ExpiredHeartbeats : 0,
TransactionsSinceLastCheckpoint : -756,
TransactionsSinceLastLogRoll : 0,
LastWrittenTransactionId : 5760,
LastCheckpointTime : 1438637246806,
CapacityTotal : 377945479446528,
CapacityTotalGB : 351989.0,
CapacityUsed : 2162847744,
CapacityUsedGB : 2.0,
CapacityRemaining : 374078076620800,
CapacityRemainingGB : 348387.0,
CapacityUsedNonDFS : 3865239977984,
TotalLoad : 16,
SnapshottableDirectories : 0,
Snapshots : 0,
BlocksTotal : 588,
FilesTotal : 825,
PendingReplicationBlocks : 0,
UnderReplicatedBlocks : 0,
CorruptBlocks : 0,
ScheduledReplicationBlocks : 0,
PendingDeletionBlocks : 0,
ExcessBlocks : 0,
PostponedMisreplicatedBlocks : 0,
PendingDataNodeMessageCount : 0,
MillisSinceLastLoadedEdits : 49071,
BlockCapacity : 2097152,
StaleDataNodes : 0,
TotalFiles : 825
} ]
}
[root@h02 patch]# curl -s
http://h02.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystem
{
beans : [ {
name : Hadoop:service=NameNode,name=FSNamesystem,
modelerType : FSNamesystem,
tag.Context : dfs,
tag.HAState : active,
tag.Hostname : h02.bigdata.com,
MissingBlocks : 0,
MissingReplOneBlocks : 0,
ExpiredHeartbeats : 0,
TransactionsSinceLastCheckpoint : 227,
TransactionsSinceLastLogRoll : 1,
LastWrittenTransactionId : 6743,
LastCheckpointTime : 1438637246983,
CapacityTotal : 377945479446528,
CapacityTotalGB : 351989.0,
CapacityUsed : 2162847744,
CapacityUsedGB : 2.0,
CapacityRemaining : 374078076620800,
CapacityRemainingGB : 348387.0,
CapacityUsedNonDFS : 3865239977984,
TotalLoad : 16,
SnapshottableDirectories : 0,
Snapshots : 0,
BlocksTotal : 588,
FilesTotal : 825,
PendingReplicationBlocks : 0,
UnderReplicatedBlocks : 0,
CorruptBlocks : 0,
ScheduledReplicationBlocks : 0,
PendingDeletionBlocks : 0,
ExcessBlocks : 0,
PostponedMisreplicatedBlocks : 0,
PendingDataNodeMessageCount : 0,
MillisSinceLastLoadedEdits : 0,
BlockCapacity : 2097152,
StaleDataNodes : 0,
TotalFiles : 825
} ]
}
2. I check carefully and found the exception I met is different from the one
reported, my exception indicates there is decode error.
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 40, in get_value_from_jmx
data_dict = json.loads(data)
File /usr/lib/python2.6/site-packages/ambari_simplejson/_init_.py, line 307,
in loads
return _default_decoder.decode(s)
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
353, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
Seems this is a new issue. from the JSON object I got, anyone know what's the
error ? How to workaround this? thanks
Unable to Start NameNode in HA Mode On HDP 2.0
--
Key: AMBARI-12374
URL: https://issues.apache.org/jira/browse/AMBARI-12374
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix
[jira] [Created] (AMBARI-12628) When HDFS HA enabled with Ambari 2.1, several service failed to start
Vincent.He created AMBARI-12628:
---
Summary: When HDFS HA enabled with Ambari 2.1, several service
failed to start
Key: AMBARI-12628
URL: https://issues.apache.org/jira/browse/AMBARI-12628
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Vincent.He
Priority: Critical
Install Ambari 2.1 with HDP 2.3, when enabled HA for HDFS, serval service
failed to start like mapredurce history server, dig into more detail, it is
different from issue 12374.
The issues reported is failed to decoded the JSON string,
2015-08-03 02:09:35,420 - Getting jmx metrics from NN failed. URL:
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 40, in get_value_from_jmx
data_dict = json.loads(data)
File /usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py, line
307, in loads
return _default_decoder.decode(s)
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
353, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
2015-08-03 02:09:35,494 - Getting jmx metrics from NN failed. URL:
http://h02.bigdata.lenovo.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 40, in get_value_from_jmx
data_dict = json.loads(data)
File /usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py, line
307, in loads
return _default_decoder.decode(s)
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
353, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py,
line 168, in module
HistoryServer().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 218, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py,
line 91, in start
self.configure(env) # FOR SECURITY
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py,
line 55, in configure
yarn(name=historyserver)
File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py,
line 89, in thunk
return fn(*args, **kwargs)
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py,
line 72, in yarn
recursive_chmod=True
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 390, in action_create_on_execute
self.action_delayed(create)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 387, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 239, in action_delayed
main_resource.resource.security_enabled, main_resource.resource.logoutput)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 126, in __init__
security_enabled, run_user)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py,
line 113, in get_property_for_active_namenode
raise Fail(There is no active namenodes.)
resource_management.core.exceptions.Fail: There is no active namenodes.
The key issue is File
/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line 353, in
raw_decode
raise ValueError(No JSON object could be decoded)
The output I got is
[root@h02 patch]# curl -s
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
{
beans : [ {
name : Hadoop:service=NameNode,name=NameNodeStatus,
modelerType :
[jira] [Created] (AMBARI-12626) Ambari does not allow hard limit for hdfs daemons to be modified
Siddharth Wagle created AMBARI-12626: Summary: Ambari does not allow hard limit for hdfs daemons to be modified Key: AMBARI-12626 URL: https://issues.apache.org/jira/browse/AMBARI-12626 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 2.1.1 Template example: src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 The open files limit is hardcoded. User has to set this manually for running NN and then edit this file and restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Apache Ambari Release 2.0.2 RC2
Hi, I have created an Apache Ambari 2.0.2 Release Candidate (RC2). This is a maintenance release for branch-2.0.maint GIT source tag: *https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc2 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc2* Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc2/ PGP release key used (signed using 392F57AC): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS One can look into the issues fixed in this release at https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747 Total 2.0.2 JIRAs: 13 Total JIRAs Resolved as Fixed: 13 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 Here's how to verify the tarball hashes: git clone --branch release-2.0.2-rc2 https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src cd apache-ambari-2.0.2-src git clean -xdf cd ambari-web npm install ulimit -n 2048 brunch build rm -rf node_modules mv public public-static cd ../.. tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src # Verify my signature, gpg --verify apache-ambari-2.0.2-src.tar.gz.asc apache-ambari-2.0.2-src.tar.gz gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC gpg: Good signature from Alejandro Fernandez (Apache Ambari Release Management) alejan...@apache.org openssl md5 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided openssl sha1 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.sha1 # and compare to the file I provided # I made sure ratcheck passes cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck cd apache-ambari-2.0.2-ratcheck mvn clean apache-rat:check Thanks, Alejandro Fernandez Apache Ambari PMC
Re: Review Request 37059: Ambari 2.0 - 2.1 LDAP: error code 12
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37059/#review93984 --- Ship it! Ship It! - Robert Levas On Aug. 3, 2015, 8:11 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37059/ --- (Updated Aug. 3, 2015, 8:11 p.m.) Review request for Ambari and Robert Levas. Bugs: AMBARI-12627 https://issues.apache.org/jira/browse/AMBARI-12627 Repository: ambari Description --- LDAP result pagination works well for large amounts of users needing to be synchronized from Active Directory, which is the common LDAP implementation. For those using ODSEE 11g, however, it's unsupported. For this reason, it would be beneficial to make this pagination option configurable. For turning off ldap search results pagination add authentication.ldap.pagination.enabled=false into ambari.properties file Diffs - ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java 50fc6a6 ambari-server/src/main/java/org/apache/ambari/server/controller/internal/LdapSyncEventResourceProvider.java 059a228 ambari-server/src/main/java/org/apache/ambari/server/security/authorization/LdapServerProperties.java df314f1 ambari-server/src/main/java/org/apache/ambari/server/security/ldap/AmbariLdapDataPopulator.java 1d8fca1 Diff: https://reviews.apache.org/r/37059/diff/ Testing --- in progress Thanks, Dmytro Sen
[jira] [Commented] (AMBARI-12374) Unable to Start NameNode in HA Mode On HDP 2.0
[
https://issues.apache.org/jira/browse/AMBARI-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652923#comment-14652923
]
Vincent.He commented on AMBARI-12374:
-
Create issue https://issues.apache.org/jira/browse/AMBARI-12628 to track this
as it is a different issue.
Unable to Start NameNode in HA Mode On HDP 2.0
--
Key: AMBARI-12374
URL: https://issues.apache.org/jira/browse/AMBARI-12374
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12374.patch
When starting an HA NameNode cluster on HDP 2.0, the following error is seen:
{code}
2015-07-07 16:02:56,371 - Getting jmx metrics from NN failed. URL:
http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
2015-07-07 16:02:56,396 - Getting jmx metrics from NN failed. URL:
http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 316, in module
NameNode().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 216, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 81, in start
namenode(action=start, rolling_restart=rolling_restart, env=env)
File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py,
line 89, in thunk
return fn(*args, **kwargs)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 141, in namenode
create_hdfs_directories(is_active_namenode_cmd)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 198, in create_hdfs_directories
only_if=check
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 390, in action_create_on_execute
self.action_delayed(create)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 387, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 239, in action_delayed
main_resource.resource.security_enabled, main_resource.resource.logoutput)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 126, in __init__
security_enabled, run_user)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py,
line 113, in get_property_for_active_namenode
raise Fail(There is no active namenodes.)
resource_management.core.exceptions.Fail: There is no active namenodes.
{code}
Although the NameNode does actually start, a failure is recorded in the
request, stopping the rest of the cluster from coming up. This probably
because the JMX properties for Active and Standby NameNode are different in
HDP 2.0 vs HDP 2.1+:
{code:title=active jmx}
{
name : Hadoop:service=NameNode,name=FSNamesystem,
modelerType : FSNamesystem,
tag.Context : dfs,
tag.HAState : active,
{code}
{code:title=standby jmx}
{
name : Hadoop:service=NameNode,name=FSNamesystem,
modelerType : FSNamesystem,
tag.Context : dfs,
tag.HAState : standby,
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: [VOTE] Apache Ambari Release 2.0.2 RC1
Canceling RC1 since Sid Waggle found an issue. Will submit RC2 for a vote in a couple of minutes. On Fri, Jul 31, 2015 at 6:47 PM, Alejandro Fernandez alejan...@apache.org wrote: Hi, I have created an Apache Ambari 2.0.2 Release Candidate (RC1). This is a maintenance release for branch-2.0.maint GIT source tag: *https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1* Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc1/ PGP release key used (signed using 392F57AC): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS One can look into the issues fixed in this release at https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747 Total 2.0.2 JIRAs: 12 Total JIRAs Resolved as Fixed: 12 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 Here's how to verify the tarball hashes: git clone --branch release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src cd apache-ambari-2.0.2-src git clean -xdf cd ambari-web npm install ulimit -n 2048 brunch build rm -rf node_modules mv public public-static cd ../.. tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src # Verify my signature, gpg --verify apache-ambari-2.0.2-src.tar.gz.asc apache-ambari-2.0.2-src.tar.gz gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC gpg: Good signature from Alejandro Fernandez (Apache Ambari Release Management) alejan...@apache.org openssl md5 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided openssl sha1 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.sha1 # and compare to the file I provided # I made sure ratcheck passes cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck cd apache-ambari-2.0.2-ratcheck mvn clean apache-rat:check Thanks, Alejandro Fernandez Apache Ambari PMC
Re: [VOTE] Apache Ambari Release 2.0.2 RC1
Hitesh, Good catch. Let’s address this in trunk and branch-2.1. I’ve opened https://issues.apache.org/jira/browse/AMBARI-12625 to keep track. Yusaku On 8/1/15, 1:12 PM, Hitesh Shah hit...@apache.org wrote: -0 The source seems to include fontawesome fonts which are licensed using SIL Open Font License but the license does not account for it. Ref: http://www.apache.org/legal/resolved.html#category-b — Hitesh On Jul 31, 2015, at 6:47 PM, Alejandro Fernandez alejan...@apache.org wrote: Hi, I have created an Apache Ambari 2.0.2 Release Candidate (RC1). This is a maintenance release for branch-2.0.maint GIT source tag: *https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1* Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc1/ PGP release key used (signed using 392F57AC): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS One can look into the issues fixed in this release at https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747 Total 2.0.2 JIRAs: 12 Total JIRAs Resolved as Fixed: 12 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 Here's how to verify the tarball hashes: git clone --branch release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src cd apache-ambari-2.0.2-src git clean -xdf cd ambari-web npm install ulimit -n 2048 brunch build rm -rf node_modules mv public public-static cd ../.. tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src # Verify my signature, gpg --verify apache-ambari-2.0.2-src.tar.gz.asc apache-ambari-2.0.2-src.tar.gz gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC gpg: Good signature from Alejandro Fernandez (Apache Ambari Release Management) alejan...@apache.org openssl md5 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided openssl sha1 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.sha1 # and compare to the file I provided # I made sure ratcheck passes cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck cd apache-ambari-2.0.2-ratcheck mvn clean apache-rat:check Thanks, Alejandro Fernandez Apache Ambari PMC
Re: Review Request 37060: Ambari does not allow hard limit for hdfs daemons to be modified
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37060/#review93980 --- Ship it! Ship It! - Sumit Mohanty On Aug. 4, 2015, 12:32 a.m., Sid Wagle wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37060/ --- (Updated Aug. 4, 2015, 12:32 a.m.) Review request for Ambari, Alejandro Fernandez, Mahadev Konar, and Sumit Mohanty. Bugs: AMBARI-12626 https://issues.apache.org/jira/browse/AMBARI-12626 Repository: ambari Description --- Template example: src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 The open files limit is hardcoded. User has to set this manually for running NN and then edit this file and restart. Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml d33cfda ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py c53508b ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 d58a6f5 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml 64653b5 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py 35b896f ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hive.conf.j2 8b7f8bd ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml 14ae20b ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml c16c3ac ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py 4443476 ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/mapreduce.conf.j2 b996645 ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/yarn.conf.j2 3bd7a45 Diff: https://reviews.apache.org/r/37060/diff/ Testing --- Manually verified Thanks, Sid Wagle
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Attachment: (was: AMBARI-12615.patch) Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 Attachments: AMBARI-12615.patch There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Attachment: AMBARI-12615.patch Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 Attachments: AMBARI-12615.patch There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12625) Update LICENSE file (and other relevant files if necessary) to address SIL Open Source License for FontAwesome
Yusaku Sako created AMBARI-12625:
Summary: Update LICENSE file (and other relevant files if
necessary) to address SIL Open Source License for FontAwesome
Key: AMBARI-12625
URL: https://issues.apache.org/jira/browse/AMBARI-12625
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.0.2
Reporter: Yusaku Sako
Assignee: Yusaku Sako
Fix For: 2.1.1
[~hitesh] reported on the Ambari 2.0.2 release vote thread:
{quote}
The source seems to include fontawesome fonts which are licensed using SIL Open
Font License but the license does not account for it.
Ref: http://www.apache.org/legal/resolved.html#category-b
{quote}
Let's get this fixed in trunk and branch-2.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Looking into ambari-web. A few questions
Hi ambari developers, I'm trying to understand the ambari code, focusing on the ambari-web. 1. Where can I find the ember v1.0.pre documents? 2. When running *brunch w -s*, ambari already has a cluster installed. Can I go to the install wizard in this testMode with mock data? 3. I'm learning ember at the same time. Any suggestion on how can I understand the code? Now I'm still struggling to understand how authentication in ambari. Thanks, Jiekai
[jira] [Commented] (AMBARI-12626) Ambari does not allow hard limit for hdfs daemons to be modified
[ https://issues.apache.org/jira/browse/AMBARI-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652998#comment-14652998 ] Hudson commented on AMBARI-12626: - SUCCESS: Integrated in Ambari-branch-2.1 #315 (See [https://builds.apache.org/job/Ambari-branch-2.1/315/]) AMBARI-12626. Ambari does not allow hard limit for hdfs daemons to be modified. (swagle) (swagle: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=62701f63d16d77f721bc46c97fc37b817be4e545) * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/mapreduce.conf.j2 * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/yarn.conf.j2 * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hive.conf.j2 * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml Ambari does not allow hard limit for hdfs daemons to be modified Key: AMBARI-12626 URL: https://issues.apache.org/jira/browse/AMBARI-12626 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 2.1.1 Template example: src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 The open files limit is hardcoded. User has to set this manually for running NN and then edit this file and restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12626) Ambari does not allow hard limit for hdfs daemons to be modified
[ https://issues.apache.org/jira/browse/AMBARI-12626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653012#comment-14653012 ] Hudson commented on AMBARI-12626: - SUCCESS: Integrated in Ambari-trunk-Commit #3213 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3213/]) AMBARI-12626. Ambari does not allow hard limit for hdfs daemons to be modified. (swagle) (swagle: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=9e4ea6d92e2546e1d9b3b81cdf3fd5a190fa91b9) * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/mapreduce.conf.j2 * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/templates/yarn.conf.j2 * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/templates/hive.conf.j2 Ambari does not allow hard limit for hdfs daemons to be modified Key: AMBARI-12626 URL: https://issues.apache.org/jira/browse/AMBARI-12626 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.0.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Priority: Critical Fix For: 2.1.1 Template example: src/main/resources/common-services/HDFS/2.1.0.2.0/package/templates/hdfs.conf.j2 The open files limit is hardcoded. User has to set this manually for running NN and then edit this file and restart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12615) Add Data Visualization to Hive View
[
https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653102#comment-14653102
]
Hadoop QA commented on AMBARI-12615:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748591/AMBARI-12615.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
contrib/views/hive.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3520//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3520//console
This message is automatically generated.
Add Data Visualization to Hive View
---
Key: AMBARI-12615
URL: https://issues.apache.org/jira/browse/AMBARI-12615
Project: Ambari
Issue Type: New Feature
Components: ambari-views
Affects Versions: 2.2.0
Reporter: Vivek Ratnavel Subramanian
Assignee: Vivek Ratnavel Subramanian
Fix For: 2.2.0
Attachments: AMBARI-12615.patch
There is no existing visualization tool to visualize the result set data in
Hive View.
Hive view should support a visualization tool with the following features.
1) Ability to visualize result set data in Hive View.
2) Ability to visualize multiple dimensions in the result set with different
types of charts
3) Support all modern browsers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12627) Ambari 2.0 - 2.1 LDAP: error code 12
[
https://issues.apache.org/jira/browse/AMBARI-12627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653031#comment-14653031
]
Hadoop QA commented on AMBARI-12627:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748567/AMBARI-12627.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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.security.ldap.AmbariLdapDataPopulatorTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3519//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3519//console
This message is automatically generated.
Ambari 2.0 - 2.1 LDAP: error code 12
-
Key: AMBARI-12627
URL: https://issues.apache.org/jira/browse/AMBARI-12627
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12627.patch
LDAP result pagination works well for large amounts of users needing to be
synchronized from Active Directory, which is the common LDAP implementation.
For those using ODSEE 11g, however, it's unsupported.
For this reason, it would be beneficial to make this pagination option
configurable.
For turning off ldap search results pagination add
authentication.ldap.pagination.enabled=false into ambari.properties file
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12583) When ambari.repo has insufficient permissions for non-root ambari-server to read failure messages are confusing
[
https://issues.apache.org/jira/browse/AMBARI-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14653097#comment-14653097
]
Hudson commented on AMBARI-12583:
-
SUCCESS: Integrated in Ambari-trunk-Commit #3214 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3214/])
AMBARI-12583. When ambari.repo has insufficient permissions for non-root
ambari-server to read failure messages are confusing (Nahappan Somasundaram via
smohanty) (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=48a0d2accac3a6950737a0a14f393c71436bec3d)
* ambari-server/src/test/python/TestAmbariServer.py
* ambari-common/src/main/python/ambari_commons/os_utils.py
* ambari-server/src/main/python/ambari_server/setupSecurity.py
When ambari.repo has insufficient permissions for non-root ambari-server to
read failure messages are confusing
---
Key: AMBARI-12583
URL: https://issues.apache.org/jira/browse/AMBARI-12583
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Nahappan Somasundaram
Assignee: Nahappan Somasundaram
Labels: newbie, patch
Fix For: 2.2.0
*STR*
# run ambari-server setup and configure ambari to use not default user
{code}Customize user account for ambari-server daemon [y/n] (n)? y
Enter user account for ambari-server daemon (root):ambariuser{code}
# run ambari-server start
# navigate through install wizard to Confirm Hosts step
*ER* hosts confirmation succeed
*AR* Hosts registration failed
{code}==
Creating target directory...
==
Command start time 2015-06-18 13:45:28
Connection to c6401.ambari.apache.org closed.
SSH command execution finished
host=c6401.ambari.apache.org, exitcode=0
Command end time 2015-06-18 13:45:29
==
Copying common functions script...
==
Command start time 2015-06-18 13:45:29
scp /usr/lib/python2.6/site-packages/ambari_commons
host=c6401.ambari.apache.org, exitcode=0
Command end time 2015-06-18 13:45:29
==
Copying OS type check script...
==
Command start time 2015-06-18 13:45:29
scp /usr/lib/python2.6/site-packages/ambari_server/os_check_type.py
host=c6401.ambari.apache.org, exitcode=0
Command end time 2015-06-18 13:45:29
==
Running OS type check...
==
Command start time 2015-06-18 13:45:29
Cluster primary/cluster OS family is redhat6 and local/current OS family is
redhat6
Connection to c6401.ambari.apache.org closed.
SSH command execution finished
host=c6401.ambari.apache.org, exitcode=0
Command end time 2015-06-18 13:45:29
==
Checking 'sudo' package on remote host...
==
Command start time 2015-06-18 13:45:29
sudo-1.8.6p3-7.el6.x86_64
Connection to c6401.ambari.apache.org closed.
SSH command execution finished
host=c6401.ambari.apache.org, exitcode=0
Command end time 2015-06-18 13:45:29
==
Copying repo file to 'tmp' folder...
==
Command start time 2015-06-18 13:45:29
/etc/yum.repos.d/ambari.repo: Permission denied
scp /etc/yum.repos.d/ambari.repo
host=c6401.ambari.apache.org, exitcode=1
Command end time 2015-06-18 13:45:29
==
Moving file to repo dir...
==
Command start time 2015-06-18 13:45:29
mv: cannot stat `/var/lib/ambari-agent/data/tmp/ambari1434635129.repo': No
such file or directory
Connection to c6401.ambari.apache.org closed.
SSH command execution finished
host=c6401.ambari.apache.org, exitcode=1
Command end time 2015-06-18 13:45:29
==
Copying setup script file...
==
Command start time 2015-06-18 13:45:29
scp /usr/lib/python2.6/site-packages/ambari_server/setupAgent.py
host=c6401.ambari.apache.org, exitcode=0
Command end time 2015-06-18 13:45:30
ERROR: Bootstrap of host c6401.ambari.apache.org fails because previous
action finished with non-zero exit code (1)
ERROR MESSAGE: Execute of 'bound method BootstrapDefault.copyNeededFiles of
BootstrapDefault(Thread-1, started daemon 140695872956160)' failed
STDOUT: Try to execute 'bound method BootstrapDefault.copyNeededFiles of
BootstrapDefault(Thread-1, started daemon 140695872956160)'{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12572) Config versions shows not all versions after save
[ https://issues.apache.org/jira/browse/AMBARI-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-12572: - Attachment: AMBARI-12572-2.patch Config versions shows not all versions after save - Key: AMBARI-12572 URL: https://issues.apache.org/jira/browse/AMBARI-12572 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12572-2.patch, AMBARI-12572-2.patch, AMBARI-12572.patch, AMBARI-12572.patch, Screen Shot 2015-07-24 at 2.04.29 PM.png 1. Go to service conf tab. 2. Add or change some properties. 3. Save config version. 4. Only current and previous version are shown. see attached. All versions appear after refreshing the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12572) Config versions shows not all versions after save
[ https://issues.apache.org/jira/browse/AMBARI-12572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652545#comment-14652545 ] Richard Zang commented on AMBARI-12572: --- +1 for patch Config versions shows not all versions after save - Key: AMBARI-12572 URL: https://issues.apache.org/jira/browse/AMBARI-12572 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Xi Wang Assignee: Xi Wang Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12572-2.patch, AMBARI-12572-2.patch, AMBARI-12572.patch, AMBARI-12572.patch, Screen Shot 2015-07-24 at 2.04.29 PM.png 1. Go to service conf tab. 2. Add or change some properties. 3. Save config version. 4. Only current and previous version are shown. see attached. All versions appear after refreshing the page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-10253) Support HTTPS and SSL RPC across Stack components
[ https://issues.apache.org/jira/browse/AMBARI-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652568#comment-14652568 ] Jerry He commented on AMBARI-10253: --- Are there any more details on this JIRA? What is the content of this JIRA and what has been done? I am asking to find out what and how Ambari supports SSL in many of the stack components. Support HTTPS and SSL RPC across Stack components - Key: AMBARI-10253 URL: https://issues.apache.org/jira/browse/AMBARI-10253 Project: Ambari Issue Type: Epic Components: stacks Affects Versions: 2.1.0 Reporter: Jeff Sposetti Fix For: 2.1.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36882: Ambari-server reset action works incorrectly for external DB
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36882/#review93870
---
Ship it!
Ship It!
- Mahadev Konar
On July 28, 2015, 9:12 a.m., Vitalyi Brodetskyi wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36882/
---
(Updated July 28, 2015, 9:12 a.m.)
Review request for Ambari, Andrew Onischuk and Dmytro Sen.
Bugs: AMBARI-12560
https://issues.apache.org/jira/browse/AMBARI-12560
Repository: ambari
Description
---
Ambari tries to drop DB schema during reset ever it is external DB, and fails
during this process.
{code}
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # cat
/etc/ambari-server/conf/ambari.properties |grep server.persistence.type
server.persistence.type=remote
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # ambari-server reset -s
Using python /usr/bin/python2.6
Resetting ambari-server
WARNING You are about to reset and clear the Ambari Server
database. This will remove all cluster host and configuration information
from the database. You will be required to re-configure the Ambari server and
re-run the cluster wizard.
Are you SURE you want to perform the reset [yes/no] (yes)?
Confirm server reset [yes/no](yes)?
Resetting the Server database...
ERROR: Exiting with exit code 1.
REASON: psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket /tmp/.s.PGSQL.5432?
{code}
Diffs
-
ambari-server/src/main/python/ambari_server/serverSetup.py e76d2bc
Diff: https://reviews.apache.org/r/36882/diff/
Testing
---
mvn clean test
Thanks,
Vitalyi Brodetskyi
[jira] [Commented] (AMBARI-12618) Service config pages load too slowly
[ https://issues.apache.org/jira/browse/AMBARI-12618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651654#comment-14651654 ] Andrii Babiichuk commented on AMBARI-12618: --- *branch 2.1.1 Service config pages load too slowly Key: AMBARI-12618 URL: https://issues.apache.org/jira/browse/AMBARI-12618 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12618.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12618) Service config pages load too slowly
[ https://issues.apache.org/jira/browse/AMBARI-12618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651644#comment-14651644 ] Oleg Nechiporenko commented on AMBARI-12618: +1 for patch Service config pages load too slowly Key: AMBARI-12618 URL: https://issues.apache.org/jira/browse/AMBARI-12618 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12618.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12618) Service config pages load too slowly
[ https://issues.apache.org/jira/browse/AMBARI-12618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-12618: -- Attachment: AMBARI-12618.patch Service config pages load too slowly Key: AMBARI-12618 URL: https://issues.apache.org/jira/browse/AMBARI-12618 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12618.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12609) Host Checks: Rerun checks doesn't work properly
[ https://issues.apache.org/jira/browse/AMBARI-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651708#comment-14651708 ] Antonenko Alexander commented on AMBARI-12609: -- committed to branch 2.1.1 Host Checks: Rerun checks doesn't work properly - Key: AMBARI-12609 URL: https://issues.apache.org/jira/browse/AMBARI-12609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.2.0 Attachments: AMBARI-12609.patch Since we have started use custom commands for checking hosts after registering Rerun checks doesn't work properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 37033: Ranger admin install fails with umask 027
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37033/#review93875 --- ambari-web/app/views/common/controls_view.js (line 597) https://reviews.apache.org/r/37033/#comment148289 Why was the name of the file changed? - Alejandro Fernandez On Aug. 3, 2015, 7:01 a.m., Gautam Borad wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37033/ --- (Updated Aug. 3, 2015, 7:01 a.m.) Review request for Ambari, Alejandro Fernandez, Mahadev Konar, Velmurugan Periasamy, and Yusaku Sako. Bugs: AMBARI-12617 https://issues.apache.org/jira/browse/AMBARI-12617 Repository: ambari Description --- Ranger admin fails to install as jdbc driver has insuffcient permissions Diffs - ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py 35d4953 ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py 070dec6 ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py c9aa97f ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py 1abfd45 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py 35b896f ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/params.py 455bd00 ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py 733caf1 ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py 6f039b2 ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py 71996d2 ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py 6f6a02b ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py ec7573a ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py 4443476 ambari-web/app/views/common/controls_view.js 0ca78b0 Diff: https://reviews.apache.org/r/37033/diff/ Testing --- Tested Ranger installation on a Ambari based cluster having Ranger (using Oracle12 DB), HDFS, Zookeeper. Thanks, Gautam Borad
[jira] [Created] (AMBARI-12618) Service config pages load too slowly
Andrii Babiichuk created AMBARI-12618: - Summary: Service config pages load too slowly Key: AMBARI-12618 URL: https://issues.apache.org/jira/browse/AMBARI-12618 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.1.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12617) Ranger admin install fails with umask 027
Gautam Borad created AMBARI-12617: - Summary: Ranger admin install fails with umask 027 Key: AMBARI-12617 URL: https://issues.apache.org/jira/browse/AMBARI-12617 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Environment: Centos6 Oracle12 DB JDK: Oracle JDK8 Reporter: Gautam Borad Assignee: Gautam Borad Ranger admin fails to install as jdbc driver has insuffcient permissions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 37033: Ranger admin install fails with umask 027
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37033/ --- Review request for Ambari, Alejandro Fernandez, Mahadev Konar, Velmurugan Periasamy, and Yusaku Sako. Bugs: AMBARI-12617 https://issues.apache.org/jira/browse/AMBARI-12617 Repository: ambari Description --- Ranger admin fails to install as jdbc driver has insuffcient permissions Diffs - ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin.py 35d4953 ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py 070dec6 ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/package/scripts/params_linux.py c9aa97f ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params_linux.py 1abfd45 ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py 35b896f ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/params.py 455bd00 ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py 733caf1 ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/params.py 6f039b2 ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger.py 71996d2 ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py 6f6a02b ambari-server/src/main/resources/common-services/STORM/0.9.1.2.1/package/scripts/params_linux.py ec7573a ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/params_linux.py 4443476 ambari-web/app/views/common/controls_view.js 0ca78b0 Diff: https://reviews.apache.org/r/37033/diff/ Testing --- Tested Ranger installation on a Ambari based cluster having Ranger (using Oracle12 DB), HDFS, Zookeeper. Thanks, Gautam Borad
[jira] [Commented] (AMBARI-12581) Host check/clean-up logic should clean up new packages and folder names
[
https://issues.apache.org/jira/browse/AMBARI-12581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651955#comment-14651955
]
Hudson commented on AMBARI-12581:
-
SUCCESS: Integrated in Ambari-trunk-Commit #3209 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3209/])
AMBARI-12581. Host check/clean-up logic should clean up new packages and
folder names (dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=fb28fe7ac286e679112a7da19f72cabbf3caa8ee)
* ambari-agent/src/main/python/ambari_agent/HostInfo.py
* ambari-agent/src/main/python/ambari_agent/HostCheckReportFileHandler.py
* ambari-server/src/main/resources/custom_actions/scripts/check_host.py
Host check/clean-up logic should clean up new packages and folder names
---
Key: AMBARI-12581
URL: https://issues.apache.org/jira/browse/AMBARI-12581
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.2
Attachments: AMBARI-12581.2.patch, AMBARI-12581.patch
Few HDP-2.3 installation ran into problem when install performed on VMs that
are not clean. One of the reported problem is:
{code}
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py,
line 38, in module
AfterInstallHook().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 218, in execute
method(env)
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py,
line 35, in hook
link_configs(self.stroutfile)
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py,
line 91, in link_configs
_link_configs(k, json_version, v)
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py,
line 156, in _link_configs
conf_select.select(HDP, package, version)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py,
line 241, in select
shell.checked_call(get_cmd(set-conf-dir, package, version),
logoutput=False, quiet=False, sudo=True)
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 291, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'conf-select
set-conf-dir --package ranger-kms --stack-version 2.3.0.0-2557 --conf-version
0' returned 1. ranger-kms not installed or incorrect package name
{code}
AMBARI-12515 is looking into making conf-select call more robust but
host-clean up script (along with host checkup) need to be modified to handle
the new folders introduced under /etc as well as /usr/hdp/current or
/usr/hdp/version.
Suggestion from [~ncole] regarding cleaning up conf dirs.
{code}
cd /etc
remove accumulo ambari-* atlas hadoop-* hive* hive-* mahout phoenix ranger
spark zookeeper falcon hadoop hbase kafka knox oozie ranger-* (ranger-admin,
ranger-kms, ranger-usersync) slider sqoop storm pig flume hive-hcatalog
{code}
The host check script should be modified to include these folders in the
report so that the cleanup script can clean it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12621) FE: Going to a service heatmap makes a call to old heatmap first
[
https://issues.apache.org/jira/browse/AMBARI-12621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651959#comment-14651959
]
Hadoop QA commented on AMBARI-12621:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748464/AMBARI-12621.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 2 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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3513//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3513//console
This message is automatically generated.
FE: Going to a service heatmap makes a call to old heatmap first
Key: AMBARI-12621
URL: https://issues.apache.org/jira/browse/AMBARI-12621
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.1.2
Attachments: AMBARI-12621.patch
I went to HDFS heatmaps which loaded in 10s. Then I went to HBase heatmaps,
but the first call was still to the Datanode heatmaps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12620) Wrong 'Affected components' list shown
[ https://issues.apache.org/jira/browse/AMBARI-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651954#comment-14651954 ] Hudson commented on AMBARI-12620: - SUCCESS: Integrated in Ambari-trunk-Commit #3209 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3209/]) AMBARI-12620. Wrong 'Affected components' list shown (alexantonenko) (hiveww: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=2462dbeffd7f3795bdf6259a759190e239db2595) * ambari-web/app/mappers/component_config_mapper.js Wrong 'Affected components' list shown -- Key: AMBARI-12620 URL: https://issues.apache.org/jira/browse/AMBARI-12620 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12620.patch On deployed cluster: Change 'NodeManager Java heap size' property. Save changes. Check affected components. 'ATS' and 'ResourceManager' shown as affected, but not 'NodeManager' Also it shows '2 hosts affected'. But if I do 'Restart All Affected'. All components of YARN on all hosts are restarted. Same for 'DataNode maximum Java heap size' only 'NameNode' and 'SNameNode' shown as affected. But restart affects all hosts and all HDFS components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12622) Malformed Alert Data Can Prevent Alerts From Reporting
Jonathan Hurley created AMBARI-12622:
Summary: Malformed Alert Data Can Prevent Alerts From Reporting
Key: AMBARI-12622
URL: https://issues.apache.org/jira/browse/AMBARI-12622
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.1.1
If there is malformed template text in an alert definition, it will prevent
alerts from being reported correctly:
{code}
INFO 2015-07-23 14:10:15,209 scheduler.py:287 - Adding job tentatively -- it
will be properly scheduled when the scheduler starts
INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:318 - [AlertScheduler]
Scheduling datanode_process with UUID 43536b17-596a-4f7d-87e6-c9034b2b99bc
INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:134 - [AlertScheduler]
Starting ambari_agent.apscheduler.scheduler.Scheduler object at 0x10ea910;
currently running: False
INFO 2015-07-23 14:10:17,219 hostname.py:87 - Read public hostname
'cn105-10.l42scl.hortonworks.com' using socket.getfqdn()
INFO 2015-07-23 14:11:15,271 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1 --hiveconf
hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', '/usr/bin/',
'/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 'ambari-qa',
'timeout': 30}
INFO 2015-07-23 14:11:15,274 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:12:15,277 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:12:15,284 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1 --hiveconf
hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', '/usr/bin/',
'/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 'ambari-qa',
'timeout': 30}
ERROR 2015-07-23 14:12:15,293 scheduler.py:520 - Job
28cad184-0e94-4b19-af31-56ab2c1d0a74 (trigger: interval[0:02:00], next run at:
2015-07-23 14:14:15.207467) raised an exception
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/ambari_agent/apscheduler/scheduler.py, line
512, in _run_job
retval = job.func(*job.args, **job.kwargs)
File
/usr/lib/python2.6/site-packages/ambari_agent/AlertSchedulerHandler.py, line
114, in lambda
return lambda: alert_def.collect()
File /usr/lib/python2.6/site-packages/ambari_agent/alerts/base_alert.py,
line 153, in collect
data['text'] = res_base_text.format(*res[1])
ValueError: Unknown format code 'd' for object of type 'float'
INFO 2015-07-23 14:13:15,264 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1 --hiveconf
hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/', '/usr/bin/',
'/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user': 'ambari-qa',
'timeout': 30}
INFO 2015-07-23 14:13:15,272 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
ERROR 2015-07-23 14:14:15,273 scheduler.py:520 - Job
Re: Review Request 37003: Add Data Visualization to Hive View
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37003/ --- (Updated Aug. 3, 2015, 4:53 p.m.) Review request for Ambari and Yusaku Sako. Changes --- Moved the position of visualization tab Bugs: AMBARI-12615 https://issues.apache.org/jira/browse/AMBARI-12615 Repository: ambari Description --- Refer to the description in AMBARI-12615 Diffs (updated) - ambari-web/app/views/main/views/details.js e90cb20 contrib/views/hive/pom.xml 39f6848 contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/browser/HiveBrowserService.java a0d44f5 contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/JobService.java 526f13f contrib/views/hive/src/main/java/org/apache/ambari/view/hive/resources/jobs/ResultsPaginationController.java 18152ad contrib/views/hive/src/main/resources/ui/hive-web/.jshintrc c1fe863 contrib/views/hive/src/main/resources/ui/hive-web/app/components/visualization-tabs-widget.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/query-tabs.js 4f5176c contrib/views/hive/src/main/resources/ui/hive-web/app/controllers/visualization-ui.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/initializers/i18n.js af5e3a7 contrib/views/hive/src/main/resources/ui/hive-web/app/templates/components/visualization-tabs-widget.hbs PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/templates/visualization-ui.hbs PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/app/utils/constants.js e4e445a contrib/views/hive/src/main/resources/ui/hive-web/app/views/visualization-ui.js PRE-CREATION contrib/views/hive/src/main/resources/ui/hive-web/bower.json 37ea901 Diff: https://reviews.apache.org/r/37003/diff/ Testing --- Tested manually with different datasets of different size. Tested switching to visualization tab with multiple SQL tabs having different queries. Tested switching between the two visualization tabs multiple times. Tested with upto 3 rows in the resultset with all possible combinations of scale and chart types. Tested with Google Chrome, Safari, Firefox and Internet Explorer 10. Tested end to end with Ambari Web and Hive View. Existing Ambari Web unit tests pass. 6482 tests complete (22 seconds) 94 tests pending [INFO] [INFO] --- apache-rat-plugin:0.11:check (default) @ ambari-web --- [INFO] 51 implicit excludes (use -debug for more details). [INFO] Exclude: .idea/** [INFO] Exclude: package.json [INFO] Exclude: public/** [INFO] Exclude: public-static/** [INFO] Exclude: app/assets/** [INFO] Exclude: vendor/** [INFO] Exclude: node_modules/** [INFO] Exclude: node/** [INFO] Exclude: npm-debug.log [INFO] 1169 resources included (use -debug for more details) Warning: org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. Compiler warnings: WARNING: 'org.apache.xerces.jaxp.SAXParserImpl: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.' Warning: org.apache.xerces.parsers.SAXParser: Feature 'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized. Warning: org.apache.xerces.parsers.SAXParser: Property 'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not recognized. [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 1169 licence. [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 49.809s [INFO] Finished at: Fri Jul 31 18:39:11 PDT 2015 [INFO] Final Memory: 12M/439M [INFO] Thanks, Vivek Ratnavel Subramanian
[jira] [Commented] (AMBARI-12560) Ambari-server reset action works incorrectly for external DB
[
https://issues.apache.org/jira/browse/AMBARI-12560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652177#comment-14652177
]
Hudson commented on AMBARI-12560:
-
SUCCESS: Integrated in Ambari-branch-2.1 #311 (See
[https://builds.apache.org/job/Ambari-branch-2.1/311/])
AMBARI-12560. Ambari-server reset action works incorrectly for external DB.
(Vitaly Brodetskyi via mpapirkovskyy) (mpapyrkovskyy:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=bf87e1f5f198558cc218d5785d505a8bde818a82)
* ambari-server/src/main/python/ambari_server/serverSetup.py
Ambari-server reset action works incorrectly for external DB
Key: AMBARI-12560
URL: https://issues.apache.org/jira/browse/AMBARI-12560
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.1
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12560.patch
Ambari tries to drop DB schema during reset ever it is external DB, and fails
during this process.
{code}
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # cat
/etc/ambari-server/conf/ambari.properties |grep server.persistence.type
server.persistence.type=remote
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # ambari-server reset -s
Using python /usr/bin/python2.6
Resetting ambari-server
WARNING You are about to reset and clear the Ambari Server
database. This will remove all cluster host and configuration information
from the database. You will be required to re-configure the Ambari server and
re-run the cluster wizard.
Are you SURE you want to perform the reset [yes/no] (yes)?
Confirm server reset [yes/no](yes)?
Resetting the Server database...
ERROR: Exiting with exit code 1.
REASON: psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket /tmp/.s.PGSQL.5432?
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12594) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
[
https://issues.apache.org/jira/browse/AMBARI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652214#comment-14652214
]
Hadoop QA commented on AMBARI-12594:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748475/AMBARI-12594.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3515//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3515//console
This message is automatically generated.
RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after
the upgrade
--
Key: AMBARI-12594
URL: https://issues.apache.org/jira/browse/AMBARI-12594
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12594.2.patch, AMBARI-12594.patch
RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after
the upgrade
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 36895: Cluster creates stuck at 9x% (deadlock sql exception)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36895/ --- (Updated Aug. 3, 2015, 2:39 p.m.) Review request for Ambari, Alejandro Fernandez, Nate Cole, and Sumit Mohanty. Changes --- Bitten by SQL Azure again. They don't support tables without CLUSTERED indexes: ``` Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: Tables without a clustered index are not supported in this version of SQL Server. Please create a clustered index and try again. Error Code: 40054 ``` It seems like the original problem boils down to how SQL Server applies the predicate values in its search. It performs 2 b-tree seeks; the first one on only the cluster_id and the second on the rest. This means that instead of hashing the values and going directly to a row lock, it must perform an X-U lock since it's doing a scan of the whole table. The solution was to move away from the compound, clustered PK and rely solely on a surrogate unique ID. Bugs: AMBARI-12570 https://issues.apache.org/jira/browse/AMBARI-12570 Repository: ambari Description --- Similar to AMBARI-12526, Ambari installation via a blueprint on SQL Azure gets stuck somewhere between 90% and 100% because of a SQL Database deadlock. - We have dual X-locks on hostcomponentstate asking for U-locks when updating the CLUSTERED INDEX. - Both dual X-locks, from different transactions and different processes, are on the same row (technically impossible) - based on the XML execution plan, we can see that the concurrent UPDATE statements are executing on different rows due to their CLUSTERED INDEX predicate. - In Java, Ambari has locks which prevent concurrent U- or X-locks on the same row - Only happens on SQL Server My best suspicion right now is that we have a key hash collision happening on this table. That's why two processes appear to have the same lock even though they are on different rows. Restricting row-level locking on this table will prevent locking on hash keys which could collide. Diffs (updated) - ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentStateDAO.java fb585fd ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntity.java 45e036b ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntityPK.java 86e0dee ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java 0850a79 ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 1b67b24 ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 16f6a0a ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql cd6e27a ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql c7138be ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 0ff1aff ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java 96bbb1d ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java ce1fd34 ambari-server/src/test/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostTest.java f6ab0ec ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog170Test.java 93f7f8c ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java 484c18d Diff: https://reviews.apache.org/r/36895/diff/ Testing --- Deployed a clean cluster on SQL Server and then ran 10+ deployments on SQL Azure without seeing a deadlock. Thanks, Jonathan Hurley
[jira] [Resolved] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
[ https://issues.apache.org/jira/browse/AMBARI-12623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty resolved AMBARI-12623. Resolution: Fixed committed to trunk and 2.1 [PluggableStackDefinition] Integrate pluggable stack definition into build -- Key: AMBARI-12623 URL: https://issues.apache.org/jira/browse/AMBARI-12623 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.1 Attachments: AMBARI-12623.patch Locations of resources in a stack deployed by Ambari should be pluggable to allow for different stack layouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12622) Malformed Alert Data Can Prevent Alerts From Reporting
[
https://issues.apache.org/jira/browse/AMBARI-12622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652237#comment-14652237
]
Hadoop QA commented on AMBARI-12622:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748471/AMBARI-12622.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3516//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3516//console
This message is automatically generated.
Malformed Alert Data Can Prevent Alerts From Reporting
--
Key: AMBARI-12622
URL: https://issues.apache.org/jira/browse/AMBARI-12622
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12622.patch
If there is malformed template text in an alert definition, it will prevent
alerts from being reported correctly:
{code}
INFO 2015-07-23 14:10:15,209 scheduler.py:287 - Adding job tentatively -- it
will be properly scheduled when the scheduler starts
INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:318 - [AlertScheduler]
Scheduling datanode_process with UUID 43536b17-596a-4f7d-87e6-c9034b2b99bc
INFO 2015-07-23 14:10:15,209 AlertSchedulerHandler.py:134 - [AlertScheduler]
Starting ambari_agent.apscheduler.scheduler.Scheduler object at 0x10ea910;
currently running: False
INFO 2015-07-23 14:10:17,219 hostname.py:87 - Read public hostname
'cn105-10.l42scl.hortonworks.com' using socket.getfqdn()
INFO 2015-07-23 14:11:15,271 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1
--hiveconf hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/',
'/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:11:15,274 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:12:15,277 logger.py:66 - Execute['! beeline -u
'jdbc:hive2://cn105-10.l42scl.hortonworks.com:1/;transportMode=binary' -e
'' 21| awk '{print}'|grep -i -e 'Connection refused' -e 'Invalid URL'']
{'path': ['/bin/', '/usr/bin/', '/usr/lib/hive/bin/', '/usr/sbin/'], 'user':
'ambari-qa', 'timeout': 30}
INFO 2015-07-23 14:12:15,284 logger.py:66 - Execute['export
HIVE_CONF_DIR='/usr/hdp/current/hive-metastore/conf/conf.server' ; hive
--hiveconf hive.metastore.uris=thrift://cn105-10.l42scl.hortonworks.com:9083
--hiveconf hive.metastore.client.connect.retry.delay=1
--hiveconf hive.metastore.failure.retries=1
--hiveconf hive.metastore.connect.retries=1 --hiveconf
hive.metastore.client.socket.timeout=14 --hiveconf
hive.execution.engine=mr -e 'show databases;''] {'path': ['/bin/',
'/usr/bin/', '/usr/sbin/', '/usr/hdp/current/hive-metastore/bin'], 'user':
'ambari-qa', 'timeout': 30}
ERROR 2015-07-23 14:12:15,293 scheduler.py:520 - Job
28cad184-0e94-4b19-af31-56ab2c1d0a74 (trigger: interval[0:02:00], next run
at: 2015-07-23 14:14:15.207467) raised an exception
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/ambari_agent/apscheduler/scheduler.py,
line 512, in _run_job
retval = job.func(*job.args, **job.kwargs)
File
/usr/lib/python2.6/site-packages/ambari_agent/AlertSchedulerHandler.py,
line 114, in lambda
return lambda: alert_def.collect()
File
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Attachment: (was: AMBARI-12615.patch) Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12595) Blueprint deployments should refresh configuration on all commands
[ https://issues.apache.org/jira/browse/AMBARI-12595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652096#comment-14652096 ] Hudson commented on AMBARI-12595: - SUCCESS: Integrated in Ambari-trunk-Commit #3210 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3210/]) AMBARI-12595. Blueprint deployments should refresh configuration on all commands. (rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=6c4eba4af0a21c03aedc21d5a9bac7c00ea4ed83) * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java Blueprint deployments should refresh configuration on all commands -- Key: AMBARI-12595 URL: https://issues.apache.org/jira/browse/AMBARI-12595 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.1.0 Reporter: Robert Nettleton Assignee: Robert Nettleton Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12595.patch Original Estimate: 4h Remaining Estimate: 4h During Blueprint deployments of large clusters, there are intermittent failures where configuration appears to not be sychronized with the rest of the cluster. This can cause un-resolved configuration to be sent down to a node, and this will subsequently cause install and start failures. When a Blueprint deployment is in process, the AmbariManagementController implementation should force a refresh on the config if each ExecutionCommand prior to sending it down to the cluster nodes. I'm working on a fix for this, and will be submitting a patch shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-12624) UpgradeHelper must provide command line arguments for Ambari Server port and desired http protocol settings
Dmitry Lysnichenko created AMBARI-12624:
---
Summary: UpgradeHelper must provide command line arguments for
Ambari Server port and desired http protocol settings
Key: AMBARI-12624
URL: https://issues.apache.org/jira/browse/AMBARI-12624
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
UpgradeHelper should work with:
different default ambari port, AND
if ambari is setup for https. Cannot assume 8443 for https
Add command line options for PORT and PROTOCOL.
Change api_port and api_protocol from default
in upgradeHelper.py for Ambari. This needs to be well documented.
{code}
[root@f11d
upgrade_hdp_226]# diff upgradeHelper.py upgradeHelper.py.old
185,186c185,186
API_PROTOCOL
= https
API_PORT
= 8443
---
API_PROTOCOL
= http
API_PORT
= “8080
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12594) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
[
https://issues.apache.org/jira/browse/AMBARI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652076#comment-14652076
]
Hadoop QA commented on AMBARI-12594:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12748457/AMBARI-12594.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3514//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3514//console
This message is automatically generated.
RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after
the upgrade
--
Key: AMBARI-12594
URL: https://issues.apache.org/jira/browse/AMBARI-12594
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12594.2.patch, AMBARI-12594.patch
RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after
the upgrade
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-12615) Add Data Visualization to Hive View
[ https://issues.apache.org/jira/browse/AMBARI-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12615: Attachment: AMBARI-12615.patch Add Data Visualization to Hive View --- Key: AMBARI-12615 URL: https://issues.apache.org/jira/browse/AMBARI-12615 Project: Ambari Issue Type: New Feature Components: ambari-views Affects Versions: 2.2.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.2.0 Attachments: AMBARI-12615.patch There is no existing visualization tool to visualize the result set data in Hive View. Hive view should support a visualization tool with the following features. 1) Ability to visualize result set data in Hive View. 2) Ability to visualize multiple dimensions in the result set with different types of charts 3) Support all modern browsers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
[ https://issues.apache.org/jira/browse/AMBARI-12623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652113#comment-14652113 ] Mahadev konar commented on AMBARI-12623: +1 for the patch. [PluggableStackDefinition] Integrate pluggable stack definition into build -- Key: AMBARI-12623 URL: https://issues.apache.org/jira/browse/AMBARI-12623 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.1 Attachments: AMBARI-12623.patch Locations of resources in a stack deployed by Ambari should be pluggable to allow for different stack layouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12624) UpgradeHelper must provide command line arguments for Ambari Server port and desired http protocol settings
[
https://issues.apache.org/jira/browse/AMBARI-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-12624:
Attachment: AMBARI-12624.patch
UpgradeHelper must provide command line arguments for Ambari Server port and
desired http protocol settings
---
Key: AMBARI-12624
URL: https://issues.apache.org/jira/browse/AMBARI-12624
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12624.patch
UpgradeHelper should work with:
different default ambari port, AND
if ambari is setup for https. Cannot assume 8443 for https
Add command line options for PORT and PROTOCOL.
Change api_port and api_protocol from default
in upgradeHelper.py for Ambari. This needs to be well documented.
{code}
[root@f11d
upgrade_hdp_226]# diff upgradeHelper.py upgradeHelper.py.old
185,186c185,186
API_PROTOCOL
= https
API_PORT
= 8443
---
API_PROTOCOL
= http
API_PORT
= “8080
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 36943: RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/#review93920 --- Ship it! Ship It! - Jonathan Hurley On Aug. 3, 2015, 11:52 a.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/ --- (Updated Aug. 3, 2015, 11:52 a.m.) Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, and Nate Cole. Bugs: AMBARI-12594 https://issues.apache.org/jira/browse/AMBARI-12594 Repository: ambari Description --- RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py d599b8c ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 3dda481 ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py 37dcb20 Diff: https://reviews.apache.org/r/36943/diff/ Testing --- OK -- Total run:808 Total errors:0 Total failures:0 OK Performing tests on live cluster Thanks, Dmitro Lisnichenko
[jira] [Commented] (AMBARI-12560) Ambari-server reset action works incorrectly for external DB
[
https://issues.apache.org/jira/browse/AMBARI-12560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652097#comment-14652097
]
Hudson commented on AMBARI-12560:
-
SUCCESS: Integrated in Ambari-trunk-Commit #3210 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3210/])
AMBARI-12560. Ambari-server reset action works incorrectly for external DB.
(Vitaly Brodetskyi via mpapirkovskyy) (mpapyrkovskyy:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=2f950f9c2a84359eeb61e119a248240a12457e54)
* ambari-server/src/main/python/ambari_server/serverSetup.py
Ambari-server reset action works incorrectly for external DB
Key: AMBARI-12560
URL: https://issues.apache.org/jira/browse/AMBARI-12560
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.1
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
Fix For: 2.1.1
Attachments: AMBARI-12560.patch
Ambari tries to drop DB schema during reset ever it is external DB, and fails
during this process.
{code}
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # cat
/etc/ambari-server/conf/ambari.properties |grep server.persistence.type
server.persistence.type=remote
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # ambari-server reset -s
Using python /usr/bin/python2.6
Resetting ambari-server
WARNING You are about to reset and clear the Ambari Server
database. This will remove all cluster host and configuration information
from the database. You will be required to re-configure the Ambari server and
re-run the cluster wizard.
Are you SURE you want to perform the reset [yes/no] (yes)?
Confirm server reset [yes/no](yes)?
Resetting the Server database...
ERROR: Exiting with exit code 1.
REASON: psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket /tmp/.s.PGSQL.5432?
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 37043: UpgradeHelper must provide command line arguments for Ambari Server port and desired http protocol settings
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37043/#review93918 --- Ship it! Ship It! - Dmytro Sen On Авг. 3, 2015, 5:16 п.п., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37043/ --- (Updated Авг. 3, 2015, 5:16 п.п.) Review request for Ambari and Dmytro Sen. Bugs: AMBARI-12624 https://issues.apache.org/jira/browse/AMBARI-12624 Repository: ambari Description --- UpgradeHelper should work with: different default ambari port, AND if ambari is setup for https. Cannot assume 8443 for https Add command line options for PORT and PROTOCOL. Change api_port and api_protocol from default in upgradeHelper.py for Ambari. This needs to be well documented. [root@f11d upgrade_hdp_226]# diff upgradeHelper.py upgradeHelper.py.old 185,186c185,186 API_PROTOCOL = https API_PORT = 8443 --- API_PROTOCOL = http API_PORT = “8080 Diffs - ambari-server/src/main/python/upgradeHelper.py c38ce5f ambari-server/src/test/python/TestUpgradeHelper.py 5aca13d Diff: https://reviews.apache.org/r/37043/diff/ Testing --- Ran 241 tests in 6.076s OK -- Total run:784 Total errors:0 Total failures:0 OK Process finished with exit code 0 Thanks, Dmitro Lisnichenko
[jira] [Created] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
Sumit Mohanty created AMBARI-12623: -- Summary: [PluggableStackDefinition] Integrate pluggable stack definition into build Key: AMBARI-12623 URL: https://issues.apache.org/jira/browse/AMBARI-12623 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.1 Locations of resources in a stack deployed by Ambari should be pluggable to allow for different stack layouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
[ https://issues.apache.org/jira/browse/AMBARI-12623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-12623: --- Attachment: AMBARI-12623.patch [PluggableStackDefinition] Integrate pluggable stack definition into build -- Key: AMBARI-12623 URL: https://issues.apache.org/jira/browse/AMBARI-12623 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.1 Attachments: AMBARI-12623.patch Locations of resources in a stack deployed by Ambari should be pluggable to allow for different stack layouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Review Request 37043: UpgradeHelper must provide command line arguments for Ambari Server port and desired http protocol settings
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37043/ --- Review request for Ambari and Dmytro Sen. Bugs: AMBARI-12624 https://issues.apache.org/jira/browse/AMBARI-12624 Repository: ambari Description --- UpgradeHelper should work with: different default ambari port, AND if ambari is setup for https. Cannot assume 8443 for https Add command line options for PORT and PROTOCOL. Change api_port and api_protocol from default in upgradeHelper.py for Ambari. This needs to be well documented. [root@f11d upgrade_hdp_226]# diff upgradeHelper.py upgradeHelper.py.old 185,186c185,186 API_PROTOCOL = https API_PORT = 8443 --- API_PROTOCOL = http API_PORT = “8080 Diffs - ambari-server/src/main/python/upgradeHelper.py c38ce5f ambari-server/src/test/python/TestUpgradeHelper.py 5aca13d Diff: https://reviews.apache.org/r/37043/diff/ Testing --- Ran 241 tests in 6.076s OK -- Total run:784 Total errors:0 Total failures:0 OK Process finished with exit code 0 Thanks, Dmitro Lisnichenko
[jira] [Commented] (AMBARI-12618) Service config pages load too slowly
[ https://issues.apache.org/jira/browse/AMBARI-12618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651749#comment-14651749 ] Hudson commented on AMBARI-12618: - SUCCESS: Integrated in Ambari-branch-2.1 #307 (See [https://builds.apache.org/job/Ambari-branch-2.1/307/]) AMBARI-12618 Service config pages load too slowly. (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=9582cc0a7f5f527aa9f9dd2521c7ce8a48fc26ac) * ambari-web/test/controllers/main/service/info/config_test.js * ambari-web/test/utils/config_test.js * ambari-web/app/data/HDP2.3/site_properties.js * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js * ambari-web/app/controllers/global/cluster_controller.js * ambari-web/app/routes/installer.js * ambari-web/app/utils/config.js * ambari-web/app/views/main/admin/serviceAccounts_view.js * ambari-web/app/controllers/main/service/info/configs.js * ambari-web/app/mixins/common/configs/enhanced_configs.js * ambari-web/app/utils/ajax/ajax.js * ambari-web/app/models/configs/stack_config_property.js * ambari-web/app/mappers/configs/themes_mapper.js * ambari-web/app/controllers/main/admin/serviceAccounts_controller.js * ambari-web/app/routes/add_service_routes.js * ambari-web/app/mixins/main/service/configs/config_overridable.js * ambari-web/app/views/common/configs/services_config.js * ambari-web/test/controllers/wizard/step7_test.js * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * ambari-web/app/data/host_component_mapping.js * ambari-web/app/controllers/wizard.js * ambari-web/app/views/common/controls_view.js * ambari-web/test/controllers/wizard_test.js * ambari-web/app/views/common/modal_popups/select_groups_popup.js * ambari-web/app/controllers/wizard/step7_controller.js * ambari-web/app/mixins/common/configs/configs_saver.js * ambari-web/app/mappers/configs/stack_config_properties_mapper.js Service config pages load too slowly Key: AMBARI-12618 URL: https://issues.apache.org/jira/browse/AMBARI-12618 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12618.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-12619) ambari agent return exit code 0 even when start action fails
[ https://issues.apache.org/jira/browse/AMBARI-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk resolved AMBARI-12619. -- Resolution: Fixed Committed to trunk and branch-2.1 ambari agent return exit code 0 even when start action fails Key: AMBARI-12619 URL: https://issues.apache.org/jira/browse/AMBARI-12619 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 When service ambari-agent start fails, the exit code should be non-zero. The script (/etc/init.d/ambari-agent) currently returns 0 no matter what. We use the exit code in our agent to determine whether we need to retry starting up ambari-agent or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 37038: ambari agent return exit code 0 even when start action fails
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37038/#review93892 --- Ship it! Ship It! - Dmitro Lisnichenko On Aug. 3, 2015, noon, Andrew Onischuk wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37038/ --- (Updated Aug. 3, 2015, noon) Review request for Ambari and Dmitro Lisnichenko. Bugs: AMBARI-12619 https://issues.apache.org/jira/browse/AMBARI-12619 Repository: ambari Description --- When service ambari-agent start fails, the exit code should be non-zero. The script (/etc/init.d/ambari-agent) currently returns 0 no matter what. We use the exit code in our agent to determine whether we need to retry starting up ambari-agent or not. Diffs - ambari-agent/etc/init.d/ambari-agent 4e255cd Diff: https://reviews.apache.org/r/37038/diff/ Testing --- mvn clean test Thanks, Andrew Onischuk
[jira] [Created] (AMBARI-12620) Wrong 'Affected components' list shown
Antonenko Alexander created AMBARI-12620: Summary: Wrong 'Affected components' list shown Key: AMBARI-12620 URL: https://issues.apache.org/jira/browse/AMBARI-12620 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.1.1 On deployed cluster: Change 'NodeManager Java heap size' property. Save changes. Check affected components. 'ATS' and 'ResourceManager' shown as affected, but not 'NodeManager' Also it shows '2 hosts affected'. But if I do 'Restart All Affected'. All components of YARN on all hosts are restarted. Same for 'DataNode maximum Java heap size' only 'NameNode' and 'SNameNode' shown as affected. But restart affects all hosts and all HDFS components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36943: [Preview] RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/#review93897 --- Ship it! Ship It! ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py (lines 48 - 50) https://reviews.apache.org/r/36943/#comment148315 Consider ``` if Script.is_hdp_stack_greater_or_equal(2.2): ``` since it's cleaner. - Jonathan Hurley On July 30, 2015, 11:33 a.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/ --- (Updated July 30, 2015, 11:33 a.m.) Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, and Nate Cole. Bugs: AMBARI-12594 https://issues.apache.org/jira/browse/AMBARI-12594 Repository: ambari Description --- RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py d599b8c ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 3dda481 ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py 37dcb20 Diff: https://reviews.apache.org/r/36943/diff/ Testing --- OK -- Total run:808 Total errors:0 Total failures:0 OK Performing tests on live cluster Thanks, Dmitro Lisnichenko
Review Request 37038: ambari agent return exit code 0 even when start action fails
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37038/ --- Review request for Ambari and Dmitro Lisnichenko. Bugs: AMBARI-12619 https://issues.apache.org/jira/browse/AMBARI-12619 Repository: ambari Description --- When service ambari-agent start fails, the exit code should be non-zero. The script (/etc/init.d/ambari-agent) currently returns 0 no matter what. We use the exit code in our agent to determine whether we need to retry starting up ambari-agent or not. Diffs - ambari-agent/etc/init.d/ambari-agent 4e255cd Diff: https://reviews.apache.org/r/37038/diff/ Testing --- mvn clean test Thanks, Andrew Onischuk
[jira] [Commented] (AMBARI-12581) Host check/clean-up logic should clean up new packages and folder names
[
https://issues.apache.org/jira/browse/AMBARI-12581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651815#comment-14651815
]
Dmitry Lysnichenko commented on AMBARI-12581:
-
Committed to trunk for now
Commit to 2.1.2 is pending
Host check/clean-up logic should clean up new packages and folder names
---
Key: AMBARI-12581
URL: https://issues.apache.org/jira/browse/AMBARI-12581
Project: Ambari
Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.2
Attachments: AMBARI-12581.2.patch, AMBARI-12581.patch
Few HDP-2.3 installation ran into problem when install performed on VMs that
are not clean. One of the reported problem is:
{code}
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py,
line 38, in module
AfterInstallHook().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 218, in execute
method(env)
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py,
line 35, in hook
link_configs(self.stroutfile)
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py,
line 91, in link_configs
_link_configs(k, json_version, v)
File
/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py,
line 156, in _link_configs
conf_select.select(HDP, package, version)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/conf_select.py,
line 241, in select
shell.checked_call(get_cmd(set-conf-dir, package, version),
logoutput=False, quiet=False, sudo=True)
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 291, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'conf-select
set-conf-dir --package ranger-kms --stack-version 2.3.0.0-2557 --conf-version
0' returned 1. ranger-kms not installed or incorrect package name
{code}
AMBARI-12515 is looking into making conf-select call more robust but
host-clean up script (along with host checkup) need to be modified to handle
the new folders introduced under /etc as well as /usr/hdp/current or
/usr/hdp/version.
Suggestion from [~ncole] regarding cleaning up conf dirs.
{code}
cd /etc
remove accumulo ambari-* atlas hadoop-* hive* hive-* mahout phoenix ranger
spark zookeeper falcon hadoop hbase kafka knox oozie ranger-* (ranger-admin,
ranger-kms, ranger-usersync) slider sqoop storm pig flume hive-hcatalog
{code}
The host check script should be modified to include these folders in the
report so that the cleanup script can clean it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 36943: [Preview] RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
On July 31, 2015, 12:21 p.m., Nate Cole wrote: ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py, lines 48-50 https://reviews.apache.org/r/36943/diff/1/?file=1025111#file1025111line48 If this is true, then the upgrade pack for 2.2.x - 2.2.y needs to be updated. If not, then this version check should be for 2.3. You are right, I correctly added definitions for 2.3 stack, but missed boilerplate code change here. NFS gateway has been added in HDP 2.3 On July 31, 2015, 12:21 p.m., Nate Cole wrote: ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml, line 140 https://reviews.apache.org/r/36943/diff/1/?file=1025112#file1025112line140 +1 for this comment. Also, python says 2.2 and higher, so would need HDP-2.2 - 2.2 upgrade pack change. I think no, since NFS gateway has been added in HDP 2.3 - Dmitro --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/#review93719 --- On July 30, 2015, 3:33 p.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/ --- (Updated July 30, 2015, 3:33 p.m.) Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, and Nate Cole. Bugs: AMBARI-12594 https://issues.apache.org/jira/browse/AMBARI-12594 Repository: ambari Description --- RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py d599b8c ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 3dda481 ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py 37dcb20 Diff: https://reviews.apache.org/r/36943/diff/ Testing --- OK -- Total run:808 Total errors:0 Total failures:0 OK Performing tests on live cluster Thanks, Dmitro Lisnichenko
Re: Review Request 36943: [Preview] RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
On July 30, 2015, 5:27 p.m., Alejandro Fernandez wrote: ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml, line 140 https://reviews.apache.org/r/36943/diff/1/?file=1025112#file1025112line140 Is this also needed inside HDP 2.2-2.3 RU? I think no, since NFS gateway has been added in HDP 2.3 - Dmitro --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/#review93610 --- On July 30, 2015, 3:33 p.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36943/ --- (Updated July 30, 2015, 3:33 p.m.) Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, and Nate Cole. Bugs: AMBARI-12594 https://issues.apache.org/jira/browse/AMBARI-12594 Repository: ambari Description --- RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade Diffs - ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py d599b8c ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml 3dda481 ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py 37dcb20 Diff: https://reviews.apache.org/r/36943/diff/ Testing --- OK -- Total run:808 Total errors:0 Total failures:0 OK Performing tests on live cluster Thanks, Dmitro Lisnichenko
[jira] [Created] (AMBARI-12619) ambari agent return exit code 0 even when start action fails
Andrew Onischuk created AMBARI-12619: Summary: ambari agent return exit code 0 even when start action fails Key: AMBARI-12619 URL: https://issues.apache.org/jira/browse/AMBARI-12619 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 When service ambari-agent start fails, the exit code should be non-zero. The script (/etc/init.d/ambari-agent) currently returns 0 no matter what. We use the exit code in our agent to determine whether we need to retry starting up ambari-agent or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-12620) Wrong 'Affected components' list shown
[ https://issues.apache.org/jira/browse/AMBARI-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-12620: - Attachment: AMBARI-12620.patch Wrong 'Affected components' list shown -- Key: AMBARI-12620 URL: https://issues.apache.org/jira/browse/AMBARI-12620 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12620.patch On deployed cluster: Change 'NodeManager Java heap size' property. Save changes. Check affected components. 'ATS' and 'ResourceManager' shown as affected, but not 'NodeManager' Also it shows '2 hosts affected'. But if I do 'Restart All Affected'. All components of YARN on all hosts are restarted. Same for 'DataNode maximum Java heap size' only 'NameNode' and 'SNameNode' shown as affected. But restart affects all hosts and all HDFS components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12609) Host Checks: Rerun checks doesn't work properly
[ https://issues.apache.org/jira/browse/AMBARI-12609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651819#comment-14651819 ] Hudson commented on AMBARI-12609: - SUCCESS: Integrated in Ambari-branch-2.1 #308 (See [https://builds.apache.org/job/Ambari-branch-2.1/308/]) AMBARI-12609. Host Checks: Rerun checks doesn't work properly (alexantonenko) (hiveww: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=eddd5f86343fececa8e4640c6e6bfd7c31157fe4) * ambari-web/app/controllers/wizard/step3_controller.js Host Checks: Rerun checks doesn't work properly - Key: AMBARI-12609 URL: https://issues.apache.org/jira/browse/AMBARI-12609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.2.0 Attachments: AMBARI-12609.patch Since we have started use custom commands for checking hosts after registering Rerun checks doesn't work properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12620) Wrong 'Affected components' list shown
[ https://issues.apache.org/jira/browse/AMBARI-12620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651821#comment-14651821 ] Andrii Babiichuk commented on AMBARI-12620: --- +1 for the patch Wrong 'Affected components' list shown -- Key: AMBARI-12620 URL: https://issues.apache.org/jira/browse/AMBARI-12620 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.1.1 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.1.1 Attachments: AMBARI-12620.patch On deployed cluster: Change 'NodeManager Java heap size' property. Save changes. Check affected components. 'ATS' and 'ResourceManager' shown as affected, but not 'NodeManager' Also it shows '2 hosts affected'. But if I do 'Restart All Affected'. All components of YARN on all hosts are restarted. Same for 'DataNode maximum Java heap size' only 'NameNode' and 'SNameNode' shown as affected. But restart affects all hosts and all HDFS components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12374) Unable to Start NameNode in HA Mode On HDP 2.0
[
https://issues.apache.org/jira/browse/AMBARI-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651845#comment-14651845
]
Vincent.He commented on AMBARI-12374:
-
I meet the same issues with Ambari 2.1 and HDP2.3, is there a patch or
workaround on this? it is a blocking issue for me.
Unable to Start NameNode in HA Mode On HDP 2.0
--
Key: AMBARI-12374
URL: https://issues.apache.org/jira/browse/AMBARI-12374
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12374.patch
When starting an HA NameNode cluster on HDP 2.0, the following error is seen:
{code}
2015-07-07 16:02:56,371 - Getting jmx metrics from NN failed. URL:
http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
2015-07-07 16:02:56,396 - Getting jmx metrics from NN failed. URL:
http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 316, in module
NameNode().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 216, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 81, in start
namenode(action=start, rolling_restart=rolling_restart, env=env)
File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py,
line 89, in thunk
return fn(*args, **kwargs)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 141, in namenode
create_hdfs_directories(is_active_namenode_cmd)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 198, in create_hdfs_directories
only_if=check
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 390, in action_create_on_execute
self.action_delayed(create)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 387, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 239, in action_delayed
main_resource.resource.security_enabled, main_resource.resource.logoutput)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 126, in __init__
security_enabled, run_user)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py,
line 113, in get_property_for_active_namenode
raise Fail(There is no active namenodes.)
resource_management.core.exceptions.Fail: There is no active namenodes.
{code}
Although the NameNode does actually start, a failure is recorded in the
request, stopping the rest of the cluster from coming up. This probably
because the JMX properties for Active and Standby NameNode are different in
HDP 2.0 vs HDP 2.1+:
{code:title=active jmx}
{
name : Hadoop:service=NameNode,name=FSNamesystem,
modelerType : FSNamesystem,
tag.Context : dfs,
tag.HAState : active,
{code}
{code:title=standby jmx}
{
name : Hadoop:service=NameNode,name=FSNamesystem,
modelerType : FSNamesystem,
tag.Context : dfs,
tag.HAState : standby,
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12374) Unable to Start NameNode in HA Mode On HDP 2.0
[
https://issues.apache.org/jira/browse/AMBARI-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651847#comment-14651847
]
Vincent.He commented on AMBARI-12374:
-
The error message I see is
2015-08-03 02:09:35,420 - Getting jmx metrics from NN failed. URL:
http://h03.bigdata.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 40, in get_value_from_jmx
data_dict = json.loads(data)
File /usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py, line
307, in loads
return _default_decoder.decode(s)
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
353, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
2015-08-03 02:09:35,494 - Getting jmx metrics from NN failed. URL:
http://h02.bigdata.lenovo.com:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 40, in get_value_from_jmx
data_dict = json.loads(data)
File /usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py, line
307, in loads
return _default_decoder.decode(s)
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File /usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py, line
353, in raw_decode
raise ValueError(No JSON object could be decoded)
ValueError: No JSON object could be decoded
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py,
line 168, in module
HistoryServer().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 218, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py,
line 91, in start
self.configure(env) # FOR SECURITY
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py,
line 55, in configure
yarn(name=historyserver)
File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py,
line 89, in thunk
return fn(*args, **kwargs)
File
/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py,
line 72, in yarn
recursive_chmod=True
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 390, in action_create_on_execute
self.action_delayed(create)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 387, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 239, in action_delayed
main_resource.resource.security_enabled, main_resource.resource.logoutput)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 126, in __init__
security_enabled, run_user)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py,
line 113, in get_property_for_active_namenode
raise Fail(There is no active namenodes.)
resource_management.core.exceptions.Fail: There is no active namenodes.
Unable to Start NameNode in HA Mode On HDP 2.0
--
Key: AMBARI-12374
URL: https://issues.apache.org/jira/browse/AMBARI-12374
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12374.patch
When starting an HA NameNode cluster on HDP 2.0, the following error is seen:
{code}
2015-07-07 16:02:56,371 - Getting jmx metrics from NN failed. URL:
http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line
Re: Review Request 36882: Ambari-server reset action works incorrectly for external DB
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36882/#review93901
---
Ship it!
Ship It!
- Dmytro Sen
On Июль 28, 2015, 9:12 д.п., Vitalyi Brodetskyi wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/36882/
---
(Updated Июль 28, 2015, 9:12 д.п.)
Review request for Ambari, Andrew Onischuk and Dmytro Sen.
Bugs: AMBARI-12560
https://issues.apache.org/jira/browse/AMBARI-12560
Repository: ambari
Description
---
Ambari tries to drop DB schema during reset ever it is external DB, and fails
during this process.
{code}
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # cat
/etc/ambari-server/conf/ambari.properties |grep server.persistence.type
server.persistence.type=remote
ambari-framework-selftest-sle113-8508-split1-re2-5:~ # ambari-server reset -s
Using python /usr/bin/python2.6
Resetting ambari-server
WARNING You are about to reset and clear the Ambari Server
database. This will remove all cluster host and configuration information
from the database. You will be required to re-configure the Ambari server and
re-run the cluster wizard.
Are you SURE you want to perform the reset [yes/no] (yes)?
Confirm server reset [yes/no](yes)?
Resetting the Server database...
ERROR: Exiting with exit code 1.
REASON: psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket /tmp/.s.PGSQL.5432?
{code}
Diffs
-
ambari-server/src/main/python/ambari_server/serverSetup.py e76d2bc
Diff: https://reviews.apache.org/r/36882/diff/
Testing
---
mvn clean test
Thanks,
Vitalyi Brodetskyi
[jira] [Updated] (AMBARI-12594) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
[ https://issues.apache.org/jira/browse/AMBARI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-12594: Attachment: AMBARI-12594.2.patch RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- Key: AMBARI-12594 URL: https://issues.apache.org/jira/browse/AMBARI-12594 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 2.1.1 Attachments: AMBARI-12594.2.patch, AMBARI-12594.patch RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12374) Unable to Start NameNode in HA Mode On HDP 2.0
[
https://issues.apache.org/jira/browse/AMBARI-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651855#comment-14651855
]
Sumit Mohanty commented on AMBARI-12374:
[~chinadragon0515], you can use the patch attached to this JIRA if you are on
2.1. If you are patching a already deployed system then
*
ambari-common/src/main/python/resource_management/libraries/functions/namenode_ha_utils.py
** patch the file
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py
on all hosts (at least NN hosts)
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/journalnode_upgrade.py
and
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_ha_state.py
** patch at
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/
and restart ambari-server
Unable to Start NameNode in HA Mode On HDP 2.0
--
Key: AMBARI-12374
URL: https://issues.apache.org/jira/browse/AMBARI-12374
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12374.patch
When starting an HA NameNode cluster on HDP 2.0, the following error is seen:
{code}
2015-07-07 16:02:56,371 - Getting jmx metrics from NN failed. URL:
http://c6401.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
2015-07-07 16:02:56,396 - Getting jmx metrics from NN failed. URL:
http://c6402.ambari.apache.org:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus
Traceback (most recent call last):
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/jmx.py,
line 41, in get_value_from_jmx
return data_dict[beans][0][property]
IndexError: list index out of range
Traceback (most recent call last):
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 316, in module
NameNode().execute()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py,
line 216, in execute
method(env)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py,
line 81, in start
namenode(action=start, rolling_restart=rolling_restart, env=env)
File /usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py,
line 89, in thunk
return fn(*args, **kwargs)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 141, in namenode
create_hdfs_directories(is_active_namenode_cmd)
File
/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py,
line 198, in create_hdfs_directories
only_if=check
File /usr/lib/python2.6/site-packages/resource_management/core/base.py,
line 157, in __init__
self.env.run()
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 152, in run
self.run_action(resource, action)
File
/usr/lib/python2.6/site-packages/resource_management/core/environment.py,
line 118, in run_action
provider_action()
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 390, in action_create_on_execute
self.action_delayed(create)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 387, in action_delayed
self.get_hdfs_resource_executor().action_delayed(action_name, self)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 239, in action_delayed
main_resource.resource.security_enabled, main_resource.resource.logoutput)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py,
line 126, in __init__
security_enabled, run_user)
File
/usr/lib/python2.6/site-packages/resource_management/libraries/functions/namenode_ha_utils.py,
line 113, in get_property_for_active_namenode
raise Fail(There is no active namenodes.)
resource_management.core.exceptions.Fail: There is no active namenodes.
{code}
Although the NameNode does actually start, a failure is recorded in the
request, stopping the rest of the cluster from coming up. This probably
because the JMX properties for Active and Standby NameNode are different in
HDP 2.0 vs HDP 2.1+:
{code:title=active jmx}
{
name :
[jira] [Commented] (AMBARI-12619) ambari agent return exit code 0 even when start action fails
[ https://issues.apache.org/jira/browse/AMBARI-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651852#comment-14651852 ] Hudson commented on AMBARI-12619: - SUCCESS: Integrated in Ambari-trunk-Commit #3208 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3208/]) AMBARI-12619. ambari agent return exit code 0 even when start action fails (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=316404fe5231b75b590f5a7f5c630d6824451786) * ambari-agent/etc/init.d/ambari-agent ambari agent return exit code 0 even when start action fails Key: AMBARI-12619 URL: https://issues.apache.org/jira/browse/AMBARI-12619 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.1.1 When service ambari-agent start fails, the exit code should be non-zero. The script (/etc/init.d/ambari-agent) currently returns 0 no matter what. We use the exit code in our agent to determine whether we need to retry starting up ambari-agent or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
[ https://issues.apache.org/jira/browse/AMBARI-12623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652347#comment-14652347 ] Hudson commented on AMBARI-12623: - SUCCESS: Integrated in Ambari-trunk-Commit #3211 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3211/]) AMBARI-12623. [PluggableStackDefinition] Integrate pluggable stack definition into build (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d6058d956fcc190edefe534c5441977f2d2b3791) * ambari-server/pom.xml * ambari-agent/pom.xml * ambari-server/src/main/assemblies/server.xml [PluggableStackDefinition] Integrate pluggable stack definition into build -- Key: AMBARI-12623 URL: https://issues.apache.org/jira/browse/AMBARI-12623 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.1 Attachments: AMBARI-12623.patch Locations of resources in a stack deployed by Ambari should be pluggable to allow for different stack layouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-12623) [PluggableStackDefinition] Integrate pluggable stack definition into build
[ https://issues.apache.org/jira/browse/AMBARI-12623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652492#comment-14652492 ] Hudson commented on AMBARI-12623: - FAILURE: Integrated in Ambari-branch-2.1 #313 (See [https://builds.apache.org/job/Ambari-branch-2.1/313/]) AMBARI-12623. [PluggableStackDefinition] Integrate pluggable stack definition into build (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=e3e5a5dae79bf92b979af735ce60f1734b666d82) * ambari-agent/pom.xml * ambari-server/src/main/assemblies/server.xml * ambari-server/pom.xml [PluggableStackDefinition] Integrate pluggable stack definition into build -- Key: AMBARI-12623 URL: https://issues.apache.org/jira/browse/AMBARI-12623 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.1.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 2.1.1 Attachments: AMBARI-12623.patch Locations of resources in a stack deployed by Ambari should be pluggable to allow for different stack layouts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [CANCEL][VOTE] Apache Ambari Release 2.0.2 RC1
-1 for this RC, found an issue with recently backported patch from branch-2.1 The addendum patch was not backported to 2.0-maint branch. I have merged the changed to 2.0-maint, here is the commit hash: commit fc7f513a3f03313d6a3b39bf2ef082ccd6695524 Author: Siddharth Wagle swa...@hortonworks.com Date: Mon Aug 3 11:07:37 2015 -0700 AMBARI-10904. Provide a configurable timeout setting on MetricsTimelineSink.emitMetrics. Sink timeout jetty issue. (swagle) Regards, Sid From: Alejandro Fernandez alejan...@apache.org Sent: Friday, July 31, 2015 6:47 PM To: dev@ambari.apache.org Subject: [VOTE] Apache Ambari Release 2.0.2 RC1 Hi, I have created an Apache Ambari 2.0.2 Release Candidate (RC1). This is a maintenance release for branch-2.0.maint GIT source tag: *https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari/repo?p=ambari.git;a=log;h=refs/tags/release-2.0.2-rc1* Staging site: http://people.apache.org/~alejandro/apache-ambari-2.0.2-rc1/ PGP release key used (signed using 392F57AC): http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x2147F220392F57AC Updated KEYS file: https://dist.apache.org/repos/dist/release/ambari/KEYS One can look into the issues fixed in this release at https://issues.apache.org/jira/browse/AMBARI/fixforversion/12332747 Total 2.0.2 JIRAs: 12 Total JIRAs Resolved as Fixed: 12 Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 Here's how to verify the tarball hashes: git clone --branch release-2.0.2-rc1 https://git-wip-us.apache.org/repos/asf/ambari.git apache-ambari-2.0.2-src cd apache-ambari-2.0.2-src git clean -xdf cd ambari-web npm install ulimit -n 2048 brunch build rm -rf node_modules mv public public-static cd ../.. tar --exclude=.git --exclude=.gitignore --exclude=.gitattributes -zcvf apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src # Verify my signature, gpg --verify apache-ambari-2.0.2-src.tar.gz.asc apache-ambari-2.0.2-src.tar.gz gpg: Signature made Fri Jul 31 18:36:49 2015 PDT using RSA key ID 392F57AC gpg: Good signature from Alejandro Fernandez (Apache Ambari Release Management) alejan...@apache.org openssl md5 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.md5# and compare to the file I provided openssl sha1 apache-ambari-2.0.2-src.tar.gz apache-ambari-2.0.2-src.tar.gz.sha1 # and compare to the file I provided # I made sure ratcheck passes cp -R apache-ambari-2.0.2-src apache-ambari-2.0.2-ratcheck cd apache-ambari-2.0.2-ratcheck mvn clean apache-rat:check Thanks, Alejandro Fernandez Apache Ambari PMC
[jira] [Commented] (AMBARI-12624) UpgradeHelper must provide command line arguments for Ambari Server port and desired http protocol settings
[
https://issues.apache.org/jira/browse/AMBARI-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652346#comment-14652346
]
Hudson commented on AMBARI-12624:
-
SUCCESS: Integrated in Ambari-trunk-Commit #3211 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3211/])
AMBARI-12624. UpgradeHelper must provide command line arguments for Ambari
Server port and desired http protocol settings (dlysnichenko) (dlysnichenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=a2e6535943671a8a16636a2eea054324e4ebc0c5)
* ambari-server/src/test/python/TestUpgradeHelper.py
* ambari-server/src/main/python/upgradeHelper.py
UpgradeHelper must provide command line arguments for Ambari Server port and
desired http protocol settings
---
Key: AMBARI-12624
URL: https://issues.apache.org/jira/browse/AMBARI-12624
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 2.1.1
Attachments: AMBARI-12624.patch
UpgradeHelper should work with:
different default ambari port, AND
if ambari is setup for https. Cannot assume 8443 for https
Add command line options for PORT and PROTOCOL.
Change api_port and api_protocol from default
in upgradeHelper.py for Ambari. This needs to be well documented.
{code}
[root@f11d
upgrade_hdp_226]# diff upgradeHelper.py upgradeHelper.py.old
185,186c185,186
API_PROTOCOL
= https
API_PORT
= 8443
---
API_PROTOCOL
= http
API_PORT
= “8080
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-12594) RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade
[ https://issues.apache.org/jira/browse/AMBARI-12594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652345#comment-14652345 ] Hudson commented on AMBARI-12594: - SUCCESS: Integrated in Ambari-trunk-Commit #3211 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3211/]) AMBARI-12594. RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=5cfe6d60d0e8b338a89a57ad623ee54afcca3312) * ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- Key: AMBARI-12594 URL: https://issues.apache.org/jira/browse/AMBARI-12594 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 2.1.1 Attachments: AMBARI-12594.2.patch, AMBARI-12594.patch RU- 2.3 - 2.3 + - NFS jars are not upgraded and refer to old version after the upgrade -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 36895: Cluster creates stuck at 9x% (deadlock sql exception)
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36895/#review93960 --- Changes look good. Will wait for the upgrade related changes. - Sumit Mohanty On Aug. 3, 2015, 6:39 p.m., Jonathan Hurley wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36895/ --- (Updated Aug. 3, 2015, 6:39 p.m.) Review request for Ambari, Alejandro Fernandez, Nate Cole, and Sumit Mohanty. Bugs: AMBARI-12570 https://issues.apache.org/jira/browse/AMBARI-12570 Repository: ambari Description --- Similar to AMBARI-12526, Ambari installation via a blueprint on SQL Azure gets stuck somewhere between 90% and 100% because of a SQL Database deadlock. - We have dual X-locks on hostcomponentstate asking for U-locks when updating the CLUSTERED INDEX. - Both dual X-locks, from different transactions and different processes, are on the same row (technically impossible) - based on the XML execution plan, we can see that the concurrent UPDATE statements are executing on different rows due to their CLUSTERED INDEX predicate. - In Java, Ambari has locks which prevent concurrent U- or X-locks on the same row - Only happens on SQL Server My best suspicion right now is that we have a key hash collision happening on this table. That's why two processes appear to have the same lock even though they are on different rows. Restricting row-level locking on this table will prevent locking on hash keys which could collide. Diffs - ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostComponentStateDAO.java fb585fd ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntity.java 45e036b ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostComponentStateEntityPK.java 86e0dee ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java 0850a79 ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 1b67b24 ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 16f6a0a ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql cd6e27a ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql c7138be ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 0ff1aff ambari-server/src/test/java/org/apache/ambari/server/state/ServiceComponentTest.java 96bbb1d ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClustersTest.java ce1fd34 ambari-server/src/test/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostTest.java f6ab0ec ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog170Test.java 93f7f8c ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java 484c18d Diff: https://reviews.apache.org/r/36895/diff/ Testing --- Deployed a clean cluster on SQL Server and then ran 10+ deployments on SQL Azure without seeing a deadlock. Thanks, Jonathan Hurley
