[jira] [Commented] (AMBARI-7996) Remove zk quorum from slider config
[ https://issues.apache.org/jira/browse/AMBARI-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188047#comment-14188047 ] Hudson commented on AMBARI-7996: SUCCESS: Integrated in Ambari-branch-1.7.0 #242 (See [https://builds.apache.org/job/Ambari-branch-1.7.0/242/]) AMBARI-7996. Remove zk quorum from slider config (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f2e55395ea3994cc5fc339ddb41998ec4c2db697) * ambari-server/src/main/resources/stacks/HDP/2.2/services/SLIDER/configuration/slider-client.xml Remove zk quorum from slider config --- Key: AMBARI-7996 URL: https://issues.apache.org/jira/browse/AMBARI-7996 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 1.7.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 1.7.0 Attachments: AMBARI-7996.patch slider no longer relies on zk quorum config provided through slider-client.xml. It instead uses hadoop.registry.zk.quorum from yarn-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-7996) Remove zk quorum from slider config
[ https://issues.apache.org/jira/browse/AMBARI-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188048#comment-14188048 ] Hudson commented on AMBARI-7996: SUCCESS: Integrated in Ambari-trunk-Commit #742 (See [https://builds.apache.org/job/Ambari-trunk-Commit/742/]) AMBARI-7996. Remove zk quorum from slider config (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=9c024238fc9d1fde3359185b1d5cb49c773ca933) * ambari-server/src/main/resources/stacks/HDP/2.2/services/SLIDER/configuration/slider-client.xml Remove zk quorum from slider config --- Key: AMBARI-7996 URL: https://issues.apache.org/jira/browse/AMBARI-7996 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 1.7.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 1.7.0 Attachments: AMBARI-7996.patch slider no longer relies on zk quorum config provided through slider-client.xml. It instead uses hadoop.registry.zk.quorum from yarn-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-7996) Remove zk quorum from slider config
[ https://issues.apache.org/jira/browse/AMBARI-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188055#comment-14188055 ] Hudson commented on AMBARI-7996: SUCCESS: Integrated in Ambari-branch-1.7.0-docker #14 (See [https://builds.apache.org/job/Ambari-branch-1.7.0-docker/14/]) AMBARI-7996. Remove zk quorum from slider config (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f2e55395ea3994cc5fc339ddb41998ec4c2db697) * ambari-server/src/main/resources/stacks/HDP/2.2/services/SLIDER/configuration/slider-client.xml Remove zk quorum from slider config --- Key: AMBARI-7996 URL: https://issues.apache.org/jira/browse/AMBARI-7996 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 1.7.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 1.7.0 Attachments: AMBARI-7996.patch slider no longer relies on zk quorum config provided through slider-client.xml. It instead uses hadoop.registry.zk.quorum from yarn-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-7996) Remove zk quorum from slider config
[ https://issues.apache.org/jira/browse/AMBARI-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188068#comment-14188068 ] Hudson commented on AMBARI-7996: SUCCESS: Integrated in Ambari-trunk-Commit-docker #43 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/43/]) AMBARI-7996. Remove zk quorum from slider config (smohanty: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=9c024238fc9d1fde3359185b1d5cb49c773ca933) * ambari-server/src/main/resources/stacks/HDP/2.2/services/SLIDER/configuration/slider-client.xml Remove zk quorum from slider config --- Key: AMBARI-7996 URL: https://issues.apache.org/jira/browse/AMBARI-7996 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 1.7.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 1.7.0 Attachments: AMBARI-7996.patch slider no longer relies on zk quorum config provided through slider-client.xml. It instead uses hadoop.registry.zk.quorum from yarn-site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8015) Dashboard: add a widget for YARN links (similar to the HDFS Links)
Mingjiang Shi created AMBARI-8015: - Summary: Dashboard: add a widget for YARN links (similar to the HDFS Links) Key: AMBARI-8015 URL: https://issues.apache.org/jira/browse/AMBARI-8015 Project: Ambari Issue Type: Improvement Components: ambari-web Reporter: Mingjiang Shi Fix For: 2.0.0 There is an HDFS Links widget. It would be good to have a similar widget for YARN. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8015) Dashboard: add a widget for YARN links (similar to the HDFS Links)
[ https://issues.apache.org/jira/browse/AMBARI-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mingjiang Shi updated AMBARI-8015: -- Attachment: yarn_links.png Dashboard: add a widget for YARN links (similar to the HDFS Links) -- Key: AMBARI-8015 URL: https://issues.apache.org/jira/browse/AMBARI-8015 Project: Ambari Issue Type: Improvement Components: ambari-web Reporter: Mingjiang Shi Fix For: 2.0.0 Attachments: yarn_links.png There is an HDFS Links widget. It would be good to have a similar widget for YARN. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8015) Dashboard: add a widget for YARN links (similar to the HDFS Links)
[ https://issues.apache.org/jira/browse/AMBARI-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188103#comment-14188103 ] Mingjiang Shi commented on AMBARI-8015: --- I am working on this right now. Dashboard: add a widget for YARN links (similar to the HDFS Links) -- Key: AMBARI-8015 URL: https://issues.apache.org/jira/browse/AMBARI-8015 Project: Ambari Issue Type: Improvement Components: ambari-web Reporter: Mingjiang Shi Fix For: 2.0.0 Attachments: yarn_links.png There is an HDFS Links widget. It would be good to have a similar widget for YARN. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8014) Tune log4j parameters to reduce logs in ambari-server when slider view is enabled
[
https://issues.apache.org/jira/browse/AMBARI-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188122#comment-14188122
]
Hadoop QA commented on AMBARI-8014:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12677832/AMBARI-8014.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/399//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/399//console
This message is automatically generated.
Tune log4j parameters to reduce logs in ambari-server when slider view is
enabled
-
Key: AMBARI-8014
URL: https://issues.apache.org/jira/browse/AMBARI-8014
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 1.7.0
Attachments: AMBARI-8014.patch
Need to set some namespaces and classes to WARN
{noformat}
log4j.logger.org.apache.hadoop.yarn.client=WARN
log4j.logger.org.apache.slider.common.tools.SliderUtils=WARN
log4j.logger.org.apache.ambari.server.security.authorization=WARN
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27286: WebHCat Server Migration option via Ambari
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27286/ --- (Updated Oct. 29, 2014, 8:27 a.m.) Review request for Ambari and Srimanth Gunturi. Bugs: AMBARI-8002 https://issues.apache.org/jira/browse/AMBARI-8002 Repository: ambari Description --- WebHCat Server Migration option via Ambari Diffs - ambari-web/app/controllers/main/service/reassign/step4_controller.js bbd61d3 ambari-web/app/controllers/wizard/step5_controller.js 186d8f8 ambari-web/app/models/stack_service_component.js 46c006e ambari-web/test/controllers/main/service/reassign/step4_controller_test.js baee572 Diff: https://reviews.apache.org/r/27286/diff/ Testing --- Unit testing. End to end testing with a clean Ambari instance. Thanks, Szilard Nemethy
Re: Review Request 27254: Alerts UI: create routes for new alerts pages
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27254/#review58974 --- Ship it! Ship It! - Aleksandr Kovalenko On Жов. 28, 2014, 12:47 до полудня, Xi Wang wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27254/ --- (Updated Жов. 28, 2014, 12:47 до полудня) Review request for Ambari, Aleksandr Kovalenko and Srimanth Gunturi. Bugs: AMBARI-7992 https://issues.apache.org/jira/browse/AMBARI-7992 Repository: ambari Description --- In this jira, need to make sure all new alerts pages are there with blank content (or some test content), also the URLs are correct. Here are the new alerts pages we need to add : * Alerts summary page: a new tab 'Alerts' on the top-nav bar will trigger this page. So we will have 'Dashboard', 'Services', 'Hosts', 'Alerts', 'Admin', 'Views' ... on the top nav bar after adding 'Alerts'. The URL should be: http://hostname:8080/#/main/alerts * Host details Alerts tab. The URL should be: http://hostname:8080/#/main/hosts/hostname/alerts Diffs - ambari-web/app/config.js f7171bf ambari-web/app/messages.js 99a429c ambari-web/app/routes/main.js bfdfc8c ambari-web/app/templates/main/alerts.hbs PRE-CREATION ambari-web/app/templates/main/host/alerts.hbs PRE-CREATION ambari-web/app/views.js 1970248 ambari-web/app/views/main/alerts.js PRE-CREATION ambari-web/app/views/main/host/alerts.js PRE-CREATION ambari-web/app/views/main/host/menu.js 0cd19b3 ambari-web/app/views/main/menu.js 6c68f53 Diff: https://reviews.apache.org/r/27254/diff/ Testing --- Thanks, Xi Wang
[jira] [Updated] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-8003: - Attachment: AMBARI-8003_2.patch UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27319: Alerts: Convert Script-Style Flume Alerts From Nagios
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27319/#review58976 --- Ship it! Ship It! - Nate Cole On Oct. 28, 2014, 11:36 p.m., Jonathan Hurley wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27319/ --- (Updated Oct. 28, 2014, 11:36 p.m.) Review request for Ambari, Nate Cole and Tom Beerbower. Bugs: AMBARI-8010 https://issues.apache.org/jira/browse/AMBARI-8010 Repository: ambari Description --- Flume is unique in that its alerts are currently run by the agents and injected into the heartbeat back to the server. There are specialized methods in flume_handler.py and flume.py that parse the flume JSON file and produce output about the running processes. These methods are also used by the main service methods (like start and configure) defined in flume.py. I have moved the methods with sharable logic into a ambari-common and altered the flume.py file to use the new shared resources. The new alerts also use the shared resources. Diffs - ambari-common/src/main/python/resource_management/libraries/functions/flume_agent_helper.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/alerts.json PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/files/alert_flume_agent_status.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume.py 2db4039 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume_handler.py 42ac560 ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py 85602ef Diff: https://reviews.apache.org/r/27319/diff/ Testing --- - Verified that when flume has no agents, the alert shows as OK - Verified that multiple agents being in various states correctly trigger alerts - Started, stopped flume service/agents and ran a configure to ensure that existing functionality still works. Updated existing flume tests Total run:679 Total errors:0 Total failures:0 OK Thanks, Jonathan Hurley
[jira] [Updated] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-8003: - Attachment: AMBARI-8003_2_branch-1.7.0.patch UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188290#comment-14188290 ] Andrii Babiichuk commented on AMBARI-8003: -- additional patch added UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk reopened AMBARI-8003: -- UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188291#comment-14188291 ] Aleksandr Kovalenko commented on AMBARI-8003: - +1 for additional patch UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188292#comment-14188292 ] Andrii Tkach commented on AMBARI-8003: -- +1 for additional patch. UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[
https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188298#comment-14188298
]
Hadoop QA commented on AMBARI-8003:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12677873/AMBARI-8003_2_branch-1.7.0.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/400//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/400//console
This message is automatically generated.
UI changes for Ambari Datanode directories need to allow for heterogeneous
storage tags
---
Key: AMBARI-8003
URL: https://issues.apache.org/jira/browse/AMBARI-8003
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 1.7.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
Fix For: 1.7.0
Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch,
AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch
allow validation for datanode directories in 2.2. stack for [ssd] /dirname
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27319: Alerts: Convert Script-Style Flume Alerts From Nagios
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27319/#review58977 --- Ship it! Ship It! - Tom Beerbower On Oct. 29, 2014, 3:36 a.m., Jonathan Hurley wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27319/ --- (Updated Oct. 29, 2014, 3:36 a.m.) Review request for Ambari, Nate Cole and Tom Beerbower. Bugs: AMBARI-8010 https://issues.apache.org/jira/browse/AMBARI-8010 Repository: ambari Description --- Flume is unique in that its alerts are currently run by the agents and injected into the heartbeat back to the server. There are specialized methods in flume_handler.py and flume.py that parse the flume JSON file and produce output about the running processes. These methods are also used by the main service methods (like start and configure) defined in flume.py. I have moved the methods with sharable logic into a ambari-common and altered the flume.py file to use the new shared resources. The new alerts also use the shared resources. Diffs - ambari-common/src/main/python/resource_management/libraries/functions/flume_agent_helper.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/alerts.json PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/files/alert_flume_agent_status.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume.py 2db4039 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume_handler.py 42ac560 ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py 85602ef Diff: https://reviews.apache.org/r/27319/diff/ Testing --- - Verified that when flume has no agents, the alert shows as OK - Verified that multiple agents being in various states correctly trigger alerts - Started, stopped flume service/agents and ran a configure to ensure that existing functionality still works. Updated existing flume tests Total run:679 Total errors:0 Total failures:0 OK Thanks, Jonathan Hurley
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188322#comment-14188322 ] Hudson commented on AMBARI-8003: SUCCESS: Integrated in Ambari-trunk-Commit-docker #44 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/44/]) AMBARI-8003 UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags 2. (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=bcf1c9914b03ceec1d639b6c1078becaa9f6aff0) * ambari-web/app/utils/validator.js * ambari-web/app/models/service_config.js * ambari-web/test/utils/validator_test.js UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188324#comment-14188324 ] Hudson commented on AMBARI-8003: SUCCESS: Integrated in Ambari-branch-1.7.0-docker #15 (See [https://builds.apache.org/job/Ambari-branch-1.7.0-docker/15/]) AMBARI-8003 UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags 2. (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=09c42383a01dd81dd2a98d42ad799336cbed886f) * ambari-web/app/utils/validator.js * ambari-web/app/models/service_config.js * ambari-web/test/utils/validator_test.js UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8003) UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188327#comment-14188327 ] Hudson commented on AMBARI-8003: SUCCESS: Integrated in Ambari-trunk-Commit #743 (See [https://builds.apache.org/job/Ambari-trunk-Commit/743/]) AMBARI-8003 UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags 2. (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=bcf1c9914b03ceec1d639b6c1078becaa9f6aff0) * ambari-web/app/models/service_config.js * ambari-web/test/utils/validator_test.js * ambari-web/app/utils/validator.js UI changes for Ambari Datanode directories need to allow for heterogeneous storage tags --- Key: AMBARI-8003 URL: https://issues.apache.org/jira/browse/AMBARI-8003 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 1.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8003.patch, AMBARI-8003_2.patch, AMBARI-8003_2_branch-1.7.0.patch, AMBARI-8003_branch-1.7.0.patch allow validation for datanode directories in 2.2. stack for [ssd] /dirname -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-7448) Create Kerberos Service
[ https://issues.apache.org/jira/browse/AMBARI-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-7448: - Attachment: AMBARI-7448.patch.5 Moved configuration parsing to params.py, some clean up, and added service definition unit tests. New patch [^AMBARI-7448.patch.5] Create Kerberos Service --- Key: AMBARI-7448 URL: https://issues.apache.org/jira/browse/AMBARI-7448 Project: Ambari Issue Type: New Feature Components: stacks Affects Versions: 2.0.0 Reporter: Robert Levas Assignee: Robert Levas Labels: component, kdc, kerberos, stack Fix For: 2.0.0 Attachments: AMBARI-7448.patch, AMBARI-7448.patch.2, AMBARI-7448.patch.3, AMBARI-7448.patch.4, AMBARI-7448.patch.5 Create a service to manage the (optional) Kerberos server (managed KDC) and client components. See [Ambari Cluster Kerberization Technical Document|https://issues.apache.org/jira/secure/attachment/12671235/AmbariClusterKerberization.pdf] for more information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27328: Cannot run hive tez query using HDP 2.1 stack
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27328/#review58984 --- Ship it! Ship It! - Andrew Onischuk On Oct. 29, 2014, 1:52 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27328/ --- (Updated Oct. 29, 2014, 1:52 p.m.) Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, and Mahadev Konar. Bugs: AMBARI-8016 https://issues.apache.org/jira/browse/AMBARI-8016 Repository: ambari Description --- [root@c6401 views]# ambari-server --hash 5e1796a9d8d32eeaa24f13d29b81c437fef5acd8 1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive) 2) set Hive engine to tez 3) attempt to run hive query, get the error below; [root@c6401 yum.repos.d]# su - hive [hive@c6401 ~]$ cd /tmp [hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip --2014-10-29 01:28:52-- http://seanlahman.com/files/database/lahman591-csv.zip Resolving seanlahman.com... 208.113.136.74 Connecting to seanlahman.com|208.113.136.74|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 8337421 (8.0M) [application/zip] Saving to: “lahman591-csv.zip” 100%[==] 8,337,421 3.45M/s in 2.3s 2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421] [hive@c6401 tmp]$ unzip lahman591-csv.zip Archive: lahman591-csv.zip inflating: Managers.csv inflating: ManagersHalf.csv inflating: Pitching.csv inflating: Salaries.csv inflating: Schools.csv inflating: SchoolsPlayers.csv inflating: Teams.csv inflating: TeamsFranchises.csv inflating: TeamsHalf.csv inflating: AllstarFull.csv inflating: AwardsManagers.csv inflating: AwardsPlayers.csv inflating: AwardsShareManagers.csv inflating: AwardsSharePlayers.csv inflating: Batting.csv inflating: Fielding.csv inflating: FieldingOF.csv inflating: readme59.txt inflating: Master.csv inflating: FieldingPost.csv inflating: HallOfFame.csv inflating: Appearances.csv inflating: PitchingPost.csv inflating: BattingPost.csv inflating: SeriesPost.csv [hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp [hive@c6401 tmp]$ hive Logging initialized using configuration in file:/etc/hive/conf.dist/hive-log4j.properties Exception in thread main java.lang.RuntimeException: java.io.FileNotFoundException: File does not exist: hdfs://c6401.ambari.apache.org:8020/apps/tez at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358) at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681) at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.main(RunJar.java:212) Caused by: java.io.FileNotFoundException: File does not exist: hdfs://c6401.ambari.apache.org:8020/apps/tez at org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128 Diffs - ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/hive_server.py 4e55cfb ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/install_jars.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/params.py 2bfbdc1 ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py 0abc438 Diff: https://reviews.apache.org/r/27328/diff/ Testing --- manual deployment + Ran 242 tests in 3.754s OK -- Total run:679 Total errors:0 Total failures:0 OK Thanks, Dmytro Sen
Review Request 27329: Upgrades : Not enough heap size for NameNode At EC2 cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/ --- Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko. Bugs: AMBARI-8017 https://issues.apache.org/jira/browse/AMBARI-8017 Repository: ambari Description --- STR: 1)Install old version 2)Enable security 3)Upgrade to 1.7.0 Actual result: NameNode become stopped sometimes. Could not start sometimes NameNode due heap size issue. Expected result: Have not heap size issue. Diffs - ambari-common/src/main/python/resource_management/libraries/functions/__init__.py e72512c ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py 063beaa ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py cd06a67 ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py e117938 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/after-INSTALL/scripts/params.py a30899c ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-ANY/scripts/params.py 2fa05df ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-INSTALL/scripts/params.py e396d89 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-START/scripts/params.py 0aecb63 ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HDFS/package/scripts/params.py 376a466 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py 1442175 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py 1d41e58 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py f4d00d6 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py d9fa00a Diff: https://reviews.apache.org/r/27329/diff/ Testing --- manual deployment Thanks, Dmytro Sen
Re: Review Request 27329: Upgrades : Not enough heap size for NameNode At EC2 cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/ --- (Updated Окт. 29, 2014, 2:06 п.п.) Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko. Bugs: AMBARI-8017 https://issues.apache.org/jira/browse/AMBARI-8017 Repository: ambari Description --- STR: 1)Install old version 2)Enable security 3)Upgrade to 1.7.0 Actual result: NameNode become stopped sometimes. Could not start sometimes NameNode due heap size issue. Expected result: Have not heap size issue. Diffs (updated) - ambari-common/src/main/python/resource_management/libraries/functions/__init__.py e72512c ambari-common/src/main/python/resource_management/libraries/functions/format_jvm_option.py PRE-CREATION ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py 063beaa ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py cd06a67 ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py e117938 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/after-INSTALL/scripts/params.py a30899c ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-ANY/scripts/params.py 2fa05df ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-INSTALL/scripts/params.py e396d89 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-START/scripts/params.py 0aecb63 ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HDFS/package/scripts/params.py 376a466 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py 1442175 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py 1d41e58 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py f4d00d6 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py d9fa00a Diff: https://reviews.apache.org/r/27329/diff/ Testing --- manual deployment Thanks, Dmytro Sen
[jira] [Commented] (AMBARI-8014) Tune log4j parameters to reduce logs in ambari-server when slider view is enabled
[
https://issues.apache.org/jira/browse/AMBARI-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188389#comment-14188389
]
Srimanth Gunturi commented on AMBARI-8014:
--
+1 for patch
Tune log4j parameters to reduce logs in ambari-server when slider view is
enabled
-
Key: AMBARI-8014
URL: https://issues.apache.org/jira/browse/AMBARI-8014
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 1.7.0
Attachments: AMBARI-8014.patch
Need to set some namespaces and classes to WARN
{noformat}
log4j.logger.org.apache.hadoop.yarn.client=WARN
log4j.logger.org.apache.slider.common.tools.SliderUtils=WARN
log4j.logger.org.apache.ambari.server.security.authorization=WARN
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-7448) Create Kerberos Service
[
https://issues.apache.org/jira/browse/AMBARI-7448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188399#comment-14188399
]
Hadoop QA commented on AMBARI-7448:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12677884/AMBARI-7448.patch.5
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 4 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/401//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/401//console
This message is automatically generated.
Create Kerberos Service
---
Key: AMBARI-7448
URL: https://issues.apache.org/jira/browse/AMBARI-7448
Project: Ambari
Issue Type: New Feature
Components: stacks
Affects Versions: 2.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Labels: component, kdc, kerberos, stack
Fix For: 2.0.0
Attachments: AMBARI-7448.patch, AMBARI-7448.patch.2,
AMBARI-7448.patch.3, AMBARI-7448.patch.4, AMBARI-7448.patch.5
Create a service to manage the (optional) Kerberos server (managed KDC) and
client components.
See [Ambari Cluster Kerberization Technical
Document|https://issues.apache.org/jira/secure/attachment/12671235/AmbariClusterKerberization.pdf]
for more information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27329: Upgrades : Not enough heap size for NameNode At EC2 cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/#review58987 --- ambari-common/src/main/python/resource_management/libraries/functions/format_jvm_option.py https://reviews.apache.org/r/27329/#comment100262 What is the point for using filter() here? - Dmitro Lisnichenko On Oct. 29, 2014, 2:06 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/ --- (Updated Oct. 29, 2014, 2:06 p.m.) Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko. Bugs: AMBARI-8017 https://issues.apache.org/jira/browse/AMBARI-8017 Repository: ambari Description --- STR: 1)Install old version 2)Enable security 3)Upgrade to 1.7.0 Actual result: NameNode become stopped sometimes. Could not start sometimes NameNode due heap size issue. Expected result: Have not heap size issue. Diffs - ambari-common/src/main/python/resource_management/libraries/functions/__init__.py e72512c ambari-common/src/main/python/resource_management/libraries/functions/format_jvm_option.py PRE-CREATION ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py 063beaa ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py cd06a67 ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py e117938 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/after-INSTALL/scripts/params.py a30899c ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-ANY/scripts/params.py 2fa05df ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-INSTALL/scripts/params.py e396d89 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-START/scripts/params.py 0aecb63 ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HDFS/package/scripts/params.py 376a466 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py 1442175 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py 1d41e58 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py f4d00d6 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py d9fa00a Diff: https://reviews.apache.org/r/27329/diff/ Testing --- manual deployment Thanks, Dmytro Sen
[jira] [Created] (AMBARI-8018) Show all properties for source subresource in alert_definitions API response
Jonathan Hurley created AMBARI-8018:
---
Summary: Show all properties for source subresource in
alert_definitions API response
Key: AMBARI-8018
URL: https://issues.apache.org/jira/browse/AMBARI-8018
Project: Ambari
Issue Type: Task
Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.0.0
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
{code}
but response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1 is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https : {{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property : {{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
And for mapping data on UI we need the full source data. Currently we need to
make one request for all alert_definitions with all data except source and one
request for each alert_definition just to get all source data.
So after this change only one request will be enough to get all
alert_definitions data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8018) Show all properties for source subresource in alert_definitions API response
[
https://issues.apache.org/jira/browse/AMBARI-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188423#comment-14188423
]
Jonathan Hurley commented on AMBARI-8018:
-
After my change:
http://localhost:8080/api/v1/clusters/c1/alert_definitions?fields=*
{code}
href : http://localhost:8080/api/v1/clusters/c1/alert_definitions/218;,
AlertDefinition : {
cluster_name : c1,
component_name : HISTORYSERVER,
enabled : true,
id : 218,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {2:.4f} seconds
},
warning : {
text : HTTP {0} response in {2:.4f} seconds
},
critical : {
text : Connection failed to {1}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https :
{{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property :
{{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
Show all properties for source subresource in alert_definitions API response
Key: AMBARI-8018
URL: https://issues.apache.org/jira/browse/AMBARI-8018
Project: Ambari
Issue Type: Task
Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.0.0
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
{code}
but response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1 is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https : {{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property : {{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
And for mapping data on UI we need the full source data. Currently we need to
make one request for all alert_definitions with all data except source and
one request for each alert_definition just to get all source data.
So after this change only one request will be enough to get all
alert_definitions data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8004) Alerts: Convert Script-Style Oozie Alerts From Nagios
[ https://issues.apache.org/jira/browse/AMBARI-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188425#comment-14188425 ] Hudson commented on AMBARI-8004: SUCCESS: Integrated in Ambari-trunk-Commit #744 (See [https://builds.apache.org/job/Ambari-trunk-Commit/744/]) AMBARI-8004 - Alerts: Convert Script-Style Oozie Alerts From Nagios (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f645c21cfca27872829a1cf4349b0a25202ee40c) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/files/alert_nodemanager_health.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/ZOOKEEPER/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.1/services/STORM/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/GANGLIA/alerts.json * ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HBASE/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.2/services/KAFKA/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.2/services/KNOX/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/package/files/alert_check_oozie_server.py * ambari-agent/src/test/python/ambari_agent/TestAlerts.py Alerts: Convert Script-Style Oozie Alerts From Nagios - Key: AMBARI-8004 URL: https://issues.apache.org/jira/browse/AMBARI-8004 Project: Ambari Issue Type: Task Components: alerts, ambari-agent, ambari-server Affects Versions: 2.0.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.0.0 Attachments: AMBARI-8004.patch Convert the Oozie server status and web UI checks from Nagios to the new alerting framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8010) Alerts: Convert Script-Style Flume Alerts From Nagios
[ https://issues.apache.org/jira/browse/AMBARI-8010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188426#comment-14188426 ] Hudson commented on AMBARI-8010: SUCCESS: Integrated in Ambari-trunk-Commit #744 (See [https://builds.apache.org/job/Ambari-trunk-Commit/744/]) AMBARI-8010 - Alerts: Convert Script-Style Flume Alerts From Nagios (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f784ed9187bd747a2d5291384819c7f690466c6d) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/files/alert_flume_agent_status.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/alerts.json * ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume.py * ambari-common/src/main/python/resource_management/libraries/functions/flume_agent_helper.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume_handler.py Alerts: Convert Script-Style Flume Alerts From Nagios - Key: AMBARI-8010 URL: https://issues.apache.org/jira/browse/AMBARI-8010 Project: Ambari Issue Type: Task Components: alerts, ambari-agent, ambari-server Affects Versions: 2.0.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.0.0 Attachments: AMBARI-8010.patch Convert the flume status python code in flume.py and flume_handler.py into a new SCRIPT alert for Ambari. This will involve refactoring the existing code so that both the agents and the alerts can leverage the same functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8018) Show all properties for source subresource in alert_definitions API response
[
https://issues.apache.org/jira/browse/AMBARI-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-8018:
Attachment: AMBARI-8018.patch
Show all properties for source subresource in alert_definitions API response
Key: AMBARI-8018
URL: https://issues.apache.org/jira/browse/AMBARI-8018
Project: Ambari
Issue Type: Task
Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.0.0
Attachments: AMBARI-8018.patch
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
{code}
but response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1 is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https : {{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property : {{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
And for mapping data on UI we need the full source data. Currently we need to
make one request for all alert_definitions with all data except source and
one request for each alert_definition just to get all source data.
So after this change only one request will be enough to get all
alert_definitions data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Review Request 27331: Show all properties for source subresource in alert_definitions API response
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27331/
---
Review request for Ambari, Aleksandr Kovalenko and Nate Cole.
Bugs: AMBARI-8018
https://issues.apache.org/jira/browse/AMBARI-8018
Repository: ambari
Description
---
The source subproperties should be available when the source itself is
requested to be return on an alert defintion resource:
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
}
but should be
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https :
{{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property :
{{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
Diffs
-
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
5d0a180
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProviderTest.java
a28fe5f
Diff: https://reviews.apache.org/r/27331/diff/
Testing
---
New tests added to cover:
- Ensuring that the source subproperties are present when the source is present
- Ensuring that the source subproperties are not present when the source is not
present
Thanks,
Jonathan Hurley
[jira] [Commented] (AMBARI-8004) Alerts: Convert Script-Style Oozie Alerts From Nagios
[ https://issues.apache.org/jira/browse/AMBARI-8004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188436#comment-14188436 ] Hudson commented on AMBARI-8004: SUCCESS: Integrated in Ambari-trunk-Commit-docker #45 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/45/]) AMBARI-8004 - Alerts: Convert Script-Style Oozie Alerts From Nagios (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f645c21cfca27872829a1cf4349b0a25202ee40c) * ambari-server/src/main/resources/stacks/HDP/2.2/services/KAFKA/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.2/services/KNOX/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.1/services/STORM/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/ZOOKEEPER/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/package/files/alert_check_oozie_server.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/files/alert_nodemanager_health.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/GANGLIA/alerts.json * ambari-agent/src/test/python/ambari_agent/TestAlerts.py * ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/alerts.json * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HBASE/alerts.json Alerts: Convert Script-Style Oozie Alerts From Nagios - Key: AMBARI-8004 URL: https://issues.apache.org/jira/browse/AMBARI-8004 Project: Ambari Issue Type: Task Components: alerts, ambari-agent, ambari-server Affects Versions: 2.0.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.0.0 Attachments: AMBARI-8004.patch Convert the Oozie server status and web UI checks from Nagios to the new alerting framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8010) Alerts: Convert Script-Style Flume Alerts From Nagios
[ https://issues.apache.org/jira/browse/AMBARI-8010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188437#comment-14188437 ] Hudson commented on AMBARI-8010: SUCCESS: Integrated in Ambari-trunk-Commit-docker #45 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/45/]) AMBARI-8010 - Alerts: Convert Script-Style Flume Alerts From Nagios (jonathanhurley) (jhurley: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=f784ed9187bd747a2d5291384819c7f690466c6d) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume_handler.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/files/alert_flume_agent_status.py * ambari-server/src/test/python/stacks/2.0.6/FLUME/test_flume.py * ambari-common/src/main/python/resource_management/libraries/functions/flume_agent_helper.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/package/scripts/flume.py * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/FLUME/alerts.json Alerts: Convert Script-Style Flume Alerts From Nagios - Key: AMBARI-8010 URL: https://issues.apache.org/jira/browse/AMBARI-8010 Project: Ambari Issue Type: Task Components: alerts, ambari-agent, ambari-server Affects Versions: 2.0.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 2.0.0 Attachments: AMBARI-8010.patch Convert the flume status python code in flume.py and flume_handler.py into a new SCRIPT alert for Ambari. This will involve refactoring the existing code so that both the agents and the alerts can leverage the same functions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27331: Show all properties for source subresource in alert_definitions API response
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27331/#review58990
---
Ship it!
Ship It!
- Nate Cole
On Oct. 29, 2014, 11:17 a.m., Jonathan Hurley wrote:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/27331/
---
(Updated Oct. 29, 2014, 11:17 a.m.)
Review request for Ambari, Aleksandr Kovalenko and Nate Cole.
Bugs: AMBARI-8018
https://issues.apache.org/jira/browse/AMBARI-8018
Repository: ambari
Description
---
The source subproperties should be available when the source itself is
requested to be return on an alert defintion resource:
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
}
but should be
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https :
{{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property :
{{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
Diffs
-
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
5d0a180
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProviderTest.java
a28fe5f
Diff: https://reviews.apache.org/r/27331/diff/
Testing
---
New tests added to cover:
- Ensuring that the source subproperties are present when the source is
present
- Ensuring that the source subproperties are not present when the source is
not present
Thanks,
Jonathan Hurley
[jira] [Commented] (AMBARI-8018) Show all properties for source subresource in alert_definitions API response
[
https://issues.apache.org/jira/browse/AMBARI-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188488#comment-14188488
]
Hadoop QA commented on AMBARI-8018:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12677894/AMBARI-8018.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/402//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/402//console
This message is automatically generated.
Show all properties for source subresource in alert_definitions API response
Key: AMBARI-8018
URL: https://issues.apache.org/jira/browse/AMBARI-8018
Project: Ambari
Issue Type: Task
Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.0.0
Attachments: AMBARI-8018.patch
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
{code}
but response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1 is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https : {{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property : {{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
And for mapping data on UI we need the full source data. Currently we need to
make one request for all alert_definitions with all data except source and
one request for each alert_definition just to get all source data.
So after this change only one request will be enough to get all
alert_definitions data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-8019) Create ability to disable protocols for https connections in Ambari.
[ https://issues.apache.org/jira/browse/AMBARI-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-8019: --- Attachment: AMBARI-8019_branch-1.7.0.patch AMBARI-8019.patch Create ability to disable protocols for https connections in Ambari. Key: AMBARI-8019 URL: https://issues.apache.org/jira/browse/AMBARI-8019 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.7.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 1.7.0 Attachments: AMBARI-8019.patch, AMBARI-8019_branch-1.7.0.patch Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8019) Create ability to disable protocols for https connections in Ambari.
[
https://issues.apache.org/jira/browse/AMBARI-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188496#comment-14188496
]
Hadoop QA commented on AMBARI-8019:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12677916/AMBARI-8019_branch-1.7.0.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/403//console
This message is automatically generated.
Create ability to disable protocols for https connections in Ambari.
Key: AMBARI-8019
URL: https://issues.apache.org/jira/browse/AMBARI-8019
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Fix For: 1.7.0
Attachments: AMBARI-8019.patch, AMBARI-8019_branch-1.7.0.patch
Create ability to disable protocols for https connections in Ambari. Port our
patch from EAR-660 to 1.7.0 and trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Review Request 27332: Create ability to disable protocols for https connections in Ambari.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27332/ --- Review request for Ambari, Andrew Onischuk and Vitalyi Brodetskyi. Bugs: AMBARI-8019 https://issues.apache.org/jira/browse/AMBARI-8019 Repository: ambari Description --- Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. Diffs - ambari-server/conf/unix/ambari.properties ebd3aa5 ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java ed59e8a ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java 0d5ee95 Diff: https://reviews.apache.org/r/27332/diff/ Testing --- manual Thanks, Dmitro Lisnichenko
[jira] [Created] (AMBARI-8020) /recommendations API mising tez.am.java.opts
Andrew Onischuk created AMBARI-8020:
---
Summary: /recommendations API mising tez.am.java.opts
Key: AMBARI-8020
URL: https://issues.apache.org/jira/browse/AMBARI-8020
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
Steps to reproduce
1)post request
/http://host:port/api/v1/stacks/HDP/versions/2.2/recommendations for geting
configurations by providing blueprint of host-layout
{hosts: [c6501.ambari.apache.org, c6502.ambari.apache.org,
c6503.ambari.apache.org], services: [YARN, TEZ, HIVE, OOZIE,
STORM, FALCON, MAPREDUCE2], recommend: configurations}
**ER** property tez.am.java_opts present
**AR** property tez.am.java_opts absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27332: Create ability to disable protocols for https connections in Ambari.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27332/#review58996 --- Ship it! Ship It! - Andrew Onischuk On Oct. 29, 2014, 4:04 p.m., Dmitro Lisnichenko wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27332/ --- (Updated Oct. 29, 2014, 4:04 p.m.) Review request for Ambari, Andrew Onischuk and Vitalyi Brodetskyi. Bugs: AMBARI-8019 https://issues.apache.org/jira/browse/AMBARI-8019 Repository: ambari Description --- Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. Diffs - ambari-server/conf/unix/ambari.properties ebd3aa5 ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java ed59e8a ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java 0d5ee95 Diff: https://reviews.apache.org/r/27332/diff/ Testing --- manual Thanks, Dmitro Lisnichenko
[jira] [Commented] (AMBARI-8014) Tune log4j parameters to reduce logs in ambari-server when slider view is enabled
[
https://issues.apache.org/jira/browse/AMBARI-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188506#comment-14188506
]
Sumit Mohanty commented on AMBARI-8014:
---
This is a log4j properties change and hence no unit tests needed. Its in trunk
but not yet in branch-1.7.0
Tune log4j parameters to reduce logs in ambari-server when slider view is
enabled
-
Key: AMBARI-8014
URL: https://issues.apache.org/jira/browse/AMBARI-8014
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 1.7.0
Attachments: AMBARI-8014.patch
Need to set some namespaces and classes to WARN
{noformat}
log4j.logger.org.apache.hadoop.yarn.client=WARN
log4j.logger.org.apache.slider.common.tools.SliderUtils=WARN
log4j.logger.org.apache.ambari.server.security.authorization=WARN
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8008) Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188515#comment-14188515 ] Hudson commented on AMBARI-8008: SUCCESS: Integrated in Ambari-branch-1.7.0 #244 (See [https://builds.apache.org/job/Ambari-branch-1.7.0/244/]) AMBARI-8008. Ambari Datanode directories need to allow for heterogeneous storage tags (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=6f27129483296f7fcaeaf704713b16279d3bc239) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py Ambari Datanode directories need to allow for heterogeneous storage tags Key: AMBARI-8008 URL: https://issues.apache.org/jira/browse/AMBARI-8008 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 1.7.0 After HDP 2.2 is deployed, users will need to be able to specify Storage types for each storage volume in dfs.datanode.data.dir. Without this, admins will not be able to configure and use the Heterogeneous storage capability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8021) Hostname information included in Blueprint export for HDP 2.2 cluster
Robert Nettleton created AMBARI-8021: Summary: Hostname information included in Blueprint export for HDP 2.2 cluster Key: AMBARI-8021 URL: https://issues.apache.org/jira/browse/AMBARI-8021 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 1.7.0 Reporter: Robert Nettleton Assignee: Robert Nettleton Fix For: 1.7.0 After launching an HDP 2.2 cluster using the Ambari UI, a Blueprint exported from the cluster will include hostname information for the following properties: 1. Hostname info appears after security is enabled (Knox also deployed in cluster): core-site : hadoop.proxyuser.knox.hosts webhcat-site: webhcat.proxyuser.knox.hosts oozie-site: hadoop.proxyuser.knox.hosts 2. kafka-broker: kafka.ganglia.metrics.host 3. yarn-site: hadoop.registry.zk.quorum slider-client: slider.zookeeper.quorum kafka-broker: zookeeper.connect The Knox-related properties only appear in the exported Blueprint when Knox and Security are enabled, but the other properties appear when the various services are deployed in either case (Slider, Kafka, Yarn). The Blueprint configuration processor needs to be updated to account for these new properties in the HDP 2.2 stack. I'm working on a patch for this, and will be submitting it shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-8020) /recommendations API mising tez.am.java.opts
[
https://issues.apache.org/jira/browse/AMBARI-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk resolved AMBARI-8020.
-
Resolution: Fixed
Committed to trunk and branch-1.7.0
/recommendations API mising tez.am.java.opts
---
Key: AMBARI-8020
URL: https://issues.apache.org/jira/browse/AMBARI-8020
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
Steps to reproduce
1)post request
/http://host:port/api/v1/stacks/HDP/versions/2.2/recommendations for geting
configurations by providing blueprint of host-layout
{hosts: [c6501.ambari.apache.org, c6502.ambari.apache.org,
c6503.ambari.apache.org], services: [YARN, TEZ, HIVE, OOZIE,
STORM, FALCON, MAPREDUCE2], recommend: configurations}
**ER** property tez.am.java_opts present
**AR** property tez.am.java_opts absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8008) Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188531#comment-14188531 ] Hudson commented on AMBARI-8008: SUCCESS: Integrated in Ambari-trunk-Commit-docker #46 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/46/]) AMBARI-8008. Ambari Datanode directories need to allow for heterogeneous storage tags (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=4fcce7dd0a4d52398bfa6b40d574e6e4280f257e) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py Ambari Datanode directories need to allow for heterogeneous storage tags Key: AMBARI-8008 URL: https://issues.apache.org/jira/browse/AMBARI-8008 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 1.7.0 After HDP 2.2 is deployed, users will need to be able to specify Storage types for each storage volume in dfs.datanode.data.dir. Without this, admins will not be able to configure and use the Heterogeneous storage capability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8008) Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188538#comment-14188538 ] Hudson commented on AMBARI-8008: SUCCESS: Integrated in Ambari-branch-1.7.0-docker #16 (See [https://builds.apache.org/job/Ambari-branch-1.7.0-docker/16/]) AMBARI-8008. Ambari Datanode directories need to allow for heterogeneous storage tags (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=6f27129483296f7fcaeaf704713b16279d3bc239) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py Ambari Datanode directories need to allow for heterogeneous storage tags Key: AMBARI-8008 URL: https://issues.apache.org/jira/browse/AMBARI-8008 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 1.7.0 After HDP 2.2 is deployed, users will need to be able to specify Storage types for each storage volume in dfs.datanode.data.dir. Without this, admins will not be able to configure and use the Heterogeneous storage capability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8008) Ambari Datanode directories need to allow for heterogeneous storage tags
[ https://issues.apache.org/jira/browse/AMBARI-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188545#comment-14188545 ] Hudson commented on AMBARI-8008: SUCCESS: Integrated in Ambari-trunk-Commit #745 (See [https://builds.apache.org/job/Ambari-trunk-Commit/745/]) AMBARI-8008. Ambari Datanode directories need to allow for heterogeneous storage tags (aonishuk) (aonishuk: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=4fcce7dd0a4d52398bfa6b40d574e6e4280f257e) * ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py Ambari Datanode directories need to allow for heterogeneous storage tags Key: AMBARI-8008 URL: https://issues.apache.org/jira/browse/AMBARI-8008 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 1.7.0 After HDP 2.2 is deployed, users will need to be able to specify Storage types for each storage volume in dfs.datanode.data.dir. Without this, admins will not be able to configure and use the Heterogeneous storage capability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27332: Create ability to disable protocols for https connections in Ambari.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27332/ --- (Updated Oct. 29, 2014, 4:47 p.m.) Review request for Ambari, Andrew Onischuk and Vitalyi Brodetskyi. Bugs: AMBARI-8019 https://issues.apache.org/jira/browse/AMBARI-8019 Repository: ambari Description --- Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. Diffs - ambari-server/conf/unix/ambari.properties ebd3aa5 ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java ed59e8a ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java 0d5ee95 Diff: https://reviews.apache.org/r/27332/diff/ Testing (updated) --- manual [INFO] [INFO] Reactor Summary: [INFO] [INFO] Ambari Views .. SUCCESS [3.063s] [INFO] Ambari Server . SUCCESS [18:09.024s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 18:12.709s [INFO] Finished at: Wed Oct 29 19:32:53 FET 2014 [INFO] Final Memory: 24M/258M [INFO] Thanks, Dmitro Lisnichenko
[jira] [Created] (AMBARI-8022) Provide better values for selected HBase configs
Ted Yu created AMBARI-8022: -- Summary: Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Bug Reporter: Ted Yu Carter made the following notes: 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-8022: --- Issue Type: Improvement (was: Bug) Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Carter made the following notes: 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-8022: --- Attachment: ambari-8022-v1.txt Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Attachments: ambari-8022-v1.txt Carter made the following notes: 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-7997) Few HDFS and YARN service metrics don't show up in the UI
[ https://issues.apache.org/jira/browse/AMBARI-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Beerbower resolved AMBARI-7997. --- Resolution: Fixed Pushed to branch-windows-dev. Few HDFS and YARN service metrics don't show up in the UI - Key: AMBARI-7997 URL: https://issues.apache.org/jira/browse/AMBARI-7997 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: branch-windows-dev Environment: Windows Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: branch-windows-dev Attachments: AMBARI-7997.patch Few of the HDFS and YARN service metrics don't show up in the latest branch-windows-dev - HDFS: Total Space Utilization This metric does not show up because in AMBARI-6578 the API call was changed to report the metrics at more precision instead of in GB. So sqlserver_properties.json needs to be updated. See : AMBARI-6578 Usability: HDFS Total Space Utilization chart data needs more precision (Dmytro Shkvyra via dsen) - YARN: Queue Metrics Queue metrics configs in sqlserver_properties.json need to be updated after merging trunk changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Review Request 27329: Upgrades : Not enough heap size for NameNode At EC2 cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/ --- (Updated Окт. 29, 2014, 5 п.п.) Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko. Bugs: AMBARI-8017 https://issues.apache.org/jira/browse/AMBARI-8017 Repository: ambari Description --- STR: 1)Install old version 2)Enable security 3)Upgrade to 1.7.0 Actual result: NameNode become stopped sometimes. Could not start sometimes NameNode due heap size issue. Expected result: Have not heap size issue. Diffs (updated) - ambari-common/src/main/python/resource_management/libraries/functions/__init__.py e72512c ambari-common/src/main/python/resource_management/libraries/functions/format_jvm_option.py PRE-CREATION ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py 063beaa ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py cd06a67 ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py e117938 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/after-INSTALL/scripts/params.py a30899c ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-ANY/scripts/params.py 2fa05df ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-INSTALL/scripts/params.py e396d89 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-START/scripts/params.py 0aecb63 ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HDFS/package/scripts/params.py 376a466 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py 1442175 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py 1d41e58 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py f4d00d6 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py d9fa00a Diff: https://reviews.apache.org/r/27329/diff/ Testing --- manual deployment Thanks, Dmytro Sen
Re: Review Request 27328: Cannot run hive tez query using HDP 2.1 stack
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27328/#review59002 --- Ship it! Ship It! - Alejandro Fernandez On Oct. 29, 2014, 1:52 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27328/ --- (Updated Oct. 29, 2014, 1:52 p.m.) Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, and Mahadev Konar. Bugs: AMBARI-8016 https://issues.apache.org/jira/browse/AMBARI-8016 Repository: ambari Description --- [root@c6401 views]# ambari-server --hash 5e1796a9d8d32eeaa24f13d29b81c437fef5acd8 1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive) 2) set Hive engine to tez 3) attempt to run hive query, get the error below; [root@c6401 yum.repos.d]# su - hive [hive@c6401 ~]$ cd /tmp [hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip --2014-10-29 01:28:52-- http://seanlahman.com/files/database/lahman591-csv.zip Resolving seanlahman.com... 208.113.136.74 Connecting to seanlahman.com|208.113.136.74|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 8337421 (8.0M) [application/zip] Saving to: “lahman591-csv.zip” 100%[==] 8,337,421 3.45M/s in 2.3s 2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421] [hive@c6401 tmp]$ unzip lahman591-csv.zip Archive: lahman591-csv.zip inflating: Managers.csv inflating: ManagersHalf.csv inflating: Pitching.csv inflating: Salaries.csv inflating: Schools.csv inflating: SchoolsPlayers.csv inflating: Teams.csv inflating: TeamsFranchises.csv inflating: TeamsHalf.csv inflating: AllstarFull.csv inflating: AwardsManagers.csv inflating: AwardsPlayers.csv inflating: AwardsShareManagers.csv inflating: AwardsSharePlayers.csv inflating: Batting.csv inflating: Fielding.csv inflating: FieldingOF.csv inflating: readme59.txt inflating: Master.csv inflating: FieldingPost.csv inflating: HallOfFame.csv inflating: Appearances.csv inflating: PitchingPost.csv inflating: BattingPost.csv inflating: SeriesPost.csv [hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp [hive@c6401 tmp]$ hive Logging initialized using configuration in file:/etc/hive/conf.dist/hive-log4j.properties Exception in thread main java.lang.RuntimeException: java.io.FileNotFoundException: File does not exist: hdfs://c6401.ambari.apache.org:8020/apps/tez at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358) at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681) at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.main(RunJar.java:212) Caused by: java.io.FileNotFoundException: File does not exist: hdfs://c6401.ambari.apache.org:8020/apps/tez at org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128 Diffs - ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/hive_server.py 4e55cfb ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/install_jars.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/params.py 2bfbdc1 ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py 0abc438 Diff: https://reviews.apache.org/r/27328/diff/ Testing --- manual deployment + Ran 242 tests in 3.754s OK -- Total run:679 Total errors:0 Total failures:0 OK Thanks, Dmytro Sen
[jira] [Commented] (AMBARI-8020) /recommendations API mising tez.am.java.opts
[
https://issues.apache.org/jira/browse/AMBARI-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188582#comment-14188582
]
Hudson commented on AMBARI-8020:
SUCCESS: Integrated in Ambari-branch-1.7.0 #245 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0/245/])
AMBARI-8020. /recommendations API mising tez.am.java.opts (aonishuk)
(aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=b1b36a16e44f8eaa8d17b32d588d6cd4608412a8)
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
/recommendations API mising tez.am.java.opts
---
Key: AMBARI-8020
URL: https://issues.apache.org/jira/browse/AMBARI-8020
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
Steps to reproduce
1)post request
/http://host:port/api/v1/stacks/HDP/versions/2.2/recommendations for geting
configurations by providing blueprint of host-layout
{hosts: [c6501.ambari.apache.org, c6502.ambari.apache.org,
c6503.ambari.apache.org], services: [YARN, TEZ, HIVE, OOZIE,
STORM, FALCON, MAPREDUCE2], recommend: configurations}
**ER** property tez.am.java_opts present
**AR** property tez.am.java_opts absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27288: Alerts: Convert Script-Style Oozie Alerts From Nagios
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27288/#review59004 --- Ship it! Ship It! - Alejandro Fernandez On Oct. 28, 2014, 4:36 p.m., Jonathan Hurley wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27288/ --- (Updated Oct. 28, 2014, 4:36 p.m.) Review request for Ambari, Alejandro Fernandez and Nate Cole. Bugs: AMBARI-8004 https://issues.apache.org/jira/browse/AMBARI-8004 Repository: ambari Description --- - Wrote Oozie SCRIPT alert to check Oozie status - Updated existing WEB alert messages to include the generated query string Diffs - ambari-agent/src/main/python/ambari_agent/alerts/web_alert.py e0e36ef ambari-agent/src/test/python/ambari_agent/TestAlerts.py 74d440f ambari-server/src/main/resources/stacks/HDP/2.0.6/services/GANGLIA/alerts.json 9b115d5 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HBASE/alerts.json 9846848 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/alerts.json 9ea31f0 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/alerts.json 3e4865d ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/alerts.json PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/OOZIE/package/files/alert_check_oozie_server.py PRE-CREATION ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/alerts.json 9793dbe ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/files/alert_nodemanager_health.py 70584b0 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/ZOOKEEPER/alerts.json 8827294 ambari-server/src/main/resources/stacks/HDP/2.1/services/FALCON/alerts.json c53230f ambari-server/src/main/resources/stacks/HDP/2.1/services/STORM/alerts.json df4909b ambari-server/src/main/resources/stacks/HDP/2.2/services/KAFKA/alerts.json a52feac ambari-server/src/main/resources/stacks/HDP/2.2/services/KNOX/alerts.json 3d2883e Diff: https://reviews.apache.org/r/27288/diff/ Testing --- Updated WEB alert tests to check for proper URL construction [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 6.908 s [INFO] Finished at: 2014-10-28T12:30:33-04:00 [INFO] Final Memory: 8M/81M [INFO] Thanks, Jonathan Hurley
Re: Review Request 27329: Upgrades : Not enough heap size for NameNode At EC2 cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/#review59005 --- Ship it! Ship It! - Dmitro Lisnichenko On Oct. 29, 2014, 5 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/ --- (Updated Oct. 29, 2014, 5 p.m.) Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko. Bugs: AMBARI-8017 https://issues.apache.org/jira/browse/AMBARI-8017 Repository: ambari Description --- STR: 1)Install old version 2)Enable security 3)Upgrade to 1.7.0 Actual result: NameNode become stopped sometimes. Could not start sometimes NameNode due heap size issue. Expected result: Have not heap size issue. Diffs - ambari-common/src/main/python/resource_management/libraries/functions/__init__.py e72512c ambari-common/src/main/python/resource_management/libraries/functions/format_jvm_option.py PRE-CREATION ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py 063beaa ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py cd06a67 ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py e117938 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/after-INSTALL/scripts/params.py a30899c ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-ANY/scripts/params.py 2fa05df ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-INSTALL/scripts/params.py e396d89 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-START/scripts/params.py 0aecb63 ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HDFS/package/scripts/params.py 376a466 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py 1442175 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py 1d41e58 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py f4d00d6 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py d9fa00a Diff: https://reviews.apache.org/r/27329/diff/ Testing --- manual deployment Thanks, Dmytro Sen
[jira] [Commented] (AMBARI-8020) /recommendations API mising tez.am.java.opts
[
https://issues.apache.org/jira/browse/AMBARI-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188594#comment-14188594
]
Hudson commented on AMBARI-8020:
SUCCESS: Integrated in Ambari-branch-1.7.0-docker #17 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0-docker/17/])
AMBARI-8020. /recommendations API mising tez.am.java.opts (aonishuk)
(aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=b1b36a16e44f8eaa8d17b32d588d6cd4608412a8)
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
/recommendations API mising tez.am.java.opts
---
Key: AMBARI-8020
URL: https://issues.apache.org/jira/browse/AMBARI-8020
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
Steps to reproduce
1)post request
/http://host:port/api/v1/stacks/HDP/versions/2.2/recommendations for geting
configurations by providing blueprint of host-layout
{hosts: [c6501.ambari.apache.org, c6502.ambari.apache.org,
c6503.ambari.apache.org], services: [YARN, TEZ, HIVE, OOZIE,
STORM, FALCON, MAPREDUCE2], recommend: configurations}
**ER** property tez.am.java_opts present
**AR** property tez.am.java_opts absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8014) Tune log4j parameters to reduce logs in ambari-server when slider view is enabled
[
https://issues.apache.org/jira/browse/AMBARI-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188597#comment-14188597
]
Hudson commented on AMBARI-8014:
SUCCESS: Integrated in Ambari-trunk-Commit-docker #47 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/47/])
AMBARI-8014. Tune log4j parameters to reduce logs in ambari-server when slider
view is enabled (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d638d9bffa11a12bd2fd3837f7d3004f81e3c095)
* ambari-server/conf/unix/log4j.properties
Tune log4j parameters to reduce logs in ambari-server when slider view is
enabled
-
Key: AMBARI-8014
URL: https://issues.apache.org/jira/browse/AMBARI-8014
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 1.7.0
Attachments: AMBARI-8014.patch
Need to set some namespaces and classes to WARN
{noformat}
log4j.logger.org.apache.hadoop.yarn.client=WARN
log4j.logger.org.apache.slider.common.tools.SliderUtils=WARN
log4j.logger.org.apache.ambari.server.security.authorization=WARN
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8020) /recommendations API mising tez.am.java.opts
[
https://issues.apache.org/jira/browse/AMBARI-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188596#comment-14188596
]
Hudson commented on AMBARI-8020:
SUCCESS: Integrated in Ambari-trunk-Commit-docker #47 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/47/])
AMBARI-8020. /recommendations API mising tez.am.java.opts (aonishuk)
(aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=6a29afb0ffc7770866cf5fb03fd8e41d7ea950e5)
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
/recommendations API mising tez.am.java.opts
---
Key: AMBARI-8020
URL: https://issues.apache.org/jira/browse/AMBARI-8020
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
Steps to reproduce
1)post request
/http://host:port/api/v1/stacks/HDP/versions/2.2/recommendations for geting
configurations by providing blueprint of host-layout
{hosts: [c6501.ambari.apache.org, c6502.ambari.apache.org,
c6503.ambari.apache.org], services: [YARN, TEZ, HIVE, OOZIE,
STORM, FALCON, MAPREDUCE2], recommend: configurations}
**ER** property tez.am.java_opts present
**AR** property tez.am.java_opts absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-8016) Cannot run hive tez query using HDP 2.1 stack
[
https://issues.apache.org/jira/browse/AMBARI-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-8016.
Resolution: Fixed
Committed to trunk and branch-1.7.0
Cannot run hive tez query using HDP 2.1 stack
-
Key: AMBARI-8016
URL: https://issues.apache.org/jira/browse/AMBARI-8016
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 1.7.0
Environment: HDP2.1
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 1.7.0
[root@c6401 views]# ambari-server --hash
5e1796a9d8d32eeaa24f13d29b81c437fef5acd8
1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive)
2) set Hive engine to tez
3) attempt to run hive query, get the error below;
{code}
[root@c6401 yum.repos.d]# su - hive
[hive@c6401 ~]$ cd /tmp
[hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip
--2014-10-29 01:28:52--
http://seanlahman.com/files/database/lahman591-csv.zip
Resolving seanlahman.com... 208.113.136.74
Connecting to seanlahman.com|208.113.136.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8337421 (8.0M) [application/zip]
Saving to: “lahman591-csv.zip”
100%[==] 8,337,421 3.45M/s in 2.3s
2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421]
[hive@c6401 tmp]$ unzip lahman591-csv.zip
Archive: lahman591-csv.zip
inflating: Managers.csv
inflating: ManagersHalf.csv
inflating: Pitching.csv
inflating: Salaries.csv
inflating: Schools.csv
inflating: SchoolsPlayers.csv
inflating: Teams.csv
inflating: TeamsFranchises.csv
inflating: TeamsHalf.csv
inflating: AllstarFull.csv
inflating: AwardsManagers.csv
inflating: AwardsPlayers.csv
inflating: AwardsShareManagers.csv
inflating: AwardsSharePlayers.csv
inflating: Batting.csv
inflating: Fielding.csv
inflating: FieldingOF.csv
inflating: readme59.txt
inflating: Master.csv
inflating: FieldingPost.csv
inflating: HallOfFame.csv
inflating: Appearances.csv
inflating: PitchingPost.csv
inflating: BattingPost.csv
inflating: SeriesPost.csv
[hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp
[hive@c6401 tmp]$ hive
Logging initialized using configuration in
file:/etc/hive/conf.dist/hive-log4j.properties
Exception in thread main java.lang.RuntimeException:
java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128)
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1120)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1120)
at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:748)
at
org.apache.hadoop.hdfs.DistributedFileSystem$15.init(DistributedFileSystem.java:736)
at
org.apache.hadoop.hdfs.DistributedFileSystem.listLocatedStatus(DistributedFileSystem.java:727)
at
org.apache.hadoop.fs.FileSystem.listLocatedStatus(FileSystem.java:1662)
at org.apache.hadoop.fs.FileSystem$5.init(FileSystem.java:1724)
at org.apache.hadoop.fs.FileSystem.listFiles(FileSystem.java:1721)
at
org.apache.tez.client.TezClientUtils.setupTezJarsLocalResources(TezClientUtils.java:164)
at org.apache.tez.client.TezSession.start(TezSession.java:105)
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionState.open(TezSessionState.java:185)
at
org.apache.hadoop.hive.ql.exec.tez.TezSessionState.open(TezSessionState.java:123)
at
[jira] [Commented] (AMBARI-8014) Tune log4j parameters to reduce logs in ambari-server when slider view is enabled
[
https://issues.apache.org/jira/browse/AMBARI-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188603#comment-14188603
]
Hudson commented on AMBARI-8014:
SUCCESS: Integrated in Ambari-trunk-Commit #746 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/746/])
AMBARI-8014. Tune log4j parameters to reduce logs in ambari-server when slider
view is enabled (smohanty:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d638d9bffa11a12bd2fd3837f7d3004f81e3c095)
* ambari-server/conf/unix/log4j.properties
Tune log4j parameters to reduce logs in ambari-server when slider view is
enabled
-
Key: AMBARI-8014
URL: https://issues.apache.org/jira/browse/AMBARI-8014
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 1.7.0
Reporter: Sumit Mohanty
Assignee: Sumit Mohanty
Fix For: 1.7.0
Attachments: AMBARI-8014.patch
Need to set some namespaces and classes to WARN
{noformat}
log4j.logger.org.apache.hadoop.yarn.client=WARN
log4j.logger.org.apache.slider.common.tools.SliderUtils=WARN
log4j.logger.org.apache.ambari.server.security.authorization=WARN
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8020) /recommendations API mising tez.am.java.opts
[
https://issues.apache.org/jira/browse/AMBARI-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188602#comment-14188602
]
Hudson commented on AMBARI-8020:
SUCCESS: Integrated in Ambari-trunk-Commit #746 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/746/])
AMBARI-8020. /recommendations API mising tez.am.java.opts (aonishuk)
(aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=6a29afb0ffc7770866cf5fb03fd8e41d7ea950e5)
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
/recommendations API mising tez.am.java.opts
---
Key: AMBARI-8020
URL: https://issues.apache.org/jira/browse/AMBARI-8020
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 1.7.0
Steps to reproduce
1)post request
/http://host:port/api/v1/stacks/HDP/versions/2.2/recommendations for geting
configurations by providing blueprint of host-layout
{hosts: [c6501.ambari.apache.org, c6502.ambari.apache.org,
c6503.ambari.apache.org], services: [YARN, TEZ, HIVE, OOZIE,
STORM, FALCON, MAPREDUCE2], recommend: configurations}
**ER** property tez.am.java_opts present
**AR** property tez.am.java_opts absent
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Review Request 27329: Upgrades : Not enough heap size for NameNode At EC2 cluster
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/#review59009 --- Ship it! Ship It! - Andrew Onischuk On Oct. 29, 2014, 5 p.m., Dmytro Sen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27329/ --- (Updated Oct. 29, 2014, 5 p.m.) Review request for Ambari, Andrew Onischuk and Dmitro Lisnichenko. Bugs: AMBARI-8017 https://issues.apache.org/jira/browse/AMBARI-8017 Repository: ambari Description --- STR: 1)Install old version 2)Enable security 3)Upgrade to 1.7.0 Actual result: NameNode become stopped sometimes. Could not start sometimes NameNode due heap size issue. Expected result: Have not heap size issue. Diffs - ambari-common/src/main/python/resource_management/libraries/functions/__init__.py e72512c ambari-common/src/main/python/resource_management/libraries/functions/format_jvm_option.py PRE-CREATION ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/after-INSTALL/scripts/params.py 063beaa ambari-server/src/main/resources/stacks/BIGTOP/0.8/hooks/before-START/scripts/params.py cd06a67 ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/HDFS/package/scripts/params.py e117938 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/after-INSTALL/scripts/params.py a30899c ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-ANY/scripts/params.py 2fa05df ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-INSTALL/scripts/params.py e396d89 ambari-server/src/main/resources/stacks/HDP/1.3.2/hooks/before-START/scripts/params.py 0aecb63 ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HDFS/package/scripts/params.py 376a466 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/params.py 1442175 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/params.py 1d41e58 ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py f4d00d6 ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HDFS/package/scripts/params.py d9fa00a Diff: https://reviews.apache.org/r/27329/diff/ Testing --- manual deployment Thanks, Dmytro Sen
[jira] [Updated] (AMBARI-7939) Customize Services doesn't pick up default configs from HDPWIN stack definition
[ https://issues.apache.org/jira/browse/AMBARI-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Florian Barca updated AMBARI-7939: -- Attachment: AMBARI-7939.1.patch +Added the missing cluster-env.xml. +Added the missing properties in the services' site configuration files. +Reinforced the configuration load error handling +Fixed loadClusterConfigError() parameters. +Fixed hbase-env.cmd template. Customize Services doesn't pick up default configs from HDPWIN stack definition --- Key: AMBARI-7939 URL: https://issues.apache.org/jira/browse/AMBARI-7939 Project: Ambari Issue Type: Task Components: ambari-server, ambari-web Affects Versions: branch-windows-dev Environment: WIndows Server 64-bit Reporter: Florian Barca Assignee: Florian Barca Fix For: branch-windows-dev Attachments: AMBARI-7939.1.patch A large number of properties are not being properly supplied in the service configuration wizard (step 7). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8019) Create ability to disable protocols for https connections in Ambari.
[ https://issues.apache.org/jira/browse/AMBARI-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188645#comment-14188645 ] Hudson commented on AMBARI-8019: SUCCESS: Integrated in Ambari-branch-1.7.0 #246 (See [https://builds.apache.org/job/Ambari-branch-1.7.0/246/]) AMBARI-8019. Create ability to disable protocols for https connections in Ambari. (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=1b3cfd6c42ee863fe11816e108ced0d4f52d85f4) * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/conf/unix/ambari.properties * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java Create ability to disable protocols for https connections in Ambari. Key: AMBARI-8019 URL: https://issues.apache.org/jira/browse/AMBARI-8019 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.7.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 1.7.0 Attachments: AMBARI-8019.patch, AMBARI-8019_branch-1.7.0.patch Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-8022: --- Attachment: ambari-8022-v2.txt Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt Carter made the following notes: 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8019) Create ability to disable protocols for https connections in Ambari.
[ https://issues.apache.org/jira/browse/AMBARI-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188666#comment-14188666 ] Hudson commented on AMBARI-8019: SUCCESS: Integrated in Ambari-branch-1.7.0-docker #18 (See [https://builds.apache.org/job/Ambari-branch-1.7.0-docker/18/]) AMBARI-8019. Create ability to disable protocols for https connections in Ambari. (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=1b3cfd6c42ee863fe11816e108ced0d4f52d85f4) * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * ambari-server/conf/unix/ambari.properties Create ability to disable protocols for https connections in Ambari. Key: AMBARI-8019 URL: https://issues.apache.org/jira/browse/AMBARI-8019 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.7.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 1.7.0 Attachments: AMBARI-8019.patch, AMBARI-8019_branch-1.7.0.patch Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8023) Cluster admin should be able to dynamically display a subset of Ganglia metrics
Sujeet Varakhedi created AMBARI-8023: Summary: Cluster admin should be able to dynamically display a subset of Ganglia metrics Key: AMBARI-8023 URL: https://issues.apache.org/jira/browse/AMBARI-8023 Project: Ambari Issue Type: Improvement Components: ambari-metrics Reporter: Sujeet Varakhedi Currently metrics definitions need to be statically defined in the metrics.json file. But for services like HAWQ, admins need to see per query metrics for query administration and control. HAWQ today is able to push per query metrics to Ganglia and so It will be good to have a mechanism where from Amabri, an admin can query the metrics list directly from Ganglia and select a subset to be displayed on the service page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8024) [Test] ambari-server unit test failures: Index out of range error
Florian Barca created AMBARI-8024:
-
Summary: [Test] ambari-server unit test failures: Index out of
range error
Key: AMBARI-8024
URL: https://issues.apache.org/jira/browse/AMBARI-8024
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: branch-windows-dev
Environment: Linux
Reporter: Florian Barca
Assignee: Florian Barca
Fix For: branch-windows-dev
12 unit test failures with similar output:
Running tests for stack:1.3.2 service:before-ANY
test_hook_default (test_before_any.TestHookBeforeInstall) ... ERROR
==
ERROR: test_hook_default (test_before_any.TestHookBeforeInstall)
--
Traceback (most recent call last):
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py,
line 1199, in patched
return func(*args, **keywargs)
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-server/src/test/python/stacks/1.3.2/hooks/before-ANY/test_before_any.py,
line 132, in test_hook_default
content = StaticFile('changeToSecureUid.sh'),
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/main/python/resource_management/core/source.py,
line 59, in __init__
super(StaticFile, self).__init__(name)
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/main/python/resource_management/core/source.py,
line 37, in __init__
self.env = Environment.get_instance()
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/main/python/resource_management/core/environment.py,
line 164, in get_instance
return cls._instances[-1]
IndexError: list index out of range
--
Ran 1 test in 0.020s
FAILED (errors=1)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8019) Create ability to disable protocols for https connections in Ambari.
[ https://issues.apache.org/jira/browse/AMBARI-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188681#comment-14188681 ] Hudson commented on AMBARI-8019: SUCCESS: Integrated in Ambari-trunk-Commit-docker #48 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/48/]) AMBARI-8019. Create ability to disable protocols for https connections in Ambari. (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=0e93c5d5e44a93202a2dfe01713b74fad2788546) * ambari-server/conf/unix/ambari.properties * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java Create ability to disable protocols for https connections in Ambari. Key: AMBARI-8019 URL: https://issues.apache.org/jira/browse/AMBARI-8019 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.7.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 1.7.0 Attachments: AMBARI-8019.patch, AMBARI-8019_branch-1.7.0.patch Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8025) [Test] ambari-server unit test failures: Exception: Local OS is not compatible with cluster primary OS family
Florian Barca created AMBARI-8025: - Summary: [Test] ambari-server unit test failures: Exception: Local OS is not compatible with cluster primary OS family Key: AMBARI-8025 URL: https://issues.apache.org/jira/browse/AMBARI-8025 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: branch-windows-dev Environment: Linux Reporter: Florian Barca Assignee: Florian Barca Fix For: branch-windows-dev 6 unit test failures with similar output: == ERROR: test_os_type_check (TestOSCheck.TestOSCheck) -- Traceback (most recent call last): File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1199, in patched return func(*args, **keywargs) File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-server/src/test/python/TestOSCheck.py, line 238, in test_os_type_check os_check_type.main() File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-server/src/main/python/os_check_type.py, line 40, in main raise Exception(Local OS is not compatible with cluster primary OS family. Please perform manual bootstrap on this host.) Exception: Local OS is not compatible with cluster primary OS family. Please perform manual bootstrap on this host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8026) [Test] ambari-server unit test failures: AttributeError
Florian Barca created AMBARI-8026: - Summary: [Test] ambari-server unit test failures: AttributeError Key: AMBARI-8026 URL: https://issues.apache.org/jira/browse/AMBARI-8026 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: branch-windows-dev Environment: Linux Reporter: Florian Barca Assignee: Florian Barca Fix For: branch-windows-dev ERROR: test_ambariServerSetupWithCustomDbName (TestAmbariServer.TestAmbariServer) -- Traceback (most recent call last): File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1191, in patched arg = patching.__enter__() File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1266, in __enter__ original, local = self.get_original() File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1240, in get_original %s does not have the attribute %r % (target, name) AttributeError: module 'ambari-server' from '/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-server/src/main/python/ambari-server.py' does not have the attribute 'download_and_install_jdk' ERROR: test_reset (TestAmbariServer.TestAmbariServer) -- Traceback (most recent call last): File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1191, in patched arg = patching.__enter__() File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1266, in __enter__ original, local = self.get_original() File /Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py, line 1240, in get_original %s does not have the attribute %r % (target, name) AttributeError: module 'ambari-server' from '/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-server/src/main/python/ambari-server.py' does not have the attribute 'is_server_running' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8016) Cannot run hive tez query using HDP 2.1 stack
[
https://issues.apache.org/jira/browse/AMBARI-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188679#comment-14188679
]
Hudson commented on AMBARI-8016:
SUCCESS: Integrated in Ambari-trunk-Commit #747 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/747/])
AMBARI-8016 Cannot run hive tez query using HDP 2.1 stack (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=957077c5c986272db4715b1ea98c2c4bb7fcb917)
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/hive_server.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/install_jars.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/params.py
Cannot run hive tez query using HDP 2.1 stack
-
Key: AMBARI-8016
URL: https://issues.apache.org/jira/browse/AMBARI-8016
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 1.7.0
Environment: HDP2.1
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 1.7.0
[root@c6401 views]# ambari-server --hash
5e1796a9d8d32eeaa24f13d29b81c437fef5acd8
1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive)
2) set Hive engine to tez
3) attempt to run hive query, get the error below;
{code}
[root@c6401 yum.repos.d]# su - hive
[hive@c6401 ~]$ cd /tmp
[hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip
--2014-10-29 01:28:52--
http://seanlahman.com/files/database/lahman591-csv.zip
Resolving seanlahman.com... 208.113.136.74
Connecting to seanlahman.com|208.113.136.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8337421 (8.0M) [application/zip]
Saving to: “lahman591-csv.zip”
100%[==] 8,337,421 3.45M/s in 2.3s
2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421]
[hive@c6401 tmp]$ unzip lahman591-csv.zip
Archive: lahman591-csv.zip
inflating: Managers.csv
inflating: ManagersHalf.csv
inflating: Pitching.csv
inflating: Salaries.csv
inflating: Schools.csv
inflating: SchoolsPlayers.csv
inflating: Teams.csv
inflating: TeamsFranchises.csv
inflating: TeamsHalf.csv
inflating: AllstarFull.csv
inflating: AwardsManagers.csv
inflating: AwardsPlayers.csv
inflating: AwardsShareManagers.csv
inflating: AwardsSharePlayers.csv
inflating: Batting.csv
inflating: Fielding.csv
inflating: FieldingOF.csv
inflating: readme59.txt
inflating: Master.csv
inflating: FieldingPost.csv
inflating: HallOfFame.csv
inflating: Appearances.csv
inflating: PitchingPost.csv
inflating: BattingPost.csv
inflating: SeriesPost.csv
[hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp
[hive@c6401 tmp]$ hive
Logging initialized using configuration in
file:/etc/hive/conf.dist/hive-log4j.properties
Exception in thread main java.lang.RuntimeException:
java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128)
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1120)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1120)
at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:748)
at
org.apache.hadoop.hdfs.DistributedFileSystem$15.init(DistributedFileSystem.java:736)
at
org.apache.hadoop.hdfs.DistributedFileSystem.listLocatedStatus(DistributedFileSystem.java:727)
at
[jira] [Commented] (AMBARI-8019) Create ability to disable protocols for https connections in Ambari.
[ https://issues.apache.org/jira/browse/AMBARI-8019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188678#comment-14188678 ] Hudson commented on AMBARI-8019: SUCCESS: Integrated in Ambari-trunk-Commit #747 (See [https://builds.apache.org/job/Ambari-trunk-Commit/747/]) AMBARI-8019. Create ability to disable protocols for https connections in Ambari. (dlysnichenko) (dlysnichenko: http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=0e93c5d5e44a93202a2dfe01713b74fad2788546) * ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * ambari-server/conf/unix/ambari.properties Create ability to disable protocols for https connections in Ambari. Key: AMBARI-8019 URL: https://issues.apache.org/jira/browse/AMBARI-8019 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 1.7.0 Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Fix For: 1.7.0 Attachments: AMBARI-8019.patch, AMBARI-8019_branch-1.7.0.patch Create ability to disable protocols for https connections in Ambari. Port our patch from EAR-660 to 1.7.0 and trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8016) Cannot run hive tez query using HDP 2.1 stack
[
https://issues.apache.org/jira/browse/AMBARI-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188704#comment-14188704
]
Hudson commented on AMBARI-8016:
SUCCESS: Integrated in Ambari-branch-1.7.0 #247 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0/247/])
AMBARI-8016 Cannot run hive tez query using HDP 2.1 stack (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=ee9be26cc7168b607242cab8f0956ff5e21cf349)
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/install_jars.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/hive_server.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/params.py
Cannot run hive tez query using HDP 2.1 stack
-
Key: AMBARI-8016
URL: https://issues.apache.org/jira/browse/AMBARI-8016
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 1.7.0
Environment: HDP2.1
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 1.7.0
[root@c6401 views]# ambari-server --hash
5e1796a9d8d32eeaa24f13d29b81c437fef5acd8
1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive)
2) set Hive engine to tez
3) attempt to run hive query, get the error below;
{code}
[root@c6401 yum.repos.d]# su - hive
[hive@c6401 ~]$ cd /tmp
[hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip
--2014-10-29 01:28:52--
http://seanlahman.com/files/database/lahman591-csv.zip
Resolving seanlahman.com... 208.113.136.74
Connecting to seanlahman.com|208.113.136.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8337421 (8.0M) [application/zip]
Saving to: “lahman591-csv.zip”
100%[==] 8,337,421 3.45M/s in 2.3s
2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421]
[hive@c6401 tmp]$ unzip lahman591-csv.zip
Archive: lahman591-csv.zip
inflating: Managers.csv
inflating: ManagersHalf.csv
inflating: Pitching.csv
inflating: Salaries.csv
inflating: Schools.csv
inflating: SchoolsPlayers.csv
inflating: Teams.csv
inflating: TeamsFranchises.csv
inflating: TeamsHalf.csv
inflating: AllstarFull.csv
inflating: AwardsManagers.csv
inflating: AwardsPlayers.csv
inflating: AwardsShareManagers.csv
inflating: AwardsSharePlayers.csv
inflating: Batting.csv
inflating: Fielding.csv
inflating: FieldingOF.csv
inflating: readme59.txt
inflating: Master.csv
inflating: FieldingPost.csv
inflating: HallOfFame.csv
inflating: Appearances.csv
inflating: PitchingPost.csv
inflating: BattingPost.csv
inflating: SeriesPost.csv
[hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp
[hive@c6401 tmp]$ hive
Logging initialized using configuration in
file:/etc/hive/conf.dist/hive-log4j.properties
Exception in thread main java.lang.RuntimeException:
java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128)
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1120)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1120)
at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:748)
at
org.apache.hadoop.hdfs.DistributedFileSystem$15.init(DistributedFileSystem.java:736)
at
org.apache.hadoop.hdfs.DistributedFileSystem.listLocatedStatus(DistributedFileSystem.java:727)
at
[jira] [Commented] (AMBARI-8016) Cannot run hive tez query using HDP 2.1 stack
[
https://issues.apache.org/jira/browse/AMBARI-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188742#comment-14188742
]
Hudson commented on AMBARI-8016:
SUCCESS: Integrated in Ambari-branch-1.7.0-docker #19 (See
[https://builds.apache.org/job/Ambari-branch-1.7.0-docker/19/])
AMBARI-8016 Cannot run hive tez query using HDP 2.1 stack (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=ee9be26cc7168b607242cab8f0956ff5e21cf349)
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/install_jars.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/params.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/hive_server.py
Cannot run hive tez query using HDP 2.1 stack
-
Key: AMBARI-8016
URL: https://issues.apache.org/jira/browse/AMBARI-8016
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 1.7.0
Environment: HDP2.1
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 1.7.0
[root@c6401 views]# ambari-server --hash
5e1796a9d8d32eeaa24f13d29b81c437fef5acd8
1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive)
2) set Hive engine to tez
3) attempt to run hive query, get the error below;
{code}
[root@c6401 yum.repos.d]# su - hive
[hive@c6401 ~]$ cd /tmp
[hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip
--2014-10-29 01:28:52--
http://seanlahman.com/files/database/lahman591-csv.zip
Resolving seanlahman.com... 208.113.136.74
Connecting to seanlahman.com|208.113.136.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8337421 (8.0M) [application/zip]
Saving to: “lahman591-csv.zip”
100%[==] 8,337,421 3.45M/s in 2.3s
2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421]
[hive@c6401 tmp]$ unzip lahman591-csv.zip
Archive: lahman591-csv.zip
inflating: Managers.csv
inflating: ManagersHalf.csv
inflating: Pitching.csv
inflating: Salaries.csv
inflating: Schools.csv
inflating: SchoolsPlayers.csv
inflating: Teams.csv
inflating: TeamsFranchises.csv
inflating: TeamsHalf.csv
inflating: AllstarFull.csv
inflating: AwardsManagers.csv
inflating: AwardsPlayers.csv
inflating: AwardsShareManagers.csv
inflating: AwardsSharePlayers.csv
inflating: Batting.csv
inflating: Fielding.csv
inflating: FieldingOF.csv
inflating: readme59.txt
inflating: Master.csv
inflating: FieldingPost.csv
inflating: HallOfFame.csv
inflating: Appearances.csv
inflating: PitchingPost.csv
inflating: BattingPost.csv
inflating: SeriesPost.csv
[hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp
[hive@c6401 tmp]$ hive
Logging initialized using configuration in
file:/etc/hive/conf.dist/hive-log4j.properties
Exception in thread main java.lang.RuntimeException:
java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128)
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1120)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1120)
at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:748)
at
org.apache.hadoop.hdfs.DistributedFileSystem$15.init(DistributedFileSystem.java:736)
at
org.apache.hadoop.hdfs.DistributedFileSystem.listLocatedStatus(DistributedFileSystem.java:727)
[jira] [Commented] (AMBARI-8016) Cannot run hive tez query using HDP 2.1 stack
[
https://issues.apache.org/jira/browse/AMBARI-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188767#comment-14188767
]
Hudson commented on AMBARI-8016:
SUCCESS: Integrated in Ambari-trunk-Commit-docker #49 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/49/])
AMBARI-8016 Cannot run hive tez query using HDP 2.1 stack (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=957077c5c986272db4715b1ea98c2c4bb7fcb917)
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/params.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/install_jars.py
* ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/package/scripts/hive_server.py
Cannot run hive tez query using HDP 2.1 stack
-
Key: AMBARI-8016
URL: https://issues.apache.org/jira/browse/AMBARI-8016
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 1.7.0
Environment: HDP2.1
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 1.7.0
[root@c6401 views]# ambari-server --hash
5e1796a9d8d32eeaa24f13d29b81c437fef5acd8
1) Install HDP 2.1 (hdfs, yarn, mr, tez, zk, hive)
2) set Hive engine to tez
3) attempt to run hive query, get the error below;
{code}
[root@c6401 yum.repos.d]# su - hive
[hive@c6401 ~]$ cd /tmp
[hive@c6401 tmp]$ wget http://seanlahman.com/files/database/lahman591-csv.zip
--2014-10-29 01:28:52--
http://seanlahman.com/files/database/lahman591-csv.zip
Resolving seanlahman.com... 208.113.136.74
Connecting to seanlahman.com|208.113.136.74|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8337421 (8.0M) [application/zip]
Saving to: “lahman591-csv.zip”
100%[==] 8,337,421 3.45M/s in 2.3s
2014-10-29 01:28:54 (3.45 MB/s) - “lahman591-csv.zip” saved [8337421/8337421]
[hive@c6401 tmp]$ unzip lahman591-csv.zip
Archive: lahman591-csv.zip
inflating: Managers.csv
inflating: ManagersHalf.csv
inflating: Pitching.csv
inflating: Salaries.csv
inflating: Schools.csv
inflating: SchoolsPlayers.csv
inflating: Teams.csv
inflating: TeamsFranchises.csv
inflating: TeamsHalf.csv
inflating: AllstarFull.csv
inflating: AwardsManagers.csv
inflating: AwardsPlayers.csv
inflating: AwardsShareManagers.csv
inflating: AwardsSharePlayers.csv
inflating: Batting.csv
inflating: Fielding.csv
inflating: FieldingOF.csv
inflating: readme59.txt
inflating: Master.csv
inflating: FieldingPost.csv
inflating: HallOfFame.csv
inflating: Appearances.csv
inflating: PitchingPost.csv
inflating: BattingPost.csv
inflating: SeriesPost.csv
[hive@c6401 tmp]$ hadoop fs -copyFromLocal Schools.csv /tmp
[hive@c6401 tmp]$ hive
Logging initialized using configuration in
file:/etc/hive/conf.dist/hive-log4j.properties
Exception in thread main java.lang.RuntimeException:
java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:358)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.io.FileNotFoundException: File does not exist:
hdfs://c6401.ambari.apache.org:8020/apps/tez
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1128)
at
org.apache.hadoop.hdfs.DistributedFileSystem$17.doCall(DistributedFileSystem.java:1120)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1120)
at org.apache.hadoop.fs.FileSystem.resolvePath(FileSystem.java:748)
at
org.apache.hadoop.hdfs.DistributedFileSystem$15.init(DistributedFileSystem.java:736)
at
org.apache.hadoop.hdfs.DistributedFileSystem.listLocatedStatus(DistributedFileSystem.java:727)
Nagios Alert Ambari 2.0
Hi Committers Contributors, With Ambari 2.0, a new alerts framework has been implemented with the intent to replace Nagios. If you would like to learn more about this feature, the design documents can be found in the Jira epic at https://issues.apache.org/jira/browse/AMBARI-6354. The work has been completed to move the HDP 2.x stack over from Nagios to the internal alerts framework. However, HDP 1.x and Bigtop have not yet been migrated. I would like to propose that we move all stacks off of Nagios so that we can remove that dependency from Ambari completely. This also means that upon upgrading from a prior Nagios-enabled release of Ambari, Nagios will be removed as a dependent service. It will no longer be a part of the managed cluster. This will allow us to also remove any Nagios-specific areas of the codebase that would otherwise need to remain for legacy purposes. It would also relieve the requirement on clients to have intimate knowledge of which stack/version can be Nagios-enabled. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Updated] (AMBARI-6354) Alerts Redesign
[ https://issues.apache.org/jira/browse/AMBARI-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-6354: Attachment: AlertTechDesignPublic.pdf Alerts Redesign --- Key: AMBARI-6354 URL: https://issues.apache.org/jira/browse/AMBARI-6354 Project: Ambari Issue Type: Epic Components: ambari-agent, ambari-server, ambari-web Reporter: Nate Cole Assignee: Nate Cole Fix For: 2.0.0 Attachments: AlertTechDesignPublic.pdf, AlertTechDesignPublic.pdf The purpose of this umbrella JIRA is to track a new feature that enables Ambari to be the source of Alert data for a cluster. * Black box Nagios and not make it a hard dependency of Ambari. * Allow custom defined alerts and thresholds. * Flexibly define how alerts get published, and recipients of those alerts. * Use stacks to define baseline alerts for a cluster that can themselves be customized. (As design documents are completed, they will be attached to this JIRA) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-8022: Description: 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. was: Carter made the following notes: 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-8022: Fix Version/s: 1.7.0 Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Affects Versions: 1.7.0 Reporter: Ted Yu Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-8022: Affects Version/s: 1.7.0 Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Affects Versions: 1.7.0 Reporter: Ted Yu Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-8022: Component/s: stacks Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 1.7.0 Reporter: Ted Yu Labels: hdp Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-8022: Labels: hdp (was: ) Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 1.7.0 Reporter: Ted Yu Labels: hdp Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188786#comment-14188786 ] Yusaku Sako commented on AMBARI-8022: - Thanks [~te...@apache.org] / [~devaraj] I'll take a look. Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8024) [Test] ambari-server unit test failures: Index out of range error
[
https://issues.apache.org/jira/browse/AMBARI-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Barca updated AMBARI-8024:
--
Attachment: AMBARI-8024.0.patch
+Fixed mock module import directives
[Test] ambari-server unit test failures: Index out of range error
---
Key: AMBARI-8024
URL: https://issues.apache.org/jira/browse/AMBARI-8024
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: branch-windows-dev
Environment: Linux
Reporter: Florian Barca
Assignee: Florian Barca
Fix For: branch-windows-dev
Attachments: AMBARI-8024.0.patch
Original Estimate: 12h
Remaining Estimate: 12h
12 unit test failures with similar output:
Running tests for stack:1.3.2 service:before-ANY
test_hook_default (test_before_any.TestHookBeforeInstall) ... ERROR
==
ERROR: test_hook_default (test_before_any.TestHookBeforeInstall)
--
Traceback (most recent call last):
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/test/python/mock/mock.py,
line 1199, in patched
return func(*args, **keywargs)
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-server/src/test/python/stacks/1.3.2/hooks/before-ANY/test_before_any.py,
line 132, in test_hook_default
content = StaticFile('changeToSecureUid.sh'),
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/main/python/resource_management/core/source.py,
line 59, in __init__
super(StaticFile, self).__init__(name)
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/main/python/resource_management/core/source.py,
line 37, in __init__
self.env = Environment.get_instance()
File
/Users/fbarca/ambari-vagrant/centos6.4/ambari/ambari-common/src/main/python/resource_management/core/environment.py,
line 164, in get_instance
return cls._instances[-1]
IndexError: list index out of range
--
Ran 1 test in 0.020s
FAILED (errors=1)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8018) Show all properties for source subresource in alert_definitions API response
[
https://issues.apache.org/jira/browse/AMBARI-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188809#comment-14188809
]
Hudson commented on AMBARI-8018:
SUCCESS: Integrated in Ambari-trunk-Commit #748 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/748/])
AMBARI-8018 - Show all properties for source subresource in alert_definitions
API response (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d063cc637991c152d0dfd2da5479f66909197f2a)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProviderTest.java
Show all properties for source subresource in alert_definitions API response
Key: AMBARI-8018
URL: https://issues.apache.org/jira/browse/AMBARI-8018
Project: Ambari
Issue Type: Task
Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.0.0
Attachments: AMBARI-8018.patch
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
{code}
but response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1 is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https : {{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property : {{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
And for mapping data on UI we need the full source data. Currently we need to
make one request for all alert_definitions with all data except source and
one request for each alert_definition just to get all source data.
So after this change only one request will be enough to get all
alert_definitions data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188812#comment-14188812 ] Yusaku Sako commented on AMBARI-8022: - [~te...@apache.org] / [~devaraj] There's v1 and v2 posted. Which one do we want? v1 says to remove hbase.hstore.flush.retries.number, while v2 does not have this entry. From the description, we do want to remove it, correct? Also, if we want 4GB as the default heapsize, shouldn't the value be 4096? Is 4196 intentional? Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 1.7.0 Reporter: Ted Yu Labels: hdp Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v2.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-8022: --- Attachment: ambari-8022-v3.txt Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 1.7.0 Reporter: Ted Yu Labels: hdp Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v3.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-8027) Admin View: need better username validation
Andrii Tkach created AMBARI-8027: Summary: Admin View: need better username validation Key: AMBARI-8027 URL: https://issues.apache.org/jira/browse/AMBARI-8027 Project: Ambari Issue Type: Bug Components: ambari-admin, ambari-server, ambari-web Affects Versions: 1.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 1.7.0 1. Go to Manage Ambari 2. Try to create user Result: user name field accept any special characters (!*?=.|/) etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-8022: --- Attachment: (was: ambari-8022-v2.txt) Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 1.7.0 Reporter: Ted Yu Labels: hdp Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v3.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8022) Provide better values for selected HBase configs
[ https://issues.apache.org/jira/browse/AMBARI-8022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188817#comment-14188817 ] Ted Yu commented on AMBARI-8022: Please take a look at patch v3 where hbase.hstore.flush.retries.number is marked deleted. Adjusted heap size as well. Provide better values for selected HBase configs Key: AMBARI-8022 URL: https://issues.apache.org/jira/browse/AMBARI-8022 Project: Ambari Issue Type: Improvement Components: stacks Affects Versions: 1.7.0 Reporter: Ted Yu Labels: hdp Fix For: 1.7.0 Attachments: ambari-8022-v1.txt, ambari-8022-v3.txt 1. retries.number should not be set (use the default instead) 2. Major compaction should be set to the 604... number rather than the 864... number Ambari is using now. 3. block multiplier should be 4 not 2. In addition, hbase-env.sh uses a very small heap size for regionservers. This needs to be increased to 4GB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-8021) Hostname information included in Blueprint export for HDP 2.2 cluster
[ https://issues.apache.org/jira/browse/AMBARI-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Nettleton updated AMBARI-8021: - Attachment: AMBARI-8021.patch AMBARI-8021_1.7.0.patch Hostname information included in Blueprint export for HDP 2.2 cluster - Key: AMBARI-8021 URL: https://issues.apache.org/jira/browse/AMBARI-8021 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 1.7.0 Reporter: Robert Nettleton Assignee: Robert Nettleton Fix For: 1.7.0 Attachments: AMBARI-8021.patch, AMBARI-8021_1.7.0.patch After launching an HDP 2.2 cluster using the Ambari UI, a Blueprint exported from the cluster will include hostname information for the following properties: 1. Hostname info appears after security is enabled (Knox also deployed in cluster): core-site : hadoop.proxyuser.knox.hosts webhcat-site: webhcat.proxyuser.knox.hosts oozie-site: hadoop.proxyuser.knox.hosts 2. kafka-broker: kafka.ganglia.metrics.host 3. yarn-site: hadoop.registry.zk.quorum slider-client: slider.zookeeper.quorum kafka-broker: zookeeper.connect The Knox-related properties only appear in the exported Blueprint when Knox and Security are enabled, but the other properties appear when the various services are deployed in either case (Slider, Kafka, Yarn). The Blueprint configuration processor needs to be updated to account for these new properties in the HDP 2.2 stack. I'm working on a patch for this, and will be submitting it shortly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8018) Show all properties for source subresource in alert_definitions API response
[
https://issues.apache.org/jira/browse/AMBARI-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14188822#comment-14188822
]
Hudson commented on AMBARI-8018:
SUCCESS: Integrated in Ambari-trunk-Commit-docker #50 (See
[https://builds.apache.org/job/Ambari-trunk-Commit-docker/50/])
AMBARI-8018 - Show all properties for source subresource in alert_definitions
API response (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.gita=commith=d063cc637991c152d0dfd2da5479f66909197f2a)
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProviderTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/AlertDefinitionResourceProvider.java
Show all properties for source subresource in alert_definitions API response
Key: AMBARI-8018
URL: https://issues.apache.org/jira/browse/AMBARI-8018
Project: Ambari
Issue Type: Task
Components: alerts, ambari-server
Affects Versions: 2.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.0.0
Attachments: AMBARI-8018.patch
Currently response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*
is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions?fields=*;,
items : [
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
type : WEB
}
}
}...
{code}
but response for
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1 is:
{code}
{
href :
http://c6401.ambari.apache.org:8080/api/v1/clusters/c/alert_definitions/1;,
AlertDefinition : {
cluster_name : c,
component_name : HISTORYSERVER,
enabled : true,
id : 1,
interval : 1,
label : History Server Web UI,
name : mapreduce_history_server_webui,
scope : ANY,
service_name : MAPREDUCE2,
source : {
reporting : {
ok : {
text : HTTP {0} response in {3:.4f} seconds
},
warning : {
text : HTTP {0} response in {3:.4f} seconds
},
critical : {
text : Connection failed to {1}:{2}
}
},
type : WEB,
uri : {
http : {{mapred-site/mapreduce.jobhistory.webapp.address}},
https : {{mapred-site/mapreduce.jobhistory.webapp.https.address}},
https_property : {{mapred-site/mapreduce.jobhistory.http.policy}},
https_property_value : HTTPS_ONLY,
default_port : 0.0
}
}
}
}
{code}
And for mapping data on UI we need the full source data. Currently we need to
make one request for all alert_definitions with all data except source and
one request for each alert_definition just to get all source data.
So after this change only one request will be enough to get all
alert_definitions data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-8027) Admin View: need better username validation
[ https://issues.apache.org/jira/browse/AMBARI-8027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-8027: - Attachment: AMBARI-8027_branch-1.7.0.patch Admin View: need better username validation --- Key: AMBARI-8027 URL: https://issues.apache.org/jira/browse/AMBARI-8027 Project: Ambari Issue Type: Bug Components: ambari-admin, ambari-server, ambari-web Affects Versions: 1.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 1.7.0 Attachments: AMBARI-8027_branch-1.7.0.patch 1. Go to Manage Ambari 2. Try to create user Result: user name field accept any special characters (!*?=.|/) etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
