[jira] [Updated] (AMBARI-15525) Parameterize distro-specific stack information for SPARK
[ https://issues.apache.org/jira/browse/AMBARI-15525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15525: --- Status: Patch Available (was: In Progress) > Parameterize distro-specific stack information for SPARK > > > Key: AMBARI-15525 > URL: https://issues.apache.org/jira/browse/AMBARI-15525 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-15525.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15526) Parameterize distro-specific stack information for KAFKA
[ https://issues.apache.org/jira/browse/AMBARI-15526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15526: --- Attachment: AMBARI-15526.patch > Parameterize distro-specific stack information for KAFKA > > > Key: AMBARI-15526 > URL: https://issues.apache.org/jira/browse/AMBARI-15526 > Project: Ambari > Issue Type: Technical task > Components: stacks >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > Attachments: AMBARI-15526.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15549) Delete service: Unable to delete a service even when it's host components are in a removable state.
[ https://issues.apache.org/jira/browse/AMBARI-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15549: --- Attachment: AMBARI-15549.patch > Delete service: Unable to delete a service even when it's host components are > in a removable state. > --- > > Key: AMBARI-15549 > URL: https://issues.apache.org/jira/browse/AMBARI-15549 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: AMBARI-15549.patch > > > It is possible for a cluster to get in a state where > # desired state of a host component was in INSTALLED state > # desired state of a service component is in STARTED state > # Delete service API fails with the error message of the component being in > non-removable state (STARTED). > *Expected behavior:* If all host components have their desired state in > INSTALLED then deletion of a service should succeed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15549) Delete service: Unable to delete a service even when it's host components are in a removable state.
[ https://issues.apache.org/jira/browse/AMBARI-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15549: --- Attachment: (was: AMBARI-15549.patch) > Delete service: Unable to delete a service even when it's host components are > in a removable state. > --- > > Key: AMBARI-15549 > URL: https://issues.apache.org/jira/browse/AMBARI-15549 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: AMBARI-15549.patch > > > It is possible for a cluster to get in a state where > # desired state of a host component was in INSTALLED state > # desired state of a service component is in STARTED state > # Delete service API fails with the error message of the component being in > non-removable state (STARTED). > *Expected behavior:* If all host components have their desired state in > INSTALLED then deletion of a service should succeed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15549) Delete service: Unable to delete a service even when it's host components are in a removable state.
[ https://issues.apache.org/jira/browse/AMBARI-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15549: --- Attachment: AMBARI-15549.patch > Delete service: Unable to delete a service even when it's host components are > in a removable state. > --- > > Key: AMBARI-15549 > URL: https://issues.apache.org/jira/browse/AMBARI-15549 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: AMBARI-15549.patch > > > It is possible for a cluster to get in a state where > # desired state of a host component was in INSTALLED state > # desired state of a service component is in STARTED state > # Delete service API fails with the error message of the component being in > non-removable state (STARTED). > *Expected behavior:* If all host components have their desired state in > INSTALLED then deletion of a service should succeed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15549) Delete service: Unable to delete a service even when it's host components are in a removable state.
[ https://issues.apache.org/jira/browse/AMBARI-15549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-15549: --- Status: Patch Available (was: Open) > Delete service: Unable to delete a service even when it's host components are > in a removable state. > --- > > Key: AMBARI-15549 > URL: https://issues.apache.org/jira/browse/AMBARI-15549 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.4.0 > > Attachments: AMBARI-15549.patch > > > It is possible for a cluster to get in a state where > # desired state of a host component was in INSTALLED state > # desired state of a service component is in STARTED state > # Delete service API fails with the error message of the component being in > non-removable state (STARTED). > *Expected behavior:* If all host components have their desired state in > INSTALLED then deletion of a service should succeed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15546) Hosts filter: placeholder text is too prominent
[ https://issues.apache.org/jira/browse/AMBARI-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209760#comment-15209760 ] Hudson commented on AMBARI-15546: - FAILURE: Integrated in Ambari-trunk-Commit #4536 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4536/]) AMBARI-15546. Hosts filter: placeholder text is too prominent (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=18dc714dbfbb655c8fcf2eba8585054561bd2bd5]) * ambari-web/app/styles/application.less > Hosts filter: placeholder text is too prominent > --- > > Key: AMBARI-15546 > URL: https://issues.apache.org/jira/browse/AMBARI-15546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15546.patch > > > Placeholder text is too prominent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15431) Atlas Integration : Rename Atlas Configurations
[
https://issues.apache.org/jira/browse/AMBARI-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209758#comment-15209758
]
Hudson commented on AMBARI-15431:
-
FAILURE: Integrated in Ambari-trunk-Commit #4536 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4536/])
AMBARI-15431 - Atlas Integration : Rename Atlas Configurations - fix for
(tbeerbower:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c5c5da75af617637ea91a29528ac9cc8f6113ab1])
* ambari-server/src/test/python/stacks/2.6/configs/default.json
* ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/metainfo.xml
*
ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/configuration/atlas-env.xml
* ambari-server/src/test/python/stacks/2.5/configs/default.json
*
ambari-server/src/main/resources/stacks/HDP/2.6/services/ATLAS/configuration/atlas-env.xml
* ambari-server/src/test/python/stacks/2.5/ATLAS/test_atlas_server.py
* ambari-server/src/main/resources/stacks/HDP/2.5/services/ATLAS/metainfo.xml
* ambari-server/src/test/python/stacks/2.6/ATLAS/test_atlas_server.py
> Atlas Integration : Rename Atlas Configurations
> ---
>
> Key: AMBARI-15431
> URL: https://issues.apache.org/jira/browse/AMBARI-15431
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-15431-2.patch, AMBARI-15431.patch
>
>
> Atlas configuration name {{application.properties}} has been changed to
> {{atlas-application.properties}} to avoid name conflicts with other services.
> See https://issues.apache.org/jira/browse/ATLAS-392.
> Ambari scripts for Atlas currently use the configuration name
> {{application.properties}} for all stack levels. Stacks which include Atlas
> > 0.5 should use the configuration name {{atlas-application.properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15539) YARN Queue should be refreshed when enabling/disabling Interactive Query
[ https://issues.apache.org/jira/browse/AMBARI-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209759#comment-15209759 ] Hudson commented on AMBARI-15539: - FAILURE: Integrated in Ambari-trunk-Commit #4536 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4536/]) AMBARI-15539. YARN Queue should be refreshed when enabling/disabling (jaimin: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1fbf7f15d9d25ef592bca07fd11d7b63b3b48b0f]) * ambari-web/app/mixins/main/service/configs/component_actions_by_configs.js > YARN Queue should be refreshed when enabling/disabling Interactive Query > > > Key: AMBARI-15539 > URL: https://issues.apache.org/jira/browse/AMBARI-15539 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-15539.patch > > > Capacity scheduler will be changed as part of saving Hive configs related to > adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed > before issuing Hive Interactive Server Start/Delete command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15524) HAWQ - exchange keys should be done only from HAWQMASTER
[ https://issues.apache.org/jira/browse/AMBARI-15524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-15524: Attachment: AMBARI-15524-branch-2.2.patch > HAWQ - exchange keys should be done only from HAWQMASTER > > > Key: AMBARI-15524 > URL: https://issues.apache.org/jira/browse/AMBARI-15524 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0, 2.2.0 > > Attachments: AMBARI-15524-1.patch, AMBARI-15524-branch-2.2.patch, > AMBARI-15524.patch > > > HAWQ - exchange keys should be done only from HAWQMASTER. Currently, both > standby and master does exchange keys however, its not required be done twice -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15540) NAMENODE critical alert is present [Percentage standard deviation] after upgrade from 2.0.2/ 2.2.1.0 etc to 2.2.2.0 and disabling security
[
https://issues.apache.org/jira/browse/AMBARI-15540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209614#comment-15209614
]
Hudson commented on AMBARI-15540:
-
SUCCESS: Integrated in Ambari-branch-2.2 #549 (See
[https://builds.apache.org/job/Ambari-branch-2.2/549/])
AMBARI-15540 : NAMENODE critical alert is present [Percentage standard
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c313536a9367e39f6e0819b4b40d0bd04d2d00bd])
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
> NAMENODE critical alert is present [Percentage standard deviation] after
> upgrade from 2.0.2/ 2.2.1.0 etc to 2.2.2.0 and disabling security
> --
>
> Key: AMBARI-15540
> URL: https://issues.apache.org/jira/browse/AMBARI-15540
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15540.patch
>
>
> STR:
> 1)Deploy old version
> 2)Enable Mit security
> 3)Make Ambari only Upgrade
> 4)Disable security
> 5)Enable NN, RM HA
> 6)Enable/Disable security
> 7) Check Alerts for HDFS
> *Issue was absent for*
> {code}
> 2.2.2.0-285
> 2b1e7b75d1970f26b0a033cdfac8b53b457b83ff
> {code}
> *Actual result:*
> NAMENODE critical alert is present [Percentage standard deviation] after
> upgrade from 2.0.2/ 2.2.1.0 etc to 2.2.2.0 and disabling security
> {code}
> {
> "href" : "https://<>:8443/api/v1/clusters/cl1/alerts/201",
> "Alert" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "definition_id" : 102,
> "definition_name" : "namenode_client_rpc_processing_latency_daily",
> "host_name" : "<>",
> "id" : 201,
> "instance" : null,
> "label" : "NameNode Client RPC Processing Latency (Daily)",
> "latest_timestamp" : 1458643485805,
> "maintenance_state" : "OFF",
> "original_timestamp" : 1458643485805,
> "scope" : "ANY",
> "service_name" : "HDFS",
> "state" : "CRITICAL",
> "text" : "CRITICAL. Percentage standard deviation value 218.17% is
> beyond the critical threshold of 200.00%"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15487) Add support for ECS stack
[ https://issues.apache.org/jira/browse/AMBARI-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-15487: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Add support for ECS stack > - > > Key: AMBARI-15487 > URL: https://issues.apache.org/jira/browse/AMBARI-15487 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Sumit Mohanty >Assignee: Vijay Srinivasaraghavan > Fix For: 2.2.2 > > Attachments: Ambari-15487-branch-2.2.patch, > Ambari-15487-branch-2.2.patch.2, Ambari-15487-branch-2.2.patch.3 > > > Add support for ECS stack. This is to track cherry-picking changes related to > adding ECS stack support to branch 2.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15552) Role selection in List view of Manage Ambari page does not work correctly
[
https://issues.apache.org/jira/browse/AMBARI-15552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keta Patel updated AMBARI-15552:
Description:
Reproduction Steps:
1. Go to Admin->Manage Ambari
2. Create a group with a few users belonging to it.
(I have created "mygroup" with "user1", "user2", "user3")
(attachments "user1.tiff", "mygroup.tiff" shows samples)
3. Go to Clusters->Roles on the left navigation menu.
4. The default view is the "Block" view for the roles. Assign "mygroup" a role,
say "Cluster User".
(attachment "block_view_original.tiff")
5. Click on "List" view, it will show Users by default. It correctly shows the
role "Cluster User" for each user in "mygroup".
(attachment "list_view_users.tiff")
6. Now, try adding a new Role, say "Service Operator", to one of the users, say
"user3".
(attachments "list_view_add_role_to_user_step1.tiff",
"list_view_add_role_to_user_step2.tiff")
7. After making this change, the role gets added for that user (in our case
"user3"), but the roles from other users in its group gets removed.
Also, the previous role for the user ("user3") is replaced by the new Role.
(attachment "list_view_add_role_to_user_step3.tiff")
8. You can confirm this from the the "Block" view.
(attachment "block_view_after_step3.tiff")
So, the problem here lies with the List view where it is not able to process
the changes in the Roles correctly.
There is no provision to add a role. Any change in the Roles of the User from
the List view only replaces the role that was displayed in the selection box
while also removing all the Roles for the remaining users in its group.
Expected results:
1. The selection box must be able to show all the selected Roles for
Users/Groups.
2. Adding a Role must not replace existing Role of the user.
3. Adding a Role to a user must not affect the Roles of other users in its
group.
4. Multiple Role selection must be allowed from the selection box in the List
view.
was:
Reproduction Steps:
1. Go to Admin->Manage Ambari
2. Create a group with a few users belonging to it. (I have created "mygroup"
with "user1", "user2", "user3") (attachments "user1.tiff", "mygroup.tiff" shows
samples)
3. Go to Clusters->Roles on the left navigation menu.
4. The default view is the "Block" view for the roles. Assign "mygroup" a role,
say "Cluster User". (attachment "block_view_original.tiff")
5. Click on "List" view, it will show Users by default. It correctly shows the
role "Cluster User" for each user in "mygroup". (attachment
"list_view_users.tiff")
6. Now, try adding a new Role, say "Service Operator", to one of the users, say
"user3". (attachments "list_view_add_role_to_user_step1.tiff",
"list_view_add_role_to_user_step2.tiff")
7. After making this change, the role gets added for that user (in our case
"user3"), but the roles from other users in its group gets removed. (attachment
"list_view_add_role_to_user_step3.tiff")
8. You can confirm this from the the "Block" view. (attachment
"block_view_after_step3.tiff")
So, the problem here lies with the List view where it is not able to process
the changes in the Roles correctly.
There is no provision to add a role. Any change in the Roles of the User from
the List view only replaces the role that was displayed in the selection box
while also removing all the Roles for the remaining users in its group.
Expected results:
1. The selection box must be able to show all the selected Roles for
Users/Groups.
2. Adding a Role must not replace existing Role of the user.
3. Adding a Role to a user must not affect the Roles of other users in its
group.
4. Multiple Role selection must be allowed from the selection box in the List
view.
> Role selection in List view of Manage Ambari page does not work correctly
> -
>
> Key: AMBARI-15552
> URL: https://issues.apache.org/jira/browse/AMBARI-15552
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: block_view_after_step3.tiff, block_view_original.tiff,
> list_view_add_role_to_user_step1.tiff, list_view_add_role_to_user_step2.tiff,
> list_view_add_role_to_user_step3.tiff, list_view_users.tiff, mygroup.tiff,
> user1.tiff
>
>
> Reproduction Steps:
> 1. Go to Admin->Manage Ambari
> 2. Create a group with a few users belonging to it.
> (I have created "mygroup" with "user1", "user2", "user3")
> (attachments "user1.tiff", "mygroup.tiff" shows samples)
> 3. Go to Clusters->Roles on the left navigation menu.
> 4. The default view is the "Block" view for the roles. Assign "mygroup" a
> role, say "Cluster User".
> (attachment "block_view_original.tiff")
> 5. Click on "List" view, it will show Users by default. It
[jira] [Updated] (AMBARI-15552) Role selection in List view of Manage Ambari page does not work correctly
[ https://issues.apache.org/jira/browse/AMBARI-15552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keta Patel updated AMBARI-15552: Attachment: block_view_after_step3.tiff block_view_original.tiff list_view_add_role_to_user_step1.tiff list_view_add_role_to_user_step2.tiff list_view_add_role_to_user_step3.tiff list_view_users.tiff mygroup.tiff user1.tiff > Role selection in List view of Manage Ambari page does not work correctly > - > > Key: AMBARI-15552 > URL: https://issues.apache.org/jira/browse/AMBARI-15552 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Reporter: Keta Patel >Assignee: Keta Patel > Attachments: block_view_after_step3.tiff, block_view_original.tiff, > list_view_add_role_to_user_step1.tiff, list_view_add_role_to_user_step2.tiff, > list_view_add_role_to_user_step3.tiff, list_view_users.tiff, mygroup.tiff, > user1.tiff > > > Reproduction Steps: > 1. Go to Admin->Manage Ambari > 2. Create a group with a few users belonging to it. (I have created "mygroup" > with "user1", "user2", "user3") (attachments "user1.tiff", "mygroup.tiff" > shows samples) > 3. Go to Clusters->Roles on the left navigation menu. > 4. The default view is the "Block" view for the roles. Assign "mygroup" a > role, say "Cluster User". (attachment "block_view_original.tiff") > 5. Click on "List" view, it will show Users by default. It correctly shows > the role "Cluster User" for each user in "mygroup". (attachment > "list_view_users.tiff") > 6. Now, try adding a new Role, say "Service Operator", to one of the users, > say "user3". (attachments "list_view_add_role_to_user_step1.tiff", > "list_view_add_role_to_user_step2.tiff") > 7. After making this change, the role gets added for that user (in our case > "user3"), but the roles from other users in its group gets removed. > (attachment "list_view_add_role_to_user_step3.tiff") > 8. You can confirm this from the the "Block" view. (attachment > "block_view_after_step3.tiff") > So, the problem here lies with the List view where it is not able to process > the changes in the Roles correctly. > There is no provision to add a role. Any change in the Roles of the User from > the List view only replaces the role that was displayed in the selection box > while also removing all the Roles for the remaining users in its group. > Expected results: > 1. The selection box must be able to show all the selected Roles for > Users/Groups. > 2. Adding a Role must not replace existing Role of the user. > 3. Adding a Role to a user must not affect the Roles of other users in its > group. > 4. Multiple Role selection must be allowed from the selection box in the List > view. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15546) Hosts filter: placeholder text is too prominent
[ https://issues.apache.org/jira/browse/AMBARI-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-15546: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Hosts filter: placeholder text is too prominent > --- > > Key: AMBARI-15546 > URL: https://issues.apache.org/jira/browse/AMBARI-15546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15546.patch > > > Placeholder text is too prominent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15551) When saving repository changes, confirm dialog shows message key instead of actual message
Sangeeta Ravindran created AMBARI-15551: --- Summary: When saving repository changes, confirm dialog shows message key instead of actual message Key: AMBARI-15551 URL: https://issues.apache.org/jira/browse/AMBARI-15551 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: trunk Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor Fix For: trunk Click on Versions in the Ambari Admin view. Click on the Repository version. Delete a repository or edit the url for it. Click on Save. A confirming dialog pops up with the following message: versions.changeBaseURLConfirmationTip.message -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15550) PXF should use hostname instead of localhost in pxf urls
[ https://issues.apache.org/jira/browse/AMBARI-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-15550: Attachment: AMBARI-15550.patch > PXF should use hostname instead of localhost in pxf urls > > > Key: AMBARI-15550 > URL: https://issues.apache.org/jira/browse/AMBARI-15550 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.0 >Reporter: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.3.0, 2.2.0 > > Attachments: AMBARI-15550.patch > > > PXF should use actual hostname instead of localhost in pxf urls. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15550) PXF should use hostname instead of localhost in pxf urls
bhuvnesh chaudhary created AMBARI-15550: --- Summary: PXF should use hostname instead of localhost in pxf urls Key: AMBARI-15550 URL: https://issues.apache.org/jira/browse/AMBARI-15550 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: trunk, 2.2.0 Reporter: bhuvnesh chaudhary Priority: Minor Attachments: AMBARI-15550.patch PXF should use actual hostname instead of localhost in pxf urls. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15550) PXF should use hostname instead of localhost in pxf urls
[ https://issues.apache.org/jira/browse/AMBARI-15550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bhuvnesh chaudhary updated AMBARI-15550: Fix Version/s: 2.2.0 2.3.0 > PXF should use hostname instead of localhost in pxf urls > > > Key: AMBARI-15550 > URL: https://issues.apache.org/jira/browse/AMBARI-15550 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk, 2.2.0 >Reporter: bhuvnesh chaudhary >Priority: Minor > Fix For: 2.3.0, 2.2.0 > > Attachments: AMBARI-15550.patch > > > PXF should use actual hostname instead of localhost in pxf urls. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15548) Add OS button on Edit repository version page shows extra space when no repositories have been selected for removal
[ https://issues.apache.org/jira/browse/AMBARI-15548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-15548: Status: Patch Available (was: In Progress) > Add OS button on Edit repository version page shows extra space when no > repositories have been selected for removal > --- > > Key: AMBARI-15548 > URL: https://issues.apache.org/jira/browse/AMBARI-15548 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-15548.patch, AddOSExtraSpace.jpg > > > Click on Versions in the Ambari Admin view. > Click on the Repository version. > Under repositories, click on + Add OS dropdown. > Since no repositories are removed yet, an empty drop-down is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15549) Delete service: Unable to delete a service even when it's host components are in a removable state.
Nahappan Somasundaram created AMBARI-15549: -- Summary: Delete service: Unable to delete a service even when it's host components are in a removable state. Key: AMBARI-15549 URL: https://issues.apache.org/jira/browse/AMBARI-15549 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Fix For: 2.4.0 It is possible for a cluster to get in a state where # desired state of a host component was in INSTALLED state # desired state of a service component is in STARTED state # Delete service API fails with the error message of the component being in non-removable state (STARTED). *Expected behavior:* If all host components have their desired state in INSTALLED then deletion of a service should succeed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15137) Parameterize distro-specific stack information for TEZ
[ https://issues.apache.org/jira/browse/AMBARI-15137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-15137: --- Attachment: AMBARI-15137.patch > Parameterize distro-specific stack information for TEZ > -- > > Key: AMBARI-15137 > URL: https://issues.apache.org/jira/browse/AMBARI-15137 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Affects Versions: 2.1.0, 2.2.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: > 0006-AMBARI-15137-Parameterize-distro-specific-stack-info.patch, > AMBARI-15137.patch > > > Apply the prototype detailed on AMBARI-13364 to TEZ . > Tokens such as: current version, upgrade version, stack name, install > path..., will be parameterized and distro-agnostic at common-service > definition level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15137) Parameterize distro-specific stack information for TEZ
[ https://issues.apache.org/jira/browse/AMBARI-15137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-15137: --- Attachment: (was: AMBARI-15137.patch) > Parameterize distro-specific stack information for TEZ > -- > > Key: AMBARI-15137 > URL: https://issues.apache.org/jira/browse/AMBARI-15137 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Affects Versions: 2.1.0, 2.2.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: > 0006-AMBARI-15137-Parameterize-distro-specific-stack-info.patch > > > Apply the prototype detailed on AMBARI-13364 to TEZ . > Tokens such as: current version, upgrade version, stack name, install > path..., will be parameterized and distro-agnostic at common-service > definition level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15389) Intermittent YARN service check failures during and post EU
[
https://issues.apache.org/jira/browse/AMBARI-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209454#comment-15209454
]
Hudson commented on AMBARI-15389:
-
FAILURE: Integrated in Ambari-trunk-Commit #4535 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4535/])
AMBARI-15389. Intermittent YARN service check failures during and post
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7213fda8d2e7de435592b6180d7d13282500ffa6])
*
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py
> Intermittent YARN service check failures during and post EU
> ---
>
> Key: AMBARI-15389
> URL: https://issues.apache.org/jira/browse/AMBARI-15389
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.2
>
> Attachments: AMBARI-15389.patch
>
>
> Build # - Ambari 2.2.1.1 - #63
> Observed this issue in a couple of EU runs recently where YARN service check
> reports failure
> a. In one test, the EU ran from HDP 2.3.4.0 to 2.4.0.0 and YARN service check
> reported failure during EU itself; a retry of the operation led to service
> check being successful
> b. In another test post EU when YARN service check was run, it reported
> failure; afterwards when I ran it again - success
> Looks like there is some corner condition which causes this issue to be hit
> {code}
> stderr: /var/lib/ambari-agent/data/errors-822.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
> line 142, in
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
> line 104, in service_check
> user=params.smokeuser,
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari...@example.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar'
> returned 2. Hortonworks #
> This is MOTD message, added for testing in qe infra
> 16/03/03 02:33:51 INFO impl.TimelineClientImpl: Timeline service address:
> http://host:8188/ws/v1/timeline/
> 16/03/03 02:33:51 INFO distributedshell.Client: Initializing Client
> 16/03/03 02:33:51 INFO distributedshell.Client: Running Client
> 16/03/03 02:33:51 INFO client.RMProxy: Connecting to ResourceManager at
> host-9-5.test/127.0.0.254:8050
> 16/03/03 02:33:53 INFO distributedshell.Client: Got Cluster metric info from
> ASM, numNodeManagers=3
> 16/03/03 02:33:53 INFO distributedshell.Client: Got Cluster node info from ASM
> 16/03/03 02:33:53 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=host:25454, nodeAddresshost:8042, nodeRackName/default-rack,
> nodeNumContainers1
> 16/03/03 02:33:53 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=host-9-5.test:25454, nodeAddresshost-9-5.test:8042,
> nodeRackName/default-rack, nodeNumContainers0
> 16/03/03 02:33:53 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=host-9-1.test:25454, nodeAddresshost-9-1.test:8042,
> nodeRackName/default-rack, nodeNumContainers0
> 16/03/03 02:33:53 INFO distributedshell.Client: Queue info,
> queueName=default, queueCurrentCapacity=0.08336, queueMaxCapacity=1.0,
> queueApplicationCount=0, queueChildQueueCount=0
> 16/03/03 02:33:53 INFO distributedshell.Client: User ACL Info for Queue,
> queueName=root, userAcl=SUBMIT_APPLICATIONS
> 16/03/03 02:33:53 INFO distributedshell.Client: User ACL Info for Queue,
> queueName=default, userAcl=SUBMIT_APPLICATIONS
> 16/03/03 02:33:53 INFO distributedshell.Client: Max mem capabililty of
> resources in this cluster 10240
> 16/03/03 02:33:53 INFO distributedshell.Client: Max virtual cores capabililty
> of resources in this cluster 1
> 16/03/03 02:33:53 INFO
[jira] [Commented] (AMBARI-15533) HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
[
https://issues.apache.org/jira/browse/AMBARI-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209452#comment-15209452
]
Hudson commented on AMBARI-15533:
-
FAILURE: Integrated in Ambari-trunk-Commit #4535 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4535/])
AMBARI-15533 - HDFS Alerts for AMS Throw 'invalid literal for int() with
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f90d0beaeb3e22da5245710b1cdfc49bf24f08c9])
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
> HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
> --
>
> Key: AMBARI-15533
> URL: https://issues.apache.org/jira/browse/AMBARI-15533
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15533.patch
>
>
> SCRIPT alerts stuck in UNKNWN status with response message 'invalid literal
> for int() with base 10: '50.0''.
> It is noticed that the error is thrown only after a PUT alertDefinition call
> to update few parameters of alert definition since the numeric values are
> changed into strings.
> The scripts need to safely cast their parameters; the fix is in the script
> here.
> E.g PUT Request :
> {noformat}
> PUT http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "name" : "mergeHaMetrics",
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "value" : "false",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "type" : "STRING"
> },
> {
> "name" : "interval",
> "display_name" : "Time interval in minutes",
> "value" : 1441.0,
> "description" : "Time interval in minutes.",
> "type" : "NUMERIC"
> },
> {
> "name" : "appId",
> "display_name" : "AMS application id",
> "value" : "NAMENODE",
> "description" : "The application id used to retrieve the metric.",
> "type" : "STRING"
> },
> {
> "name" : "metricName",
> "display_name" : "Metric Name",
> "value" : "jvm.JvmMetrics.MemHeapUsedM",
> "description" : "The metric to monitor.",
> "type" : "STRING"
> },
> {
> "name" : "metric.deviation.warning.threshold",
> "display_name" : "The standard deviation threshold above which a
> warning is produced.",
> "units" : "%",
> "value" : 20.0,
> "type" : "PERCENT",
> "threshold" : "WARNING"
> },
> {
> "name" : "metric.deviation.critical.threshold",
> "display_name" : "The standard deviation threshold above which a
> critical alert is produced.",
> "units" : "%",
> "value" : 50.0,
> "type" : "PERCENT",
> "threshold" : "CRITICAL"
> }
> ],
> "path" : "HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py",
> "type" : "SCRIPT"
> }
> }
> }
> {noformat}
> Response :200OK
> {noformat}
> GET http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "href" :
> "http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38;,
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "description" : "Whether active and stanby NameNodes metrics should
[jira] [Commented] (AMBARI-15535) Permission on metrics-grafana.ini should be 600 to protect password
[ https://issues.apache.org/jira/browse/AMBARI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209450#comment-15209450 ] Hudson commented on AMBARI-15535: - FAILURE: Integrated in Ambari-trunk-Commit #4535 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4535/]) AMBARI-15535 : Permission on metrics-grafana.ini should be 600 to (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1744996ce5faeeb9dd5913b161a35eff430a796d]) * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py * ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py > Permission on metrics-grafana.ini should be 600 to protect password > --- > > Key: AMBARI-15535 > URL: https://issues.apache.org/jira/browse/AMBARI-15535 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15535.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15547) User names in the List view of Roles are displayed with URI encoding
[ https://issues.apache.org/jira/browse/AMBARI-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keta Patel updated AMBARI-15547: Attachment: AMBARI-15547.patch > User names in the List view of Roles are displayed with URI encoding > > > Key: AMBARI-15547 > URL: https://issues.apache.org/jira/browse/AMBARI-15547 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > Attachments: AMBARI-15547.patch, names with No URI encoding.tiff, > names with URI encoding.tiff > > > Under the List view of Roles, the name of Users with special characters, like > '@', are displayed with URI encoding. (see attachment "names with URI > encoding.tiff") > The names should be displayed without any encoding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15547) User names in the List view of Roles are displayed with URI encoding
[ https://issues.apache.org/jira/browse/AMBARI-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209420#comment-15209420 ] Keta Patel commented on AMBARI-15547: - The fix for this issue is to replace the displayed name with the correct name attribute, which is not URI encoded. This attribute is already present in the User's object. The attachment "names with No URI encoding.tiff" shows the corrected User names. > User names in the List view of Roles are displayed with URI encoding > > > Key: AMBARI-15547 > URL: https://issues.apache.org/jira/browse/AMBARI-15547 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > Attachments: names with No URI encoding.tiff, names with URI > encoding.tiff > > > Under the List view of Roles, the name of Users with special characters, like > '@', are displayed with URI encoding. (see attachment "names with URI > encoding.tiff") > The names should be displayed without any encoding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15547) User names in the List view of Roles are displayed with URI encoding
[ https://issues.apache.org/jira/browse/AMBARI-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keta Patel updated AMBARI-15547: Attachment: names with No URI encoding.tiff names with URI encoding.tiff > User names in the List view of Roles are displayed with URI encoding > > > Key: AMBARI-15547 > URL: https://issues.apache.org/jira/browse/AMBARI-15547 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > Attachments: names with No URI encoding.tiff, names with URI > encoding.tiff > > > Under the List view of Roles, the name of Users with special characters, like > '@', are displayed with URI encoding. (see attachment "names with URI > encoding.tiff") > The names should be displayed without any encoding. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15546) Hosts filter: placeholder text is too prominent
[ https://issues.apache.org/jira/browse/AMBARI-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209403#comment-15209403 ] Xi Wang commented on AMBARI-15546: -- +1 for patch > Hosts filter: placeholder text is too prominent > --- > > Key: AMBARI-15546 > URL: https://issues.apache.org/jira/browse/AMBARI-15546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15546.patch > > > Placeholder text is too prominent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15546) Hosts filter: placeholder text is too prominent
[ https://issues.apache.org/jira/browse/AMBARI-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-15546: -- Attachment: AMBARI-15546.patch > Hosts filter: placeholder text is too prominent > --- > > Key: AMBARI-15546 > URL: https://issues.apache.org/jira/browse/AMBARI-15546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15546.patch > > > Placeholder text is too prominent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15546) Hosts filter: placeholder text is too prominent
[ https://issues.apache.org/jira/browse/AMBARI-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-15546: -- Status: Patch Available (was: Open) > Hosts filter: placeholder text is too prominent > --- > > Key: AMBARI-15546 > URL: https://issues.apache.org/jira/browse/AMBARI-15546 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.4.0 > > Attachments: AMBARI-15546.patch > > > Placeholder text is too prominent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15546) Hosts filter: placeholder text is too prominent
Richard Zang created AMBARI-15546: - Summary: Hosts filter: placeholder text is too prominent Key: AMBARI-15546 URL: https://issues.apache.org/jira/browse/AMBARI-15546 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.4.0 Placeholder text is too prominent -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15431) Atlas Integration : Rename Atlas Configurations
[
https://issues.apache.org/jira/browse/AMBARI-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-15431:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Atlas Integration : Rename Atlas Configurations
> ---
>
> Key: AMBARI-15431
> URL: https://issues.apache.org/jira/browse/AMBARI-15431
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-15431-2.patch, AMBARI-15431.patch
>
>
> Atlas configuration name {{application.properties}} has been changed to
> {{atlas-application.properties}} to avoid name conflicts with other services.
> See https://issues.apache.org/jira/browse/ATLAS-392.
> Ambari scripts for Atlas currently use the configuration name
> {{application.properties}} for all stack levels. Stacks which include Atlas
> > 0.5 should use the configuration name {{atlas-application.properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Attachment: AMBARI-15412-trunk.patch Modified trunk to address the issue. > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-15412-trunk.patch, AMBARI-15412.patch, > AMBARI-15412_branch-2.2.patch, AMBARI-15412_output.png, trunk-output.png > > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Attachment: trunk-output.png Modified output on trunk > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-15412.patch, AMBARI-15412_branch-2.2.patch, > AMBARI-15412_output.png, trunk-output.png > > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[ https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-15412: --- Status: Open (was: Patch Available) > Improve error logging for install errors during blueprint deployments > - > > Key: AMBARI-15412 > URL: https://issues.apache.org/jira/browse/AMBARI-15412 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-15412.patch, AMBARI-15412_branch-2.2.patch, > AMBARI-15412_output.png > > > Improve error logging for install errors during blueprint deployment. > Currently a severe error during install of a service component gets logged as > a WARNing. > E.g.: > 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 - > Operation failed - may be retried. Service component host: KAFKA_BROKER, > host: hdtest159.svl.ibm.com Action id12-0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15544) Creating multi-node cluster using Blueprints fails.
[
https://issues.apache.org/jira/browse/AMBARI-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-15544:
---
Status: Patch Available (was: In Progress)
> Creating multi-node cluster using Blueprints fails.
> ---
>
> Key: AMBARI-15544
> URL: https://issues.apache.org/jira/browse/AMBARI-15544
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: rb45253.patch
>
>
> Provisioning multinode cluster using Blueprints fails as Ambari sends install
> and start tasks only to a single node (agent) but not to nodes.
> Apparently this is being caused by an NPE thrown from
> RecoveryConfigHelper.java: 146
> Long timestamp = hostTimestamp.get(hostname);
> if (timestamp.longValue() != recoveryTimestamp) {
> return true;
> }
> for all agents except one. Due to the NPE the server never gets to execute
> the code that adds the commands to be executed by the agent to the heartbeat
> response for the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15544) Creating multi-node cluster using Blueprints fails.
[
https://issues.apache.org/jira/browse/AMBARI-15544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-15544:
---
Attachment: rb45253.patch
> Creating multi-node cluster using Blueprints fails.
> ---
>
> Key: AMBARI-15544
> URL: https://issues.apache.org/jira/browse/AMBARI-15544
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
>Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: rb45253.patch
>
>
> Provisioning multinode cluster using Blueprints fails as Ambari sends install
> and start tasks only to a single node (agent) but not to nodes.
> Apparently this is being caused by an NPE thrown from
> RecoveryConfigHelper.java: 146
> Long timestamp = hostTimestamp.get(hostname);
> if (timestamp.longValue() != recoveryTimestamp) {
> return true;
> }
> for all agents except one. Due to the NPE the server never gets to execute
> the code that adds the commands to be executed by the agent to the heartbeat
> response for the agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15539) YARN Queue should be refreshed when enabling/disabling Interactive Query
[ https://issues.apache.org/jira/browse/AMBARI-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-15539: Status: Patch Available (was: Open) Tested the patch on a cluster. Verified that all ambari-web unit tests passes with the patch: 24653 tests complete (24 seconds) 145 tests pending > YARN Queue should be refreshed when enabling/disabling Interactive Query > > > Key: AMBARI-15539 > URL: https://issues.apache.org/jira/browse/AMBARI-15539 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-15539.patch > > > Capacity scheduler will be changed as part of saving Hive configs related to > adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed > before issuing Hive Interactive Server Start/Delete command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15545) ALERTS for yarn_resourcemanager_webui do not work in HA+SSL enabled environment.
Armando Paniagua created AMBARI-15545:
-
Summary: ALERTS for yarn_resourcemanager_webui do not work in
HA+SSL enabled environment.
Key: AMBARI-15545
URL: https://issues.apache.org/jira/browse/AMBARI-15545
Project: Ambari
Issue Type: Bug
Components: alerts
Affects Versions: 2.1.0
Reporter: Armando Paniagua
ALERTS for yarn_resourcemanager_webui do not work in HA+SSL enabled
environment.
After you enable Resourcemanager HA+SSL through Ambari, the Alert shows
Critical for yarn_resourcemanager_webui because the Alert is doing a service
check on the wrong URI property.
If you look at that Alert definition (YARN/alerts.json) you can see the URI
describes different yarn-site attributes for non-ssl (http), ssl (https) and
high availability. But even after correctly enabling SSL and HA for yarn the
Alert for this service still looks at the non-ssl/non-HA attribute:
yarn-site/yarn.resourcemanager.webapp.address
Of course the service check rightfully fails since the resourcemanager webui
service is using a different service property which is the high availability
https attribute.
I did not see any other similar JIRA reported so I'm wondering if this is a
known problem?
"RESOURCEMANAGER": [
{
"name": "yarn_resourcemanager_webui",
"label": "ResourceManager Web UI",
"description": "This host-level alert is triggered if the
ResourceManager Web UI is unreachable.",
"interval": 1,
"scope": "ANY",
"source": {
"type": "WEB",
"uri": {
"http": "{{yarn-site/yarn.resourcemanager.webapp.address}}",
"https": "{{yarn-site/yarn.resourcemanager.webapp.https.address}}",
"https_property": "{{yarn-site/yarn.http.policy}}",
"https_property_value": "HTTPS_ONLY",
"kerberos_keytab":
"{{yarn-site/yarn.resourcemanager.webapp.spnego-keytab-file}}",
"kerberos_principal":
"{{yarn-site/yarn.resourcemanager.webapp.spnego-principal}}",
"high_availability": {
"alias_key" : "{{yarn-site/yarn.resourcemanager.ha.rm-ids}}",
"http_pattern" :
"{{yarn-site/yarn.resourcemanager.webapp.address.{{alias",
"https_pattern" :
"{{yarn-site/yarn.resourcemanager.webapp.https.address.{{alias"
}
},
"reporting": {
"ok": {
"text": "HTTP {0} response in {2:.3f}s"
},
"warning":{
"text": "HTTP {0} response from {1} in {2:.3f}s ({3})"
},
"critical": {
"text": "Connection failed to {1} ({3})"
}
}
}
}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15520) Add more warning on Pause button saying no topology changes.
[ https://issues.apache.org/jira/browse/AMBARI-15520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209307#comment-15209307 ] Hudson commented on AMBARI-15520: - SUCCESS: Integrated in Ambari-branch-2.2 #548 (See [https://builds.apache.org/job/Ambari-branch-2.2/548/]) Summary:AMBARI-15520 Add more warning on Pause button saying no topology (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cb193cc276418655f5eb218968b9597b81ff44aa]) * ambari-web/app/messages.js > Add more warning on Pause button saying no topology changes. > > > Key: AMBARI-15520 > URL: https://issues.apache.org/jira/browse/AMBARI-15520 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.2.2 > > Attachments: AMBARI-15520_branch-2.2.v0.patch, > AMBARI-15520_trunk.v0.patch, AMBARI-15520_trunk.v1.patch > > > Add more warning on Pause button saying no topology changes. > Really need to warn folks on not making any add hosts/RM HA/others. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15533) HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
[
https://issues.apache.org/jira/browse/AMBARI-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209306#comment-15209306
]
Hudson commented on AMBARI-15533:
-
SUCCESS: Integrated in Ambari-branch-2.2 #548 (See
[https://builds.apache.org/job/Ambari-branch-2.2/548/])
AMBARI-15533 - HDFS Alerts for AMS Throw 'invalid literal for int() with
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f1efa3a5e1b64fa3eb66815ce3d40e9bd54aa4b0])
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py
> HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
> --
>
> Key: AMBARI-15533
> URL: https://issues.apache.org/jira/browse/AMBARI-15533
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15533.patch
>
>
> SCRIPT alerts stuck in UNKNWN status with response message 'invalid literal
> for int() with base 10: '50.0''.
> It is noticed that the error is thrown only after a PUT alertDefinition call
> to update few parameters of alert definition since the numeric values are
> changed into strings.
> The scripts need to safely cast their parameters; the fix is in the script
> here.
> E.g PUT Request :
> {noformat}
> PUT http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "name" : "mergeHaMetrics",
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "value" : "false",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "type" : "STRING"
> },
> {
> "name" : "interval",
> "display_name" : "Time interval in minutes",
> "value" : 1441.0,
> "description" : "Time interval in minutes.",
> "type" : "NUMERIC"
> },
> {
> "name" : "appId",
> "display_name" : "AMS application id",
> "value" : "NAMENODE",
> "description" : "The application id used to retrieve the metric.",
> "type" : "STRING"
> },
> {
> "name" : "metricName",
> "display_name" : "Metric Name",
> "value" : "jvm.JvmMetrics.MemHeapUsedM",
> "description" : "The metric to monitor.",
> "type" : "STRING"
> },
> {
> "name" : "metric.deviation.warning.threshold",
> "display_name" : "The standard deviation threshold above which a
> warning is produced.",
> "units" : "%",
> "value" : 20.0,
> "type" : "PERCENT",
> "threshold" : "WARNING"
> },
> {
> "name" : "metric.deviation.critical.threshold",
> "display_name" : "The standard deviation threshold above which a
> critical alert is produced.",
> "units" : "%",
> "value" : 50.0,
> "type" : "PERCENT",
> "threshold" : "CRITICAL"
> }
> ],
> "path" : "HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py",
> "type" : "SCRIPT"
> }
> }
> }
> {noformat}
> Response :200OK
> {noformat}
> GET http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "href" :
> "http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38;,
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "description" : "Whether active and stanby NameNodes metrics should
> be
[jira] [Updated] (AMBARI-15542) PXF service checks fails on secured cluster
[
https://issues.apache.org/jira/browse/AMBARI-15542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lav Jain updated AMBARI-15542:
--
Fix Version/s: 2.2.2
2.3.0
Status: Patch Available (was: Open)
> PXF service checks fails on secured cluster
> ---
>
> Key: AMBARI-15542
> URL: https://issues.apache.org/jira/browse/AMBARI-15542
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.1
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15542.branch22.patch, AMBARI-15542.patch
>
>
> PXF service checks fails on secured cluster branch-2.2
> {code}
> 2016-03-11 23:37:35,588 - HdfsResource[None] {'security_enabled': True,
> 'keytab': '/etc/security/keytabs/hdfs.headless.keytab', 'default_fs':
> 'hdfs://c6401.ambari.apache.org:8020', 'hdfs_site': ..., 'kinit_path_local':
> '/usr/bin/kinit', 'principal_name': 'hdfs-...@ambari.apache.org', 'user':
> 'hdfs', 'action': ['execute']}
> 2016-03-11 23:37:35,588 - Testing PXF HDFS read
> 2016-03-11 23:37:35,675 - Error code: 500
> 2016-03-11 23:37:35,675 - HDFS test Failed: Exception occurred in HDFS test:
> PXF data read failed: HTTP Error 500: Internal Server Error
> {code}
> Pxf log says
> {code}
> SEVERE: Servlet.service() for servlet [PXF REST Service] in context with path
> [/pxf] threw exception [java.io.IOException: Can't get Master Kerberos
> principal for use as renewer] with root cause
> java.io.IOException: Can't get Master Kerberos principal for use as renewer
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:116)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:100)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:80)
> at
> org.apache.hadoop.mapred.FileInputFormat.listStatus(FileInputFormat.java:206)
> at
> org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getSplits(HdfsDataFragmenter.java:108)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getFragments(HdfsDataFragmenter.java:69)
> at
> org.apache.hawq.pxf.service.rest.FragmenterResource.getFragments(FragmenterResource.java:84)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-15189) Set dfs.allow.truncate = True on HDFS during HAWQ install or add service
[ https://issues.apache.org/jira/browse/AMBARI-15189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain resolved AMBARI-15189. --- Resolution: Fixed > Set dfs.allow.truncate = True on HDFS during HAWQ install or add service > > > Key: AMBARI-15189 > URL: https://issues.apache.org/jira/browse/AMBARI-15189 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.2.0 >Reporter: Lav Jain >Assignee: Lav Jain > Fix For: 2.3.0, 2.2.2 > > Attachments: AMBARI-15189.branch22-2.patch, > AMBARI-15189.branch22.patch, AMBARI-15189.patch > > > Setting this param to True is Mandatory, otherwise, failed transactions in > HAWQ might generate too many small files and will impact performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15542) PXF service checks fails on secured cluster without YARN
[
https://issues.apache.org/jira/browse/AMBARI-15542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lav Jain updated AMBARI-15542:
--
Summary: PXF service checks fails on secured cluster without YARN (was:
PXF service checks fails on secured cluster)
> PXF service checks fails on secured cluster without YARN
>
>
> Key: AMBARI-15542
> URL: https://issues.apache.org/jira/browse/AMBARI-15542
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.1
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15542.branch22.patch, AMBARI-15542.patch
>
>
> PXF service checks fails on secured cluster branch-2.2
> {code}
> 2016-03-11 23:37:35,588 - HdfsResource[None] {'security_enabled': True,
> 'keytab': '/etc/security/keytabs/hdfs.headless.keytab', 'default_fs':
> 'hdfs://c6401.ambari.apache.org:8020', 'hdfs_site': ..., 'kinit_path_local':
> '/usr/bin/kinit', 'principal_name': 'hdfs-...@ambari.apache.org', 'user':
> 'hdfs', 'action': ['execute']}
> 2016-03-11 23:37:35,588 - Testing PXF HDFS read
> 2016-03-11 23:37:35,675 - Error code: 500
> 2016-03-11 23:37:35,675 - HDFS test Failed: Exception occurred in HDFS test:
> PXF data read failed: HTTP Error 500: Internal Server Error
> {code}
> Pxf log says
> {code}
> SEVERE: Servlet.service() for servlet [PXF REST Service] in context with path
> [/pxf] threw exception [java.io.IOException: Can't get Master Kerberos
> principal for use as renewer] with root cause
> java.io.IOException: Can't get Master Kerberos principal for use as renewer
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:116)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:100)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:80)
> at
> org.apache.hadoop.mapred.FileInputFormat.listStatus(FileInputFormat.java:206)
> at
> org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getSplits(HdfsDataFragmenter.java:108)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getFragments(HdfsDataFragmenter.java:69)
> at
> org.apache.hawq.pxf.service.rest.FragmenterResource.getFragments(FragmenterResource.java:84)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15536) HBASE start,Check ZooKeeper and other ones was failed after upgrade to ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
[
https://issues.apache.org/jira/browse/AMBARI-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209281#comment-15209281
]
Hadoop QA commented on AMBARI-15536:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12795038/AMBARI-15536.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5995//console
This message is automatically generated.
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> --
>
> Key: AMBARI-15536
> URL: https://issues.apache.org/jira/browse/AMBARI-15536
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.2.2
>
> Attachments: AMBARI-15536.patch
>
>
> STR: *Gateway* : http://host:8080/#/main/services/HBASE/summary - for 2.1.2
> 1)Deploy old version
> 2)Make Ambari only Upgrade
> Actual result:
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> {code}
> stderr: /var/lib/ambari-agent/data/errors-916.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 73, in
> ZookeeperServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 59, in service_check
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/zkSmoke.sh
> /usr/hdp/current/zookeeper-client/bin/zkCli.sh c-smoke
> /usr/hdp/current/zookeeper-client/conf 2181 False /usr/bin/kinit no_keytab
> no_principal /var/lib/ambari-agent/tmp/zkSmoke.out' returned 3.
> zk_node1=os-s11-3-usjyms-upg-sanity-202-1.test
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:703)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:363)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for
[jira] [Updated] (AMBARI-15542) PXF service checks fails on secured cluster
[
https://issues.apache.org/jira/browse/AMBARI-15542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lav Jain updated AMBARI-15542:
--
Attachment: AMBARI-15542.patch
> PXF service checks fails on secured cluster
> ---
>
> Key: AMBARI-15542
> URL: https://issues.apache.org/jira/browse/AMBARI-15542
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.1
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15542.branch22.patch, AMBARI-15542.patch
>
>
> PXF service checks fails on secured cluster branch-2.2
> {code}
> 2016-03-11 23:37:35,588 - HdfsResource[None] {'security_enabled': True,
> 'keytab': '/etc/security/keytabs/hdfs.headless.keytab', 'default_fs':
> 'hdfs://c6401.ambari.apache.org:8020', 'hdfs_site': ..., 'kinit_path_local':
> '/usr/bin/kinit', 'principal_name': 'hdfs-...@ambari.apache.org', 'user':
> 'hdfs', 'action': ['execute']}
> 2016-03-11 23:37:35,588 - Testing PXF HDFS read
> 2016-03-11 23:37:35,675 - Error code: 500
> 2016-03-11 23:37:35,675 - HDFS test Failed: Exception occurred in HDFS test:
> PXF data read failed: HTTP Error 500: Internal Server Error
> {code}
> Pxf log says
> {code}
> SEVERE: Servlet.service() for servlet [PXF REST Service] in context with path
> [/pxf] threw exception [java.io.IOException: Can't get Master Kerberos
> principal for use as renewer] with root cause
> java.io.IOException: Can't get Master Kerberos principal for use as renewer
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:116)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:100)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:80)
> at
> org.apache.hadoop.mapred.FileInputFormat.listStatus(FileInputFormat.java:206)
> at
> org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getSplits(HdfsDataFragmenter.java:108)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getFragments(HdfsDataFragmenter.java:69)
> at
> org.apache.hawq.pxf.service.rest.FragmenterResource.getFragments(FragmenterResource.java:84)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15542) PXF service checks fails on secured cluster
[
https://issues.apache.org/jira/browse/AMBARI-15542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lav Jain updated AMBARI-15542:
--
Attachment: AMBARI-15542.branch22.patch
> PXF service checks fails on secured cluster
> ---
>
> Key: AMBARI-15542
> URL: https://issues.apache.org/jira/browse/AMBARI-15542
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.1
>Reporter: Lav Jain
>Assignee: Lav Jain
> Fix For: 2.3.0, 2.2.2
>
> Attachments: AMBARI-15542.branch22.patch, AMBARI-15542.patch
>
>
> PXF service checks fails on secured cluster branch-2.2
> {code}
> 2016-03-11 23:37:35,588 - HdfsResource[None] {'security_enabled': True,
> 'keytab': '/etc/security/keytabs/hdfs.headless.keytab', 'default_fs':
> 'hdfs://c6401.ambari.apache.org:8020', 'hdfs_site': ..., 'kinit_path_local':
> '/usr/bin/kinit', 'principal_name': 'hdfs-...@ambari.apache.org', 'user':
> 'hdfs', 'action': ['execute']}
> 2016-03-11 23:37:35,588 - Testing PXF HDFS read
> 2016-03-11 23:37:35,675 - Error code: 500
> 2016-03-11 23:37:35,675 - HDFS test Failed: Exception occurred in HDFS test:
> PXF data read failed: HTTP Error 500: Internal Server Error
> {code}
> Pxf log says
> {code}
> SEVERE: Servlet.service() for servlet [PXF REST Service] in context with path
> [/pxf] threw exception [java.io.IOException: Can't get Master Kerberos
> principal for use as renewer] with root cause
> java.io.IOException: Can't get Master Kerberos principal for use as renewer
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:116)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:100)
> at
> org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:80)
> at
> org.apache.hadoop.mapred.FileInputFormat.listStatus(FileInputFormat.java:206)
> at
> org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getSplits(HdfsDataFragmenter.java:108)
> at
> org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getFragments(HdfsDataFragmenter.java:69)
> at
> org.apache.hawq.pxf.service.rest.FragmenterResource.getFragments(FragmenterResource.java:84)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209255#comment-15209255 ] Bolke de Bruin commented on AMBARI-6432: That's great news! Thanks > FreeIPA Support in Ambari > - > > Key: AMBARI-6432 > URL: https://issues.apache.org/jira/browse/AMBARI-6432 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: jay vyas >Assignee: Bolke de Bruin > Fix For: 2.4.0 > > Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, > AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, > AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, > AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, > AMBARI-6432.trunk.v6.patch, AMBARI-6432.trunk.v7.patch, > AMBARI-6432.trunk.v8.patch, ipa-patch-v0.5.patch > > > FreeIPA Is a powerful tool for unifying identity, kerberos credentials, > across a cluster. > A great value add for ambari would be to provide support for using FreeIPA to > kerberize services. This would allow for > 1) better HCFS interoperability, because first class GID/UID is critical for > certain file systems (GlusterFS, Lustre, and any other file system which uses > kernel / FUSE apis for determining identity) > 2) better enterprise interoperability. Because of the fact that FreeIPA > makes it easy to interop with different identity solutions (like active > directory), it would make ambari easier to adopt for various enterprises. > 3) broadens ambaris scope. Now ambari could also allow people to setup the > users of their clusters, and at least some of the security features of their > clusters, all from one interface (no more manual handling of TGTs and such - > it could all be done quite easily via the ambari UI which could make calls to > underlying FreeIPA clients). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209252#comment-15209252
]
Robert Levas commented on AMBARI-6432:
--
[~bolke].. I committed the patch to trunk
{noformat}
commit 476d87b70b42a58914c69c3ce8098531d9405e48
Author: Bolke de Bruin
Date: Wed Mar 23 17:55:01 2016 -0400
AMBARI-6432. FreeIPA Support in Ambari (Bolke de Bruin via rlevas)
{noformat}
You can resolve this JIRA and close your review.
> FreeIPA Support in Ambari
> -
>
> Key: AMBARI-6432
> URL: https://issues.apache.org/jira/browse/AMBARI-6432
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk
>Reporter: jay vyas
>Assignee: Bolke de Bruin
> Fix For: 2.4.0
>
> Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch,
> AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch,
> AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch,
> AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch,
> AMBARI-6432.trunk.v6.patch, AMBARI-6432.trunk.v7.patch,
> AMBARI-6432.trunk.v8.patch, ipa-patch-v0.5.patch
>
>
> FreeIPA Is a powerful tool for unifying identity, kerberos credentials,
> across a cluster.
> A great value add for ambari would be to provide support for using FreeIPA to
> kerberize services. This would allow for
> 1) better HCFS interoperability, because first class GID/UID is critical for
> certain file systems (GlusterFS, Lustre, and any other file system which uses
> kernel / FUSE apis for determining identity)
> 2) better enterprise interoperability. Because of the fact that FreeIPA
> makes it easy to interop with different identity solutions (like active
> directory), it would make ambari easier to adopt for various enterprises.
> 3) broadens ambaris scope. Now ambari could also allow people to setup the
> users of their clusters, and at least some of the security features of their
> clusters, all from one interface (no more manual handling of TGTs and such -
> it could all be done quite easily via the ambari UI which could make calls to
> underlying FreeIPA clients).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15543) RBAC based user access to view instances are not honoured
Robert Levas created AMBARI-15543: - Summary: RBAC based user access to view instances are not honoured Key: AMBARI-15543 URL: https://issues.apache.org/jira/browse/AMBARI-15543 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Robert Levas Assignee: Robert Levas Priority: Critical Fix For: 2.4.0 Problem: 1. Create a cluster 2. Create some view instances in amber 3. Create a local non-admin ambari user 4. Grant the newly created user access to one of the view instances Log-in with the non-admin user. The user should only see the view instances it has permission instead of all view instances. This seems to have been introduced by https://issues.apache.org/jira/browse/AMBARI-14194 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15542) PXF service checks fails on secured cluster
Lav Jain created AMBARI-15542:
-
Summary: PXF service checks fails on secured cluster
Key: AMBARI-15542
URL: https://issues.apache.org/jira/browse/AMBARI-15542
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk, 2.2.1
Reporter: Lav Jain
Assignee: Lav Jain
PXF service checks fails on secured cluster branch-2.2
{code}
2016-03-11 23:37:35,588 - HdfsResource[None] {'security_enabled': True,
'keytab': '/etc/security/keytabs/hdfs.headless.keytab', 'default_fs':
'hdfs://c6401.ambari.apache.org:8020', 'hdfs_site': ..., 'kinit_path_local':
'/usr/bin/kinit', 'principal_name': 'hdfs-...@ambari.apache.org', 'user':
'hdfs', 'action': ['execute']}
2016-03-11 23:37:35,588 - Testing PXF HDFS read
2016-03-11 23:37:35,675 - Error code: 500
2016-03-11 23:37:35,675 - HDFS test Failed: Exception occurred in HDFS test:
PXF data read failed: HTTP Error 500: Internal Server Error
{code}
Pxf log says
{code}
SEVERE: Servlet.service() for servlet [PXF REST Service] in context with path
[/pxf] threw exception [java.io.IOException: Can't get Master Kerberos
principal for use as renewer] with root cause
java.io.IOException: Can't get Master Kerberos principal for use as renewer
at
org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:116)
at
org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodesInternal(TokenCache.java:100)
at
org.apache.hadoop.mapreduce.security.TokenCache.obtainTokensForNamenodes(TokenCache.java:80)
at
org.apache.hadoop.mapred.FileInputFormat.listStatus(FileInputFormat.java:206)
at
org.apache.hadoop.mapred.FileInputFormat.getSplits(FileInputFormat.java:315)
at
org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getSplits(HdfsDataFragmenter.java:108)
at
org.apache.hawq.pxf.plugins.hdfs.HdfsDataFragmenter.getFragments(HdfsDataFragmenter.java:69)
at
org.apache.hawq.pxf.service.rest.FragmenterResource.getFragments(FragmenterResource.java:84)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15534) Unable to restart Falcon server
[ https://issues.apache.org/jira/browse/AMBARI-15534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209156#comment-15209156 ] Hudson commented on AMBARI-15534: - ABORTED: Integrated in Ambari-trunk-Commit #4534 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4534/]) AMBARI-15534. Unable to restart Falcon server (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e45d869e7434dba29bf55a06a54707f267b1f8f6]) * contrib/fast-hdfs-resource/src/main/java/org/apache/ambari/fast_hdfs_resource/Resource.java * ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/files/fast-hdfs-resource.jar > Unable to restart Falcon server > > > Key: AMBARI-15534 > URL: https://issues.apache.org/jira/browse/AMBARI-15534 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.2.2 > > Attachments: AMBARI-15534.patch > > > This is consistently noticed on WASB environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15539) YARN Queue should be refreshed when enabling/disabling Interactive Query
[ https://issues.apache.org/jira/browse/AMBARI-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-15539: Summary: YARN Queue should be refreshed when enabling/disabling Interactive Query (was: YARN Queue should be refreshed when adding/deleting Hive Interactive Server) > YARN Queue should be refreshed when enabling/disabling Interactive Query > > > Key: AMBARI-15539 > URL: https://issues.apache.org/jira/browse/AMBARI-15539 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-15539.patch > > > Capacity scheduler will be changed as part of saving Hive configs related to > adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed > before issuing Hive Interactive Server Start/Delete command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15539) YARN Queue should be refreshed when adding/deleting Hive Interactive Server
[ https://issues.apache.org/jira/browse/AMBARI-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-15539: Attachment: AMBARI-15539.patch > YARN Queue should be refreshed when adding/deleting Hive Interactive Server > --- > > Key: AMBARI-15539 > URL: https://issues.apache.org/jira/browse/AMBARI-15539 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > Attachments: AMBARI-15539.patch > > > Capacity scheduler will be changed as part of saving Hive configs related to > adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed > before issuing Hive Interactive Server Start/Delete command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15539) YARN Queue should be refreshed when adding/deleting Hive Interactive Server
[ https://issues.apache.org/jira/browse/AMBARI-15539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-15539: Description: Capacity scheduler will be changed as part of saving Hive configs related to adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed before issuing Hive Interactive Server Start/Delete command > YARN Queue should be refreshed when adding/deleting Hive Interactive Server > --- > > Key: AMBARI-15539 > URL: https://issues.apache.org/jira/browse/AMBARI-15539 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > > Capacity scheduler will be changed as part of saving Hive configs related to > adding/deleting Hive Interactive Server. So YARN Queue has to be refreshed > before issuing Hive Interactive Server Start/Delete command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15524) HAWQ - exchange keys should be done only from HAWQMASTER
[ https://issues.apache.org/jira/browse/AMBARI-15524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209123#comment-15209123 ] bhuvnesh chaudhary commented on AMBARI-15524: - The failed test does not relate to the patch applied. > HAWQ - exchange keys should be done only from HAWQMASTER > > > Key: AMBARI-15524 > URL: https://issues.apache.org/jira/browse/AMBARI-15524 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: bhuvnesh chaudhary >Assignee: bhuvnesh chaudhary > Fix For: 2.3.0, 2.2.0 > > Attachments: AMBARI-15524-1.patch, AMBARI-15524.patch > > > HAWQ - exchange keys should be done only from HAWQMASTER. Currently, both > standby and master does exchange keys however, its not required be done twice -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-15393: Attachment: AMBARI-15393_branch-2.2.patch > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15393.patch, AMBARI-15393_branch-2.2.patch > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option log_auto_execute_errors in logging > section to ambari-agent.ini. In case this is enabled agent will append stderr > of auto recovery command to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15393) Add stderr output of Ambari auto-recovery commands in agent log
[ https://issues.apache.org/jira/browse/AMBARI-15393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-15393: Attachment: (was: AMBARI-15393.patch) > Add stderr output of Ambari auto-recovery commands in agent log > --- > > Key: AMBARI-15393 > URL: https://issues.apache.org/jira/browse/AMBARI-15393 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.2.1 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.2.2 > > > Users rely on Ambari auto-recovery logic to recover from component start > failures during cluster create. The idea is to improve reliability (through > retries) by sacrificing some of the latency. > In some cases we see that cluster creates fail because component start fails > and auto-recovery is unable to start those components for up to 2 hrs, most > often on headnodes for HIVE_SERVER, OOZIE_SERVER, and NAMENODE components. > The problem these kind of problems are hard to investigate later, as auto > recovery files are not sent to server side nor they are saved in ambari agent > logs, only stored on agent . > The solution is to add a new an option log_auto_execute_errors in logging > section to ambari-agent.ini. In case this is enabled agent will append stderr > of auto recovery command to agent log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15534) Unable to restart Falcon server
[ https://issues.apache.org/jira/browse/AMBARI-15534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209069#comment-15209069 ] Hudson commented on AMBARI-15534: - FAILURE: Integrated in Ambari-branch-2.2 #547 (See [https://builds.apache.org/job/Ambari-branch-2.2/547/]) AMBARI-15534. Unable to restart Falcon server (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d177b60feff3a7f067ae14c37abd45f294d5e142]) * contrib/fast-hdfs-resource/src/main/java/org/apache/ambari/fast_hdfs_resource/Resource.java * ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/files/fast-hdfs-resource.jar > Unable to restart Falcon server > > > Key: AMBARI-15534 > URL: https://issues.apache.org/jira/browse/AMBARI-15534 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.2.2 > > Attachments: AMBARI-15534.patch > > > This is consistently noticed on WASB environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-6432) FreeIPA Support in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15209020#comment-15209020 ] Robert Levas commented on AMBARI-6432: -- Sorry for the delay. I got side tracked on a bunch of other issues. Also I failed to get FreeIPA installed on CentOS6 and for some reason Ambari no longer properly installs on CentOS7. I gave my +1 on the review board assuming all worked fine for you while testing. > FreeIPA Support in Ambari > - > > Key: AMBARI-6432 > URL: https://issues.apache.org/jira/browse/AMBARI-6432 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: jay vyas >Assignee: Bolke de Bruin > Fix For: 2.4.0 > > Attachments: AMBARI-6432-FreeIPA.patch, AMBARI-6432.patch, > AMBARI-6432.patch, AMBARI-6432.trunk.v1.patch, AMBARI-6432.trunk.v2.patch, > AMBARI-6432.trunk.v3.patch, AMBARI-6432.trunk.v4.patch, > AMBARI-6432.trunk.v5.patch, AMBARI-6432.trunk.v5.patch, > AMBARI-6432.trunk.v6.patch, AMBARI-6432.trunk.v7.patch, > AMBARI-6432.trunk.v8.patch, ipa-patch-v0.5.patch > > > FreeIPA Is a powerful tool for unifying identity, kerberos credentials, > across a cluster. > A great value add for ambari would be to provide support for using FreeIPA to > kerberize services. This would allow for > 1) better HCFS interoperability, because first class GID/UID is critical for > certain file systems (GlusterFS, Lustre, and any other file system which uses > kernel / FUSE apis for determining identity) > 2) better enterprise interoperability. Because of the fact that FreeIPA > makes it easy to interop with different identity solutions (like active > directory), it would make ambari easier to adopt for various enterprises. > 3) broadens ambaris scope. Now ambari could also allow people to setup the > users of their clusters, and at least some of the security features of their > clusters, all from one interface (no more manual handling of TGTs and such - > it could all be done quite easily via the ambari UI which could make calls to > underlying FreeIPA clients). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14854) Support downloadable Ambari Management Packs
[ https://issues.apache.org/jira/browse/AMBARI-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-14854: --- Attachment: ApacheAmbariManagementPacks.pdf > Support downloadable Ambari Management Packs > > > Key: AMBARI-14854 > URL: https://issues.apache.org/jira/browse/AMBARI-14854 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.4.0 > > Attachments: ApacheAmbariManagementPacks.pdf > > > _Motivation_: > Completely Decouple Ambari's cluster management and monitoring functions from > stack management and definition. This is true to some extent however the > objective of this Jira is to identify and address all issues that do not > allow Ambari core to live without a stack definition and thereby define the > scope of work as : "Allow stack definition to be a deploy time artifact vs > compile time". > In this regard following is short-term goals that can be achieved for the > next minor release version. > _Goals_: > - Allow ambari to be shipped without a default stack definition > - On server setup: > -- Make sure ambari gets a stack definition from the FS or a URL > -- Support basic checksum validation on the downloaded stack > - Make sure Ambari start after _setup-management-pack_ operation results in > graceful failure for _in-compatible_ stack definition downloaded. Example: > Deployed stack version is not present in the downloaded management pack. > - Support updates to the pack (to be scoped out) > _Assumptions_: > - The stack definition is a copy/download and replace (with backup), we do > not support fine-grained service merge / replace > - New definition is all inclusive stack def of all service versions supported > with current deployed version of Ambari > - The stack can have newer versions of services. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15537) Service Level Extensions for Add-On Services
[ https://issues.apache.org/jira/browse/AMBARI-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15537: --- Epic Name: ServiceExtensions > Service Level Extensions for Add-On Services > > > Key: AMBARI-15537 > URL: https://issues.apache.org/jira/browse/AMBARI-15537 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.1.0, 2.2.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > > In order to make add-on services self contained we need to support following > extension points > - Upgrade Pack Extensions > - Stack Advisor Extensions > - Role Command Order Extensions. This is covered in AMBARI-9363 (service > level RCO extension) > - Repo Extensions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15537) Service Level Extensions for Add-On Services
Jayush Luniya created AMBARI-15537: -- Summary: Service Level Extensions for Add-On Services Key: AMBARI-15537 URL: https://issues.apache.org/jira/browse/AMBARI-15537 Project: Ambari Issue Type: Story Affects Versions: 2.1.0, 2.2.0 Reporter: Jayush Luniya Assignee: Jayush Luniya In order to make add-on services self contained we need to support following extension points - Upgrade Pack Extensions - Stack Advisor Extensions - Role Command Order Extensions. This is covered in AMBARI-9363 (service level RCO extension) - Repo Extensions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15536) HBASE start,Check ZooKeeper and other ones was failed after upgrade to ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
[
https://issues.apache.org/jira/browse/AMBARI-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-15536:
Status: Patch Available (was: Open)
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> --
>
> Key: AMBARI-15536
> URL: https://issues.apache.org/jira/browse/AMBARI-15536
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-15536.patch
>
>
> STR: *Gateway* : http://host:8080/#/main/services/HBASE/summary - for 2.1.2
> 1)Deploy old version
> 2)Make Ambari only Upgrade
> Actual result:
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> {code}
> stderr: /var/lib/ambari-agent/data/errors-916.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 73, in
> ZookeeperServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 59, in service_check
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/zkSmoke.sh
> /usr/hdp/current/zookeeper-client/bin/zkCli.sh c-smoke
> /usr/hdp/current/zookeeper-client/conf 2181 False /usr/bin/kinit no_keytab
> no_principal /var/lib/ambari-agent/tmp/zkSmoke.out' returned 3.
> zk_node1=os-s11-3-usjyms-upg-sanity-202-1.test
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:703)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:363)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:698)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at
[jira] [Updated] (AMBARI-15536) HBASE start,Check ZooKeeper and other ones was failed after upgrade to ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
[
https://issues.apache.org/jira/browse/AMBARI-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-15536:
Affects Version/s: 2.2.2
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> --
>
> Key: AMBARI-15536
> URL: https://issues.apache.org/jira/browse/AMBARI-15536
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-15536.patch
>
>
> STR: *Gateway* : http://host:8080/#/main/services/HBASE/summary - for 2.1.2
> 1)Deploy old version
> 2)Make Ambari only Upgrade
> Actual result:
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> {code}
> stderr: /var/lib/ambari-agent/data/errors-916.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 73, in
> ZookeeperServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 59, in service_check
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/zkSmoke.sh
> /usr/hdp/current/zookeeper-client/bin/zkCli.sh c-smoke
> /usr/hdp/current/zookeeper-client/conf 2181 False /usr/bin/kinit no_keytab
> no_principal /var/lib/ambari-agent/tmp/zkSmoke.out' returned 3.
> zk_node1=os-s11-3-usjyms-upg-sanity-202-1.test
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:703)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:363)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:698)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at
[jira] [Updated] (AMBARI-15536) HBASE start,Check ZooKeeper and other ones was failed after upgrade to ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
[
https://issues.apache.org/jira/browse/AMBARI-15536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-15536:
Attachment: AMBARI-15536.patch
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> --
>
> Key: AMBARI-15536
> URL: https://issues.apache.org/jira/browse/AMBARI-15536
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-15536.patch
>
>
> STR: *Gateway* : http://host:8080/#/main/services/HBASE/summary - for 2.1.2
> 1)Deploy old version
> 2)Make Ambari only Upgrade
> Actual result:
> HBASE start,Check ZooKeeper and other ones was failed after upgrade to
> ambari 2.2.2.0 (resource_management.core.exceptions.Fail) from 2.1.1/2.1.2 etc
> {code}
> stderr: /var/lib/ambari-agent/data/errors-916.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 73, in
> ZookeeperServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/ZOOKEEPER/3.4.5.2.0/package/scripts/service_check.py",
> line 59, in service_check
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 238, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of
> '/var/lib/ambari-agent/tmp/zkSmoke.sh
> /usr/hdp/current/zookeeper-client/bin/zkCli.sh c-smoke
> /usr/hdp/current/zookeeper-client/conf 2181 False /usr/bin/kinit no_keytab
> no_principal /var/lib/ambari-agent/tmp/zkSmoke.out' returned 3.
> zk_node1=os-s11-3-usjyms-upg-sanity-202-1.test
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.delete(ZooKeeper.java:873)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:703)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:363)
> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:323)
> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:282)
> log4j:WARN No appenders could be found for logger
> (org.apache.zookeeper.ZooKeeper).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Exception in thread "main"
> org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode
> = ConnectionLoss for /zk_smoketest
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:99)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
> at org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:698)
> at org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:591)
> at
[jira] [Updated] (AMBARI-15533) HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
[
https://issues.apache.org/jira/browse/AMBARI-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15533:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
> --
>
> Key: AMBARI-15533
> URL: https://issues.apache.org/jira/browse/AMBARI-15533
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15533.patch
>
>
> SCRIPT alerts stuck in UNKNWN status with response message 'invalid literal
> for int() with base 10: '50.0''.
> It is noticed that the error is thrown only after a PUT alertDefinition call
> to update few parameters of alert definition since the numeric values are
> changed into strings.
> The scripts need to safely cast their parameters; the fix is in the script
> here.
> E.g PUT Request :
> {noformat}
> PUT http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "name" : "mergeHaMetrics",
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "value" : "false",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "type" : "STRING"
> },
> {
> "name" : "interval",
> "display_name" : "Time interval in minutes",
> "value" : 1441.0,
> "description" : "Time interval in minutes.",
> "type" : "NUMERIC"
> },
> {
> "name" : "appId",
> "display_name" : "AMS application id",
> "value" : "NAMENODE",
> "description" : "The application id used to retrieve the metric.",
> "type" : "STRING"
> },
> {
> "name" : "metricName",
> "display_name" : "Metric Name",
> "value" : "jvm.JvmMetrics.MemHeapUsedM",
> "description" : "The metric to monitor.",
> "type" : "STRING"
> },
> {
> "name" : "metric.deviation.warning.threshold",
> "display_name" : "The standard deviation threshold above which a
> warning is produced.",
> "units" : "%",
> "value" : 20.0,
> "type" : "PERCENT",
> "threshold" : "WARNING"
> },
> {
> "name" : "metric.deviation.critical.threshold",
> "display_name" : "The standard deviation threshold above which a
> critical alert is produced.",
> "units" : "%",
> "value" : 50.0,
> "type" : "PERCENT",
> "threshold" : "CRITICAL"
> }
> ],
> "path" : "HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py",
> "type" : "SCRIPT"
> }
> }
> }
> {noformat}
> Response :200OK
> {noformat}
> GET http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "href" :
> "http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38;,
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "name" : "mergeHaMetrics",
> "value" : "false",
> "type" : "STRING"
> },
> {
> "display_name" : "Time interval in minutes",
> "description" : "Time interval in minutes.",
> "name" : "interval",
> "value" : "1441.0",
> "type" : "NUMERIC"
> },
[jira] [Resolved] (AMBARI-15520) Add more warning on Pause button saying no topology changes.
[ https://issues.apache.org/jira/browse/AMBARI-15520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang resolved AMBARI-15520. - Resolution: Fixed Committed to branch-2.2 and trunk > Add more warning on Pause button saying no topology changes. > > > Key: AMBARI-15520 > URL: https://issues.apache.org/jira/browse/AMBARI-15520 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.2.2 > > Attachments: AMBARI-15520_branch-2.2.v0.patch, > AMBARI-15520_trunk.v0.patch, AMBARI-15520_trunk.v1.patch > > > Add more warning on Pause button saying no topology changes. > Really need to warn folks on not making any add hosts/RM HA/others. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14435) Parameterize distro-specific stack information for ZOOKEEPER
[
https://issues.apache.org/jira/browse/AMBARI-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juanjo Marron updated AMBARI-14435:
---
Description:
Apply the stack featurization prototype detailed on AMBARI-13364 to ZOOKEEPER
service plus the comments and reviews received on:
This patch removes the hardcoded stack versions and stack specific paths into
ZK common-services code
stack_features is now a property in .json format in
HDP/2.0.6/properties/stack_features.json
With the structure:
{
"stack_features": [
{ "name": "feature1", "description" : "Feature1 support", "min_version" :
"Y.Y.Y.Y" , "max_version" : "X.X.X.X"}
,
...
]
}
where min_version/max_version are optional constraints.
The upgrade constants, such has ROLLING_UPGRADE = "rolling_upgrade" has been
added to in a new StackFeature in
resource_management/libraries/functions/constants.py
Stack featurization was added as part of the HDP stack configurations on
/HDP/2.0.6/configuration/cluster-env.xml, introducing a new stack_features
property
New resource_management/libraries/functions/stack_fetaures.py has been
introduced to parse the json file and called from service code to check if the
stack supports the required feature.
was:
Apply the stack featurization prototype detailed on AMBARI-13364 to ZOOKEEPER
service.
This patch removes the hardcoded stack versions in ZK common-services code and
uses stack_features which a property in .json format in
configuration/cluster-env.xml for each stack version.
> Parameterize distro-specific stack information for ZOOKEEPER
>
>
> Key: AMBARI-14435
> URL: https://issues.apache.org/jira/browse/AMBARI-14435
> Project: Ambari
> Issue Type: Technical task
> Components: ambari-server
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
> Fix For: 2.4.0
>
> Attachments:
> 0001-AMBARI-14435-Parameterize-distro-specific-stack-info.patch,
> AMBARI-14435.patch
>
>
> Apply the stack featurization prototype detailed on AMBARI-13364 to
> ZOOKEEPER service plus the comments and reviews received on:
> This patch removes the hardcoded stack versions and stack specific paths into
> ZK common-services code
> stack_features is now a property in .json format in
> HDP/2.0.6/properties/stack_features.json
> With the structure:
> {
> "stack_features": [
> { "name": "feature1", "description" : "Feature1 support", "min_version" :
> "Y.Y.Y.Y" , "max_version" : "X.X.X.X"}
> ,
> ...
> ]
> }
> where min_version/max_version are optional constraints.
> The upgrade constants, such has ROLLING_UPGRADE = "rolling_upgrade" has been
> added to in a new StackFeature in
> resource_management/libraries/functions/constants.py
> Stack featurization was added as part of the HDP stack configurations on
> /HDP/2.0.6/configuration/cluster-env.xml, introducing a new stack_features
> property
> New resource_management/libraries/functions/stack_fetaures.py has been
> introduced to parse the json file and called from service code to check if
> the stack supports the required feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15522) update pxf-profile template with new fields and description
[ https://issues.apache.org/jira/browse/AMBARI-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208802#comment-15208802 ] bhuvnesh chaudhary commented on AMBARI-15522: - pushed to trunk and branch-2.2 > update pxf-profile template with new fields and description > --- > > Key: AMBARI-15522 > URL: https://issues.apache.org/jira/browse/AMBARI-15522 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov >Assignee: Alexander Denissov >Priority: Minor > Fix For: 2.2.2 > > Attachments: AMBARI-15522.branch22.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15531) Hiveserver2 goes down on HA cluster deployed via blueprint
[
https://issues.apache.org/jira/browse/AMBARI-15531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laszlo Puskas updated AMBARI-15531:
---
Status: Patch Available (was: In Progress)
> Hiveserver2 goes down on HA cluster deployed via blueprint
> --
>
> Key: AMBARI-15531
> URL: https://issues.apache.org/jira/browse/AMBARI-15531
> Project: Ambari
> Issue Type: Bug
>Reporter: Laszlo Puskas
>Assignee: Laszlo Puskas
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15531.b22.v1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> On an HA cluster deployed via bluerint, HiveServer2 is down and we see below
> in hiveserver2 logs
> {code}
> Caused by:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
> Permission denied: user=hive, access=WRITE,
> inode="/tmp/hive":hdfs:hdfs:drwxr-xr-x
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1780)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1764)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1747)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:3930)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1068)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:622)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2206)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2202)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2200)
> at org.apache.hadoop.ipc.Client.call(Client.java:1427)
> at org.apache.hadoop.ipc.Client.call(Client.java:1358)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy15.mkdirs(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.mkdirs(ClientNamenodeProtocolTranslatorPB.java:558)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:252)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:104)
> at com.sun.proxy.$Proxy16.mkdirs(Unknown Source)
> at org.apache.hadoop.hdfs.DFSClient.primitiveMkdir(DFSClient.java:3018)
> ... 24 more
> 2016-03-21 20:06:00,216 INFO [Thread-4]: server.HiveServer2
> (HiveStringUtils.java:run(709)) - SHUTDOWN_MSG:
> /
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15535) Permission on metrics-grafana.ini should be 600 to protect password
[ https://issues.apache.org/jira/browse/AMBARI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15535: --- Attachment: (was: AMBARI-15535.patch) > Permission on metrics-grafana.ini should be 600 to protect password > --- > > Key: AMBARI-15535 > URL: https://issues.apache.org/jira/browse/AMBARI-15535 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15535) Permission on metrics-grafana.ini should be 600 to protect password
[ https://issues.apache.org/jira/browse/AMBARI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15535: --- Attachment: AMBARI-15535.patch > Permission on metrics-grafana.ini should be 600 to protect password > --- > > Key: AMBARI-15535 > URL: https://issues.apache.org/jira/browse/AMBARI-15535 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15535.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15535) Permission on metrics-grafana.ini should be 600 to protect password
[ https://issues.apache.org/jira/browse/AMBARI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15535: --- Attachment: (was: AMBARI-15535.patch) > Permission on metrics-grafana.ini should be 600 to protect password > --- > > Key: AMBARI-15535 > URL: https://issues.apache.org/jira/browse/AMBARI-15535 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15535.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15535) Permission on metrics-grafana.ini should be 600 to protect password
[ https://issues.apache.org/jira/browse/AMBARI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208750#comment-15208750 ] Dmytro Sen commented on AMBARI-15535: - +1 > Permission on metrics-grafana.ini should be 600 to protect password > --- > > Key: AMBARI-15535 > URL: https://issues.apache.org/jira/browse/AMBARI-15535 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15535.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15535) Permission on metrics-grafana.ini should be 600 to protect password
[ https://issues.apache.org/jira/browse/AMBARI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-15535: --- Status: Patch Available (was: Open) > Permission on metrics-grafana.ini should be 600 to protect password > --- > > Key: AMBARI-15535 > URL: https://issues.apache.org/jira/browse/AMBARI-15535 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15535.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15534) Unable to restart Falcon server
[ https://issues.apache.org/jira/browse/AMBARI-15534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-15534: - Attachment: AMBARI-15534.patch > Unable to restart Falcon server > > > Key: AMBARI-15534 > URL: https://issues.apache.org/jira/browse/AMBARI-15534 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.2.2 > > Attachments: AMBARI-15534.patch > > > This is consistently noticed on WASB environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15534) Unable to restart Falcon server
Andrew Onischuk created AMBARI-15534: Summary: Unable to restart Falcon server Key: AMBARI-15534 URL: https://issues.apache.org/jira/browse/AMBARI-15534 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.2.2 Attachments: AMBARI-15534.patch This is consistently noticed on WASB environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15534) Unable to restart Falcon server
[ https://issues.apache.org/jira/browse/AMBARI-15534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-15534: - Status: Patch Available (was: Open) > Unable to restart Falcon server > > > Key: AMBARI-15534 > URL: https://issues.apache.org/jira/browse/AMBARI-15534 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.2.2 > > Attachments: AMBARI-15534.patch > > > This is consistently noticed on WASB environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15517) Improve config groups loading on wizard (part 1)
[ https://issues.apache.org/jira/browse/AMBARI-15517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208670#comment-15208670 ] Hudson commented on AMBARI-15517: - ABORTED: Integrated in Ambari-trunk-Commit #4533 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4533/]) AMBARI-15517 Improve config groups loading on wizard (part 1). (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7e1815db51adc60b2944b7cf17cf99ac293af84c]) * ambari-web/test/controllers/wizard/step7_test.js * ambari-web/app/utils/config.js * ambari-web/app/controllers/wizard/step7_controller.js > Improve config groups loading on wizard (part 1) > > > Key: AMBARI-15517 > URL: https://issues.apache.org/jira/browse/AMBARI-15517 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15517.patch > > > Simplify logic for adding saved overrides to configs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15431) Atlas Integration : Rename Atlas Configurations
[
https://issues.apache.org/jira/browse/AMBARI-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-15431:
---
Status: Patch Available (was: Reopened)
> Atlas Integration : Rename Atlas Configurations
> ---
>
> Key: AMBARI-15431
> URL: https://issues.apache.org/jira/browse/AMBARI-15431
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-15431-2.patch, AMBARI-15431.patch
>
>
> Atlas configuration name {{application.properties}} has been changed to
> {{atlas-application.properties}} to avoid name conflicts with other services.
> See https://issues.apache.org/jira/browse/ATLAS-392.
> Ambari scripts for Atlas currently use the configuration name
> {{application.properties}} for all stack levels. Stacks which include Atlas
> > 0.5 should use the configuration name {{atlas-application.properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15431) Atlas Integration : Rename Atlas Configurations
[
https://issues.apache.org/jira/browse/AMBARI-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-15431:
---
Attachment: AMBARI-15431-2.patch
> Atlas Integration : Rename Atlas Configurations
> ---
>
> Key: AMBARI-15431
> URL: https://issues.apache.org/jira/browse/AMBARI-15431
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-15431-2.patch, AMBARI-15431.patch
>
>
> Atlas configuration name {{application.properties}} has been changed to
> {{atlas-application.properties}} to avoid name conflicts with other services.
> See https://issues.apache.org/jira/browse/ATLAS-392.
> Ambari scripts for Atlas currently use the configuration name
> {{application.properties}} for all stack levels. Stacks which include Atlas
> > 0.5 should use the configuration name {{atlas-application.properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15383) Cleanup LDAP sync process
[
https://issues.apache.org/jira/browse/AMBARI-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208639#comment-15208639
]
Hadoop QA commented on AMBARI-15383:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794986/AMBARI-15383.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5991//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5991//console
This message is automatically generated.
> Cleanup LDAP sync process
> -
>
> Key: AMBARI-15383
> URL: https://issues.apache.org/jira/browse/AMBARI-15383
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.4.0
>
> Attachments: AMBARI-15383.patch
>
>
> 1. Skip unnecessary queries during ldap sync (speed up --all)
> 2. Remove membership attribute case sensitivity
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15533) HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
[
https://issues.apache.org/jira/browse/AMBARI-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15533:
-
Attachment: AMBARI-15533.patch
> HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
> --
>
> Key: AMBARI-15533
> URL: https://issues.apache.org/jira/browse/AMBARI-15533
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15533.patch
>
>
> SCRIPT alerts stuck in UNKNWN status with response message 'invalid literal
> for int() with base 10: '50.0''.
> It is noticed that the error is thrown only after a PUT alertDefinition call
> to update few parameters of alert definition since the numeric values are
> changed into strings.
> The scripts need to safely cast their parameters; the fix is in the script
> here.
> E.g PUT Request :
> {noformat}
> PUT http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "name" : "mergeHaMetrics",
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "value" : "false",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "type" : "STRING"
> },
> {
> "name" : "interval",
> "display_name" : "Time interval in minutes",
> "value" : 1441.0,
> "description" : "Time interval in minutes.",
> "type" : "NUMERIC"
> },
> {
> "name" : "appId",
> "display_name" : "AMS application id",
> "value" : "NAMENODE",
> "description" : "The application id used to retrieve the metric.",
> "type" : "STRING"
> },
> {
> "name" : "metricName",
> "display_name" : "Metric Name",
> "value" : "jvm.JvmMetrics.MemHeapUsedM",
> "description" : "The metric to monitor.",
> "type" : "STRING"
> },
> {
> "name" : "metric.deviation.warning.threshold",
> "display_name" : "The standard deviation threshold above which a
> warning is produced.",
> "units" : "%",
> "value" : 20.0,
> "type" : "PERCENT",
> "threshold" : "WARNING"
> },
> {
> "name" : "metric.deviation.critical.threshold",
> "display_name" : "The standard deviation threshold above which a
> critical alert is produced.",
> "units" : "%",
> "value" : 50.0,
> "type" : "PERCENT",
> "threshold" : "CRITICAL"
> }
> ],
> "path" : "HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py",
> "type" : "SCRIPT"
> }
> }
> }
> {noformat}
> Response :200OK
> {noformat}
> GET http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "href" :
> "http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38;,
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "name" : "mergeHaMetrics",
> "value" : "false",
> "type" : "STRING"
> },
> {
> "display_name" : "Time interval in minutes",
> "description" : "Time interval in minutes.",
> "name" : "interval",
> "value" : "1441.0",
> "type" : "NUMERIC"
> },
> {
>
[jira] [Updated] (AMBARI-15533) HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
[
https://issues.apache.org/jira/browse/AMBARI-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-15533:
-
Status: Patch Available (was: Open)
> HDFS Alerts for AMS Throw 'invalid literal for int() with base 10: '50.0''
> --
>
> Key: AMBARI-15533
> URL: https://issues.apache.org/jira/browse/AMBARI-15533
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.2.2
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15533.patch
>
>
> SCRIPT alerts stuck in UNKNWN status with response message 'invalid literal
> for int() with base 10: '50.0''.
> It is noticed that the error is thrown only after a PUT alertDefinition call
> to update few parameters of alert definition since the numeric values are
> changed into strings.
> The scripts need to safely cast their parameters; the fix is in the script
> here.
> E.g PUT Request :
> {noformat}
> PUT http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "name" : "mergeHaMetrics",
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "value" : "false",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "type" : "STRING"
> },
> {
> "name" : "interval",
> "display_name" : "Time interval in minutes",
> "value" : 1441.0,
> "description" : "Time interval in minutes.",
> "type" : "NUMERIC"
> },
> {
> "name" : "appId",
> "display_name" : "AMS application id",
> "value" : "NAMENODE",
> "description" : "The application id used to retrieve the metric.",
> "type" : "STRING"
> },
> {
> "name" : "metricName",
> "display_name" : "Metric Name",
> "value" : "jvm.JvmMetrics.MemHeapUsedM",
> "description" : "The metric to monitor.",
> "type" : "STRING"
> },
> {
> "name" : "metric.deviation.warning.threshold",
> "display_name" : "The standard deviation threshold above which a
> warning is produced.",
> "units" : "%",
> "value" : 20.0,
> "type" : "PERCENT",
> "threshold" : "WARNING"
> },
> {
> "name" : "metric.deviation.critical.threshold",
> "display_name" : "The standard deviation threshold above which a
> critical alert is produced.",
> "units" : "%",
> "value" : 50.0,
> "type" : "PERCENT",
> "threshold" : "CRITICAL"
> }
> ],
> "path" : "HDFS/2.1.0.2.0/package/alerts/alert_metrics_deviation.py",
> "type" : "SCRIPT"
> }
> }
> }
> {noformat}
> Response :200OK
> {noformat}
> GET http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38
> {
> "href" :
> "http://172.22.114.20:8080/api/v1/clusters/cl1/alert_definitions/38;,
> "AlertDefinition" : {
> "cluster_name" : "cl1",
> "component_name" : "NAMENODE",
> "description" : "This service-level alert is triggered if the NN heap
> usage deviation has grown beyond the specified threshold within a given time
> interval.",
> "enabled" : true,
> "id" : 38,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "NameNode Heap Usage (Daily)",
> "name" : "increase_nn_heap_usage_daily",
> "scope" : "ANY",
> "service_name" : "HDFS",
> "source" : {
> "parameters" : [
> {
> "display_name" : "Whether active and stanby NameNodes metrics
> should be merged",
> "description" : "Whether active and stanby NameNodes metrics should
> be merged.",
> "name" : "mergeHaMetrics",
> "value" : "false",
> "type" : "STRING"
> },
> {
> "display_name" : "Time interval in minutes",
> "description" : "Time interval in minutes.",
> "name" : "interval",
> "value" : "1441.0",
> "type" : "NUMERIC"
> },
> {
>
[jira] [Commented] (AMBARI-15431) Atlas Integration : Rename Atlas Configurations
[
https://issues.apache.org/jira/browse/AMBARI-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208518#comment-15208518
]
Tom Beerbower commented on AMBARI-15431:
Reopening... Need to move the
{{ambari-server/src/main/resources/stacks/HDP/2.6/}} changes to
{{ambari-server/src/main/resources/stacks/HDP/2.5/}}
> Atlas Integration : Rename Atlas Configurations
> ---
>
> Key: AMBARI-15431
> URL: https://issues.apache.org/jira/browse/AMBARI-15431
> Project: Ambari
> Issue Type: Bug
>Reporter: Tom Beerbower
>Assignee: Tom Beerbower
> Attachments: AMBARI-15431.patch
>
>
> Atlas configuration name {{application.properties}} has been changed to
> {{atlas-application.properties}} to avoid name conflicts with other services.
> See https://issues.apache.org/jira/browse/ATLAS-392.
> Ambari scripts for Atlas currently use the configuration name
> {{application.properties}} for all stack levels. Stacks which include Atlas
> > 0.5 should use the configuration name {{atlas-application.properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15532) ambari-web allows to delete a service that has running processes
[ https://issues.apache.org/jira/browse/AMBARI-15532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208448#comment-15208448 ] Aleksandr Kovalenko commented on AMBARI-15532: -- +1 for the patch > ambari-web allows to delete a service that has running processes > > > Key: AMBARI-15532 > URL: https://issues.apache.org/jira/browse/AMBARI-15532 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15532.patch > > > # Navigate to Hive Service summary page > # Stop Webhcat server > # Delete Hive Service > *Actual behavior:* As one master component of Hive is in installed state > which brings hive service in installed state, ambari-web considers this to be > a valid siatuation and executes delete API call on Hive service resource > *Expected behavior:* Instead of relying on service state, state of all master > and slave component of a service should be checked and if any of them is in > started state then user should be asked to stop the master component first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15532) ambari-web allows to delete a service that has running processes
[ https://issues.apache.org/jira/browse/AMBARI-15532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-15532: -- Status: Patch Available (was: Open) 24653 tests complete (21 seconds) 145 tests pending > ambari-web allows to delete a service that has running processes > > > Key: AMBARI-15532 > URL: https://issues.apache.org/jira/browse/AMBARI-15532 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15532.patch > > > # Navigate to Hive Service summary page > # Stop Webhcat server > # Delete Hive Service > *Actual behavior:* As one master component of Hive is in installed state > which brings hive service in installed state, ambari-web considers this to be > a valid siatuation and executes delete API call on Hive service resource > *Expected behavior:* Instead of relying on service state, state of all master > and slave component of a service should be checked and if any of them is in > started state then user should be asked to stop the master component first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15532) ambari-web allows to delete a service that has running processes
[ https://issues.apache.org/jira/browse/AMBARI-15532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-15532: -- Attachment: AMBARI-15532.patch > ambari-web allows to delete a service that has running processes > > > Key: AMBARI-15532 > URL: https://issues.apache.org/jira/browse/AMBARI-15532 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15532.patch > > > # Navigate to Hive Service summary page > # Stop Webhcat server > # Delete Hive Service > *Actual behavior:* As one master component of Hive is in installed state > which brings hive service in installed state, ambari-web considers this to be > a valid siatuation and executes delete API call on Hive service resource > *Expected behavior:* Instead of relying on service state, state of all master > and slave component of a service should be checked and if any of them is in > started state then user should be asked to stop the master component first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15532) ambari-web allows to delete a service that has running processes
Andrii Babiichuk created AMBARI-15532: - Summary: ambari-web allows to delete a service that has running processes Key: AMBARI-15532 URL: https://issues.apache.org/jira/browse/AMBARI-15532 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Priority: Critical Fix For: 2.4.0 # Navigate to Hive Service summary page # Stop Webhcat server # Delete Hive Service *Actual behavior:* As one master component of Hive is in installed state which brings hive service in installed state, ambari-web considers this to be a valid siatuation and executes delete API call on Hive service resource *Expected behavior:* Instead of relying on service state, state of all master and slave component of a service should be checked and if any of them is in started state then user should be asked to stop the master component first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15383) Cleanup LDAP sync process
[ https://issues.apache.org/jira/browse/AMBARI-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-15383: -- Attachment: AMBARI-15383.patch > Cleanup LDAP sync process > - > > Key: AMBARI-15383 > URL: https://issues.apache.org/jira/browse/AMBARI-15383 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-15383.patch > > > 1. Skip unnecessary queries during ldap sync (speed up --all) > 2. Remove membership attribute case sensitivity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15530) Hive View: Execution of queries throws "No query to process."
[
https://issues.apache.org/jira/browse/AMBARI-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208414#comment-15208414
]
Hadoop QA commented on AMBARI-15530:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794967/AMBARI-15530.branch-2.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5990//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5990//console
This message is automatically generated.
> Hive View: Execution of queries throws "No query to process."
> -
>
> Key: AMBARI-15530
> URL: https://issues.apache.org/jira/browse/AMBARI-15530
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.1.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.2.2
>
> Attachments: AMBARI-15530.branch-2.2.patch
>
>
> It is seen this a few times but no consistent way to reproduce. The Hive view
> can get into a state where when you hit Execute it says "No query to
> process." This happens when using queries that you can execute other times.
> Nothing shows up in the HS2 log when you hit this so this might be purely
> happening on the client side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15522) update pxf-profile template with new fields and description
[
https://issues.apache.org/jira/browse/AMBARI-15522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208395#comment-15208395
]
Hadoop QA commented on AMBARI-15522:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794889/AMBARI-15522.branch22.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5988//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5988//console
This message is automatically generated.
> update pxf-profile template with new fields and description
> ---
>
> Key: AMBARI-15522
> URL: https://issues.apache.org/jira/browse/AMBARI-15522
> Project: Ambari
> Issue Type: Bug
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
>Priority: Minor
> Fix For: 2.2.2
>
> Attachments: AMBARI-15522.branch22.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15412) Improve error logging for install errors during blueprint deployments
[
https://issues.apache.org/jira/browse/AMBARI-15412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208382#comment-15208382
]
Hadoop QA commented on AMBARI-15412:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794906/AMBARI-15412_branch-2.2.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5987//console
This message is automatically generated.
> Improve error logging for install errors during blueprint deployments
> -
>
> Key: AMBARI-15412
> URL: https://issues.apache.org/jira/browse/AMBARI-15412
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Attachments: AMBARI-15412.patch, AMBARI-15412_branch-2.2.patch,
> AMBARI-15412_output.png
>
>
> Improve error logging for install errors during blueprint deployment.
> Currently a severe error during install of a service component gets logged as
> a WARNing.
> E.g.:
> 09 Mar 2016 12:11:45,881 WARN [qtp-ambari-agent-146] HeartBeatHandler:603 -
> Operation failed - may be retried. Service component host: KAFKA_BROKER,
> host: hdtest159.svl.ibm.com Action id12-0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15383) Cleanup LDAP sync process
[ https://issues.apache.org/jira/browse/AMBARI-15383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-15383: -- Fix Version/s: (was: 2.2.2) 2.4.0 > Cleanup LDAP sync process > - > > Key: AMBARI-15383 > URL: https://issues.apache.org/jira/browse/AMBARI-15383 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.4.0 > > Attachments: AMBARI-15383.patch > > > 1. Skip unnecessary queries during ldap sync (speed up --all) > 2. Remove membership attribute case sensitivity -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15524) HAWQ - exchange keys should be done only from HAWQMASTER
[
https://issues.apache.org/jira/browse/AMBARI-15524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208380#comment-15208380
]
Hadoop QA commented on AMBARI-15524:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794909/AMBARI-15524.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5986//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5986//console
This message is automatically generated.
> HAWQ - exchange keys should be done only from HAWQMASTER
>
>
> Key: AMBARI-15524
> URL: https://issues.apache.org/jira/browse/AMBARI-15524
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: 2.3.0, 2.2.0
>
> Attachments: AMBARI-15524.patch
>
>
> HAWQ - exchange keys should be done only from HAWQMASTER. Currently, both
> standby and master does exchange keys however, its not required be done twice
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15388) Upgrade XML should be pushed down as much as possible to the services
[
https://issues.apache.org/jira/browse/AMBARI-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15208359#comment-15208359
]
Hadoop QA commented on AMBARI-15388:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12794806/AMBARI-15388%20Design.pdf
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/5984//console
This message is automatically generated.
> Upgrade XML should be pushed down as much as possible to the services
> -
>
> Key: AMBARI-15388
> URL: https://issues.apache.org/jira/browse/AMBARI-15388
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Tim Thorpe
>Assignee: Tim Thorpe
> Fix For: trunk
>
> Attachments: AMBARI-15388 Design.pdf, AMBARI-15388.patch
>
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> Currently the upgrade is defined as a series of xml files specific to the
> current stack version and the target stack version. Each upgrade xml defines
> the overall sequence of the upgrade and what needs to be done for each
> service. It would both easier to maintain and easier to add new services, if
> the services themselves could specify what should be done during their
> upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15531) Hiveserver2 goes down on HA cluster deployed via blueprint
Laszlo Puskas created AMBARI-15531:
--
Summary: Hiveserver2 goes down on HA cluster deployed via blueprint
Key: AMBARI-15531
URL: https://issues.apache.org/jira/browse/AMBARI-15531
Project: Ambari
Issue Type: Bug
Reporter: Laszlo Puskas
Assignee: Laszlo Puskas
Priority: Critical
Fix For: 2.2.2
On an HA cluster deployed via bluerint, HiveServer2 is down and we see below in
hiveserver2 logs
{code}
Caused by:
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException):
Permission denied: user=hive, access=WRITE,
inode="/tmp/hive":hdfs:hdfs:drwxr-xr-x
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:292)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:213)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1780)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1764)
at
org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkAncestorAccess(FSDirectory.java:1747)
at
org.apache.hadoop.hdfs.server.namenode.FSDirMkdirOp.mkdirs(FSDirMkdirOp.java:71)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.mkdirs(FSNamesystem.java:3930)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.mkdirs(NameNodeRpcServer.java:1068)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.mkdirs(ClientNamenodeProtocolServerSideTranslatorPB.java:622)
at
org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2206)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2202)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2200)
at org.apache.hadoop.ipc.Client.call(Client.java:1427)
at org.apache.hadoop.ipc.Client.call(Client.java:1358)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
at com.sun.proxy.$Proxy15.mkdirs(Unknown Source)
at
org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.mkdirs(ClientNamenodeProtocolTranslatorPB.java:558)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:252)
at
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:104)
at com.sun.proxy.$Proxy16.mkdirs(Unknown Source)
at org.apache.hadoop.hdfs.DFSClient.primitiveMkdir(DFSClient.java:3018)
... 24 more
2016-03-21 20:06:00,216 INFO [Thread-4]: server.HiveServer2
(HiveStringUtils.java:run(709)) - SHUTDOWN_MSG:
/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
