[jira] [Created] (AMBARI-19145) Namenodes failed to start while adding a Jouralnode
Vivek Rathod created AMBARI-19145:
-
Summary: Namenodes failed to start while adding a Jouralnode
Key: AMBARI-19145
URL: https://issues.apache.org/jira/browse/AMBARI-19145
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
STR:
1) Install cluster and Enable HA with 3 Journalnodes
2) Add a Journal node using manage JN wizard (This goes through fine)
3) Add another Journal node
This time go to hosts page, and click add component-> JN and use the manage JN
wizard
Namenodes fail to start in the final step.
Both the namenodes fail to connect to each other
{noformat}
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
at
org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
at
org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
at org.apache.hadoop.ipc.Client.call(Client.java:1449)
at org.apache.hadoop.ipc.Client.call(Client.java:1396)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
at
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[
https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734517#comment-15734517
]
Hadoop QA commented on AMBARI-19117:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842454/AMBARI-19117.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/9598//console
This message is automatically generated.
> Implement Create Alerts: PORT alert configs page (step 2)
> -
>
> Key: AMBARI-19117
> URL: https://issues.apache.org/jira/browse/AMBARI-19117
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 3.0.0
>
> Attachments: AMBARI-19117.patch, AMBARI-19117.patch, Step2-PORT-40%
> done.png
>
>
> This is a FE task to implement the "Create Alerts Wizard " based on the
> design attached.
> This task is to create Step 2 of PORT alert. see the design for details.
> Pay attention to the dependencies on selecting different options. The further
> fields will determined by the current selection.
> eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display
> totally different UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[
https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734505#comment-15734505
]
Hadoop QA commented on AMBARI-19143:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842482/AMBARI-19143.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/9597//console
This message is automatically generated.
> Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
> -
>
> Key: AMBARI-19143
> URL: https://issues.apache.org/jira/browse/AMBARI-19143
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19143.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[
https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734492#comment-15734492
]
Hadoop QA commented on AMBARI-19123:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842490/AMBARI-19123_branch-2.5-v3.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/9596//console
This message is automatically generated.
> Update zeppelin configuration for ambari 2.5
>
>
> Key: AMBARI-19123
> URL: https://issues.apache.org/jira/browse/AMBARI-19123
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Fix For: 2.5.0
>
> Attachments: AMBARI-19123_branch-2.5-v1.patch,
> AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch
>
>
> Update zeppelin configuration for ambari 2.5, and add more configuration
> template for shiro.ini
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18801) Druid Router should be specified as a MASTER instead of SLAVE
[ https://issues.apache.org/jira/browse/AMBARI-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734469#comment-15734469 ] Hudson commented on AMBARI-18801: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6196 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6196/]) AMBARI-18801. Druid Router should be specified as a MASTER instead of (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0e4cac685b90861a44837ca9100ef2468992d47b]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml > Druid Router should be specified as a MASTER instead of SLAVE > - > > Key: AMBARI-18801 > URL: https://issues.apache.org/jira/browse/AMBARI-18801 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18801.patch > > > DRUID ROUTER should be specified as a MASTER instead of SLAVE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18801) Druid Router should be specified as a MASTER instead of SLAVE
[ https://issues.apache.org/jira/browse/AMBARI-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734457#comment-15734457 ] Hudson commented on AMBARI-18801: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #495 (See [https://builds.apache.org/job/Ambari-branch-2.5/495/]) AMBARI-18801. Druid Router should be specified as a MASTER instead of (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5e2c267f77639e8d9a8dbd5884f681c95781f4b5]) * (edit) ambari-server/src/main/resources/common-services/DRUID/0.9.2/metainfo.xml > Druid Router should be specified as a MASTER instead of SLAVE > - > > Key: AMBARI-18801 > URL: https://issues.apache.org/jira/browse/AMBARI-18801 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18801.patch > > > DRUID ROUTER should be specified as a MASTER instead of SLAVE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18791: --- Assignee: Nishant Bangarwa (was: Sumit Mohanty) > ADD configs for DRUID in KNOX service definitions > - > > Key: AMBARI-18791 > URL: https://issues.apache.org/jira/browse/AMBARI-18791 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18791.patch > > > KNOX now supports proxying druid services - > https://issues.apache.org/jira/browse/KNOX-758 > Add configs for DRUID in KNOX service definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18801) Druid Router should be specified as a MASTER instead of SLAVE
[ https://issues.apache.org/jira/browse/AMBARI-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18801: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Druid Router should be specified as a MASTER instead of SLAVE > - > > Key: AMBARI-18801 > URL: https://issues.apache.org/jira/browse/AMBARI-18801 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18801.patch > > > DRUID ROUTER should be specified as a MASTER instead of SLAVE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19144) Add property existence check to druid stack advisor code
Nishant Bangarwa created AMBARI-19144: - Summary: Add property existence check to druid stack advisor code Key: AMBARI-19144 URL: https://issues.apache.org/jira/browse/AMBARI-19144 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa Druid stack advisor assumes that druid-common will always be present in configurations. Generally, we cannot assume that druid configuration is always available.So adding a check for if "druid-common" exists in services['configurations'] will be enough. Review the rest of the code and ensure that there are checks for the existence of the config types. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19123) Update zeppelin configuration for ambari 2.5
[ https://issues.apache.org/jira/browse/AMBARI-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-19123: - Attachment: AMBARI-19123_branch-2.5-v3.patch > Update zeppelin configuration for ambari 2.5 > > > Key: AMBARI-19123 > URL: https://issues.apache.org/jira/browse/AMBARI-19123 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 2.5.0 > > Attachments: AMBARI-19123_branch-2.5-v1.patch, > AMBARI-19123_branch-2.5-v2.patch, AMBARI-19123_branch-2.5-v3.patch > > > Update zeppelin configuration for ambari 2.5, and add more configuration > template for shiro.ini -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-18791: -- Assignee: Sumit Mohanty > ADD configs for DRUID in KNOX service definitions > - > > Key: AMBARI-18791 > URL: https://issues.apache.org/jira/browse/AMBARI-18791 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Sumit Mohanty > Fix For: trunk, 2.5.0 > > Attachments: ambari-18791.patch > > > KNOX now supports proxying druid services - > https://issues.apache.org/jira/browse/KNOX-758 > Add configs for DRUID in KNOX service definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18791) ADD configs for DRUID in KNOX service definitions
[ https://issues.apache.org/jira/browse/AMBARI-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734375#comment-15734375 ] Nishant Bangarwa commented on AMBARI-18791: --- [~sumitmohanty] assigned to you for review. Please review. > ADD configs for DRUID in KNOX service definitions > - > > Key: AMBARI-18791 > URL: https://issues.apache.org/jira/browse/AMBARI-18791 > Project: Ambari > Issue Type: Task >Reporter: Nishant Bangarwa >Assignee: Sumit Mohanty > Fix For: trunk, 2.5.0 > > Attachments: ambari-18791.patch > > > KNOX now supports proxying druid services - > https://issues.apache.org/jira/browse/KNOX-758 > Add configs for DRUID in KNOX service definitions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18801) Druid Router should be specified as a MASTER instead of SLAVE
[ https://issues.apache.org/jira/browse/AMBARI-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18801: --- Assignee: Nishant Bangarwa > Druid Router should be specified as a MASTER instead of SLAVE > - > > Key: AMBARI-18801 > URL: https://issues.apache.org/jira/browse/AMBARI-18801 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.5.0 > > Attachments: ambari-18801.patch > > > DRUID ROUTER should be specified as a MASTER instead of SLAVE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[ https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19143: - Attachment: AMBARI-19143.patch > Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. > - > > Key: AMBARI-19143 > URL: https://issues.apache.org/jira/browse/AMBARI-19143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19143.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[ https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19143: - Status: Patch Available (was: Open) > Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. > - > > Key: AMBARI-19143 > URL: https://issues.apache.org/jira/browse/AMBARI-19143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > Attachments: AMBARI-19143.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[ https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19143: - Fix Version/s: 2.5.0 > Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. > - > > Key: AMBARI-19143 > URL: https://issues.apache.org/jira/browse/AMBARI-19143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[ https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reassigned AMBARI-19143: Assignee: Swapan Shridhar > Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. > - > > Key: AMBARI-19143 > URL: https://issues.apache.org/jira/browse/AMBARI-19143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
[ https://issues.apache.org/jira/browse/AMBARI-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-19143: - Affects Version/s: 2.4.1 > Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. > - > > Key: AMBARI-19143 > URL: https://issues.apache.org/jira/browse/AMBARI-19143 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.1 >Reporter: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19143) Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'.
Swapan Shridhar created AMBARI-19143: Summary: Fix test cases in : 'test_hive_server_int.py and 'test_stack_advisor.py'. Key: AMBARI-19143 URL: https://issues.apache.org/jira/browse/AMBARI-19143 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Swapan Shridhar -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-11001) Ambari uses users' interactive ticket cache
[ https://issues.apache.org/jira/browse/AMBARI-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734134#comment-15734134 ] Eric Yang commented on AMBARI-11001: Sorry I am not following your logic. useTicketCache, and renewTGT should both set to true for good defaults. I don't understand the current default logic to have Ambari stop working after 24 hours. > Ambari uses users' interactive ticket cache > --- > > Key: AMBARI-11001 > URL: https://issues.apache.org/jira/browse/AMBARI-11001 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Critical > Labels: JAAS > Fix For: 2.1.0 > > Attachments: AMBARI-11001_01.patch > > > It appears that it is necessary to kinit prior to starting ambari-server, > even after ambari-server setup-security (#3). It seems that this should be > automatically handled by Ambari. > Ambari-server should NOT use the same ticket cache as the interactive user. > STR: > 1. kinit > 2. ambari-server start > 3. verify that ambari-server can authenticate with ticket specified in #1 > 4. kdestroy > 5. try to authenticate through Ambari again (it will not work) > *Solution* > Ensure JAAS Login works properly such that the Kerberos tickets for the > account that executes Ambari is not relevant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18926) Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
[ https://issues.apache.org/jira/browse/AMBARI-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733849#comment-15733849 ] Sangeeta Ravindran edited comment on AMBARI-18926 at 12/9/16 12:37 AM: --- Failure is unrelated to commit. [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari-server: Too many files with unapproved license: 2 See RAT report in: /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/rat.txt -> [Help 1] was (Author: sangeetar): Failure is unrelated to changes. [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari-server: Too many files with unapproved license: 2 See RAT report in: /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/rat.txt -> [Help 1] > Kerberos Wizard UI creates duplicate radio buttons for FreeIPA > -- > > Key: AMBARI-18926 > URL: https://issues.apache.org/jira/browse/AMBARI-18926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Jesus Alvarez >Assignee: Jesus Alvarez >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18926-3.patch, kdc_type_duplicate_ipa.png > > > If the enableIPA flag is set to allow Ambari to use FreeIPA as a KDC, the > kerberos wizard will create duplicate radio buttons if a user navigates Back > from step2 to step1 of the kerberos wizard. > Issue here that in step1_controller.js, options.pushObject(ipaOption) will be > called on every loadStep.. including when navigating back to step1 from a > later step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18926) Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
[ https://issues.apache.org/jira/browse/AMBARI-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733849#comment-15733849 ] Sangeeta Ravindran commented on AMBARI-18926: - Failure is unrelated to changes. [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ambari-server: Too many files with unapproved license: 2 See RAT report in: /home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/target/rat.txt -> [Help 1] > Kerberos Wizard UI creates duplicate radio buttons for FreeIPA > -- > > Key: AMBARI-18926 > URL: https://issues.apache.org/jira/browse/AMBARI-18926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Jesus Alvarez >Assignee: Jesus Alvarez >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18926-3.patch, kdc_type_duplicate_ipa.png > > > If the enableIPA flag is set to allow Ambari to use FreeIPA as a KDC, the > kerberos wizard will create duplicate radio buttons if a user navigates Back > from step2 to step1 of the kerberos wizard. > Issue here that in step1_controller.js, options.pushObject(ipaOption) will be > called on every loadStep.. including when navigating back to step1 from a > later step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19117) Implement Create Alerts: PORT alert configs page (step 2)
[ https://issues.apache.org/jira/browse/AMBARI-19117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19117: - Attachment: AMBARI-19117.patch > Implement Create Alerts: PORT alert configs page (step 2) > - > > Key: AMBARI-19117 > URL: https://issues.apache.org/jira/browse/AMBARI-19117 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19117.patch, AMBARI-19117.patch, Step2-PORT-40% > done.png > > > This is a FE task to implement the "Create Alerts Wizard " based on the > design attached. > This task is to create Step 2 of PORT alert. see the design for details. > Pay attention to the dependencies on selecting different options. The further > fields will determined by the current selection. > eg. Selecting HDP service (such as HDFS, YARN) or Custom service will display > totally different UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18926) Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
[ https://issues.apache.org/jira/browse/AMBARI-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733812#comment-15733812 ] Hudson commented on AMBARI-18926: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6195 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6195/]) AMBARI-18926 - Kerberos Wizard UI creates duplicate radio buttons for (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=da2228fb3fe10c485ba374030eef85151cf8565d]) * (edit) ambari-web/app/controllers/main/admin/kerberos/step1_controller.js * (edit) ambari-web/test/controllers/main/admin/kerberos/step1_controller_test.js > Kerberos Wizard UI creates duplicate radio buttons for FreeIPA > -- > > Key: AMBARI-18926 > URL: https://issues.apache.org/jira/browse/AMBARI-18926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Jesus Alvarez >Assignee: Jesus Alvarez >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18926-3.patch, kdc_type_duplicate_ipa.png > > > If the enableIPA flag is set to allow Ambari to use FreeIPA as a KDC, the > kerberos wizard will create duplicate radio buttons if a user navigates Back > from step2 to step1 of the kerberos wizard. > Issue here that in step1_controller.js, options.pushObject(ipaOption) will be > called on every loadStep.. including when navigating back to step1 from a > later step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19137) HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
[ https://issues.apache.org/jira/browse/AMBARI-19137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733762#comment-15733762 ] Hudson commented on AMBARI-19137: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6194 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6194/]) AMBARI-19137. HDP 3.0 TP - move ZK, HDFS, YARN/MR into new (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=647c6f27e21c1f3ac620b039860cbb9c176acb2f]) * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_namenode.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/install_jars.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_nfsgateway.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/templates/mapreduce.conf.j2 * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/mapred_service_check.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/params_linux.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/ranger-yarn-policymgr-ssl.xml * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration-mapred/mapred-env.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/datanode_upgrade.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/capacity-scheduler.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/namenode_ha_state.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/kerberos.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/zkfc_slave.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/files/validateYarnComponentStatusWindows.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/alerts.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/alerts/alert_nodemanager_health.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/datanode.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/templates/hdfs.conf.j2 * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/alerts/alert_ha_namenode_health.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/ranger-yarn-security.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hadoop-env.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/setup_ranger_hdfs.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/params_windows.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_client.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/service_check.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/setup_ranger_yarn.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/kerberos.json * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-audit.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/alerts/alert_datanode_unmounted_data_dir.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/widgets.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/themes/theme.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/metainfo.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration-mapred/mapred-site.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/yarn-env.xml * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-log4j.xml * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/core-site.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/install_params.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/capacity-scheduler.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/journalnode_upgrade.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/ssl-client.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/themes-mapred/theme.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/utils.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/metain
[jira] [Commented] (AMBARI-19137) HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
[ https://issues.apache.org/jira/browse/AMBARI-19137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733749#comment-15733749 ] Hudson commented on AMBARI-19137: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #494 (See [https://builds.apache.org/job/Ambari-branch-2.5/494/]) AMBARI-19137. HDP 3.0 TP - move ZK, HDFS, YARN/MR into new (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d845449afaa2f64c6b06f48159248c0538bd493c]) * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/mapred_service_check.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/templates/exclude_hosts_list.j2 * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/yarn.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/datanode_upgrade.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/yarn-log4j.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/nodemanager_upgrade.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/themes-mapred/theme.json * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hdfs-log4j.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration-mapred/mapred-site.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/kerberos.json * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-plugin-properties.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/journalnode.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/templates/exclude_hosts_list.j2 * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/YARN_widgets.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration/ranger-yarn-security.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_rebalance.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hadoop-env.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/ranger-hdfs-security.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/ranger-hdfs-plugin-properties.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/alerts/alert_nodemanager_health.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-audit.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/install_jars.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs_nfsgateway.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/metainfo.xml * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/yarn-log4j.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/configuration/hadoop-policy.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/themes/theme.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/balancer-emulator/balancer.log * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/alerts.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/files/checkWebUI.py * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/YARN_widgets.json * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/setup_ranger_yarn.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/hdfs-log4j.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/package/scripts/service.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/themes/theme.json * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/scripts/hdfs.py * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/alerts/alert_ha_namenode_health.py * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/HDFS/configuration/ranger-hdfs-security.xml * (add) ambari-server/src/main/resources/common-services/YARN/3.0.0/configuration-mapred/mapred-logsearch-conf.xml * (delete) ambari-server/src/main/resources/stacks/HDP/3.0/services/YARN/configuration/ranger-yarn-plugin-properties.xml * (add) ambari-server/src/main/resources/common-services/HDFS/3.0.0/package/alerts/alert_metrics_deviation.py * (add) ambari-server/src/main/resources/common-se
[jira] [Commented] (AMBARI-19133) hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed unless WebHcat is installed
[
https://issues.apache.org/jira/browse/AMBARI-19133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733736#comment-15733736
]
Hadoop QA commented on AMBARI-19133:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842436/AMBARI-19133_trunk_01.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/9595//console
This message is automatically generated.
> hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed
> unless WebHcat is installed
>
>
> Key: AMBARI-19133
> URL: https://issues.apache.org/jira/browse/AMBARI-19133
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19133_branch-2.5_01.patch,
> AMBARI-19133_trunk_01.patch
>
>
> {{hadoop.proxyuser.HTTP.hosts}} should not be updated when Hive is installed
> unless WebHcat is installed.
> This is happening because the following block in the Kerberos descriptor is
> at the HIVE service level rather than the WEBHCAT_SERVER component level.
> {code}
> {
> "core-site": {
> "hadoop.proxyuser.HTTP.hosts":
> "${clusterHostInfo/webhcat_server_host}"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18926) Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
[ https://issues.apache.org/jira/browse/AMBARI-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18926: Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to ambari-trunk as commit da2228fb3fe10c485ba374030eef85151cf8565d Author: Sangeeta Ravindran Date: Thu Dec 8 15:32:26 2016 -0800 AMBARI-18926 - Kerberos Wizard UI creates duplicate radio buttons for FreeIPA (Jesus Alvarez via sangeetar) > Kerberos Wizard UI creates duplicate radio buttons for FreeIPA > -- > > Key: AMBARI-18926 > URL: https://issues.apache.org/jira/browse/AMBARI-18926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Jesus Alvarez >Assignee: Jesus Alvarez >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18926-3.patch, kdc_type_duplicate_ipa.png > > > If the enableIPA flag is set to allow Ambari to use FreeIPA as a KDC, the > kerberos wizard will create duplicate radio buttons if a user navigates Back > from step2 to step1 of the kerberos wizard. > Issue here that in step1_controller.js, options.pushObject(ipaOption) will be > called on every loadStep.. including when navigating back to step1 from a > later step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19130) Downgrade Can Create Multiple Mappings For Latest Configs
[
https://issues.apache.org/jira/browse/AMBARI-19130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733699#comment-15733699
]
Hudson commented on AMBARI-19130:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6193 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6193/])
AMBARI-19130 - Downgrade Can Create Multiple Mappings For Latest Configs
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=72586a1ed95728dff642758545cc9676fb77aa9e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigMappingEntity.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/ServiceConfigDAOTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
> Downgrade Can Create Multiple Mappings For Latest Configs
> -
>
> Key: AMBARI-19130
> URL: https://issues.apache.org/jira/browse/AMBARI-19130
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19130.patch
>
>
> During a downgrade which crosses major stack versions (such as from HDP 2.y
> to HDP 2.x), Ambari attempts to set the latest configurations from HDP 2.x as
> "current". However, after the downgrade succeeds, the database fails with the
> following consistency check:
> {code}
> ERROR - You have config(s), in cluster c1, that is(are) selected more than
> once in clusterconfigmapping table:
> ranger-storm-plugin-properties,mapred-env,webhcat-env,hive-exec-log4j,hive-log4j,webhcat-log4j,storm-env,yarn-log4j,hcat-env
> {code}
> The problem is actually not with {{clusterconfig}} but with the state of the
> {{clusterconfigmapping}} table _before_ upgrade. Apparently, it is possible
> to have multiple mappings for the same config. We match on the config type
> and tag (such as hdfs-site / version1234566789). There should never, EVER be
> duplicate mappings for the same config and version tag.
> The current downgrade code doesn't "break" after finding its first match:
> {code}
> for(ClusterConfigMappingEntity configMappingEntity:
> configMappingEntities){
> String type = configMappingEntity.getType();
> String tag = configMappingEntity.getTag();
> for (ClusterConfigMappingEntity latest : latestConfigMappingByStack) {
> String latestType = latest.getType();
> String latestTag = latest.getTag();
> // find the latest config of a given mapping entity
> if (StringUtils.equals(type, latestType) && StringUtils.equals(tag,
> latestTag)) {
> LOG.info("{} with version tag {} is selected for stack {}", type,
> tag, stackId.toString());
> configMappingEntity.setSelected(1);
> }
> }
> }
> {code}
> I'm not sure that breaking will work here since we don't know the ordering.
> We could order the results and then break on the first match. In any event,
> it's a problem. But it's only a problem for the latest version of a config
> since that's what we're going to try to make selected.
> Here's a query from a test cluster which shows that if this cluster were to
> be downgraded, 5 configs would have multiple mappings created. This is
> because for the latest config, there are multiple mappings in
> {{clusterconfigmapping}}.
> {noformat}
> SELECT
> mapping.type_name,
> mapping.version_tag,
> COUNT(*)
> FROM clusterconfigmapping mapping
> JOIN (SELECT
> config.type_name,
> config.version_tag,
> MAX(config.version) AS latest_version
> FROM clusterconfig config
> GROUP BY config.type_name) AS latestConfig
> ON latestConfig.type_name = mapping.type_name
> AND latestConfig.version_tag = mapping.version_tag
> GROUP BY
> type_name, version_tag
> HAVING COUNT(*) > 1
> +---+--+--+
> | type_name | version_tag | COUNT(*) |
> +---+--+--+
> | hcat-env | version1 |5 |
> | hive-exec-log4j | version1 |5 |
> | hive-log4j| version1 |5 |
> | ranger-hive-plugin-properties | version1436918769763 |3 |
> | webhcat-env | version1 |5 |
> +---+--+--+
> 5 rows in set (0.00 sec)
> {noformat}
> STR:
> # Install a cluster, and instrument the {{clusterconfigmapping}} table to
> hav
[jira] [Commented] (AMBARI-19130) Downgrade Can Create Multiple Mappings For Latest Configs
[
https://issues.apache.org/jira/browse/AMBARI-19130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733695#comment-15733695
]
Hudson commented on AMBARI-19130:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #493 (See
[https://builds.apache.org/job/Ambari-branch-2.5/493/])
AMBARI-19130 - Downgrade Can Create Multiple Mappings For Latest Configs
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=facfa8cea364370434f9e3596147801d73c0d1f0])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/cluster/ClusterTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigMappingEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/ServiceConfigDAOTest.java
> Downgrade Can Create Multiple Mappings For Latest Configs
> -
>
> Key: AMBARI-19130
> URL: https://issues.apache.org/jira/browse/AMBARI-19130
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19130.patch
>
>
> During a downgrade which crosses major stack versions (such as from HDP 2.y
> to HDP 2.x), Ambari attempts to set the latest configurations from HDP 2.x as
> "current". However, after the downgrade succeeds, the database fails with the
> following consistency check:
> {code}
> ERROR - You have config(s), in cluster c1, that is(are) selected more than
> once in clusterconfigmapping table:
> ranger-storm-plugin-properties,mapred-env,webhcat-env,hive-exec-log4j,hive-log4j,webhcat-log4j,storm-env,yarn-log4j,hcat-env
> {code}
> The problem is actually not with {{clusterconfig}} but with the state of the
> {{clusterconfigmapping}} table _before_ upgrade. Apparently, it is possible
> to have multiple mappings for the same config. We match on the config type
> and tag (such as hdfs-site / version1234566789). There should never, EVER be
> duplicate mappings for the same config and version tag.
> The current downgrade code doesn't "break" after finding its first match:
> {code}
> for(ClusterConfigMappingEntity configMappingEntity:
> configMappingEntities){
> String type = configMappingEntity.getType();
> String tag = configMappingEntity.getTag();
> for (ClusterConfigMappingEntity latest : latestConfigMappingByStack) {
> String latestType = latest.getType();
> String latestTag = latest.getTag();
> // find the latest config of a given mapping entity
> if (StringUtils.equals(type, latestType) && StringUtils.equals(tag,
> latestTag)) {
> LOG.info("{} with version tag {} is selected for stack {}", type,
> tag, stackId.toString());
> configMappingEntity.setSelected(1);
> }
> }
> }
> {code}
> I'm not sure that breaking will work here since we don't know the ordering.
> We could order the results and then break on the first match. In any event,
> it's a problem. But it's only a problem for the latest version of a config
> since that's what we're going to try to make selected.
> Here's a query from a test cluster which shows that if this cluster were to
> be downgraded, 5 configs would have multiple mappings created. This is
> because for the latest config, there are multiple mappings in
> {{clusterconfigmapping}}.
> {noformat}
> SELECT
> mapping.type_name,
> mapping.version_tag,
> COUNT(*)
> FROM clusterconfigmapping mapping
> JOIN (SELECT
> config.type_name,
> config.version_tag,
> MAX(config.version) AS latest_version
> FROM clusterconfig config
> GROUP BY config.type_name) AS latestConfig
> ON latestConfig.type_name = mapping.type_name
> AND latestConfig.version_tag = mapping.version_tag
> GROUP BY
> type_name, version_tag
> HAVING COUNT(*) > 1
> +---+--+--+
> | type_name | version_tag | COUNT(*) |
> +---+--+--+
> | hcat-env | version1 |5 |
> | hive-exec-log4j | version1 |5 |
> | hive-log4j| version1 |5 |
> | ranger-hive-plugin-properties | version1436918769763 |3 |
> | webhcat-env | version1 |5 |
> +---+--+--+
> 5 rows in set (0.00 sec)
> {noformat}
> STR:
> # Install a cluster, and instrument the {{clusterconfigmapping}} table to
> have mult
[jira] [Updated] (AMBARI-19137) HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
[
https://issues.apache.org/jira/browse/AMBARI-19137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19137:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk, commit 647c6f27e21c1f3ac620b039860cbb9c176acb2f
branch-2.5, commit d845449afaa2f64c6b06f48159248c0538bd493c
> HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
>
>
> Key: AMBARI-19137
> URL: https://issues.apache.org/jira/browse/AMBARI-19137
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19137.patch
>
>
> Create new versions in common-services for ZK, HDFS, YARN/MR and inherit from
> them in HDP 3.0 TP
> common-services is allowed to define
> * kerberos.json
> * widgets
> * themes
> * configs
> Create new version in common services
> ZK: 3.4.9, inherit from ZK 3.4.6 in common services
> HDFS: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor from
> the previous version in common-services and combine with the flattened files
> from HDP 2.0.6 through HDP 2.6
> YARN/MR: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor
> from the previous version in common-services and combine with the flattened
> files from HDP 2.0.6 through HDP 2.6
> Finally, any configs with references to /usr/hdp must be replaced by
> {{stack_root}, and configs that use ${hdp.version} must be overriden by the
> HDP 3.0 stack and kept clean in the version used by common-services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19137) HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
[
https://issues.apache.org/jira/browse/AMBARI-19137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-19137:
-
Summary: HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services
version (was: HDP 3.0 TP - move ZK, HFDS, YARN/MR into new common-services
version)
> HDP 3.0 TP - move ZK, HDFS, YARN/MR into new common-services version
>
>
> Key: AMBARI-19137
> URL: https://issues.apache.org/jira/browse/AMBARI-19137
> Project: Ambari
> Issue Type: Story
> Components: stacks
>Affects Versions: 2.5.0
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.0
>
> Attachments: AMBARI-19137.patch
>
>
> Create new versions in common-services for ZK, HDFS, YARN/MR and inherit from
> them in HDP 3.0 TP
> common-services is allowed to define
> * kerberos.json
> * widgets
> * themes
> * configs
> Create new version in common services
> ZK: 3.4.9, inherit from ZK 3.4.6 in common services
> HDFS: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor from
> the previous version in common-services and combine with the flattened files
> from HDP 2.0.6 through HDP 2.6
> YARN/MR: 3.0.0, copy every script/config/widget/theme/kerberos-descriptor
> from the previous version in common-services and combine with the flattened
> files from HDP 2.0.6 through HDP 2.6
> Finally, any configs with references to /usr/hdp must be replaced by
> {{stack_root}, and configs that use ${hdp.version} must be overriden by the
> HDP 3.0 stack and kept clean in the version used by common-services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19133) hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed unless WebHcat is installed
[
https://issues.apache.org/jira/browse/AMBARI-19133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19133:
--
Attachment: AMBARI-19133_trunk_01.patch
AMBARI-19133_branch-2.5_01.patch
> hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed
> unless WebHcat is installed
>
>
> Key: AMBARI-19133
> URL: https://issues.apache.org/jira/browse/AMBARI-19133
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19133_branch-2.5_01.patch,
> AMBARI-19133_trunk_01.patch
>
>
> {{hadoop.proxyuser.HTTP.hosts}} should not be updated when Hive is installed
> unless WebHcat is installed.
> This is happening because the following block in the Kerberos descriptor is
> at the HIVE service level rather than the WEBHCAT_SERVER component level.
> {code}
> {
> "core-site": {
> "hadoop.proxyuser.HTTP.hosts":
> "${clusterHostInfo/webhcat_server_host}"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19133) hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed unless WebHcat is installed
[
https://issues.apache.org/jira/browse/AMBARI-19133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19133:
--
Status: Patch Available (was: In Progress)
> hadoop.proxyuser.HTTP.hosts should not be updated when Hive is installed
> unless WebHcat is installed
>
>
> Key: AMBARI-19133
> URL: https://issues.apache.org/jira/browse/AMBARI-19133
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Labels: kerberos, kerberos_descriptor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19133_branch-2.5_01.patch,
> AMBARI-19133_trunk_01.patch
>
>
> {{hadoop.proxyuser.HTTP.hosts}} should not be updated when Hive is installed
> unless WebHcat is installed.
> This is happening because the following block in the Kerberos descriptor is
> at the HIVE service level rather than the WEBHCAT_SERVER component level.
> {code}
> {
> "core-site": {
> "hadoop.proxyuser.HTTP.hosts":
> "${clusterHostInfo/webhcat_server_host}"
> }
> },
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18926) Kerberos Wizard UI creates duplicate radio buttons for FreeIPA
[ https://issues.apache.org/jira/browse/AMBARI-18926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733582#comment-15733582 ] Jesus Alvarez commented on AMBARI-18926: [~sangeetar] [~dili] can this be pushed in? > Kerberos Wizard UI creates duplicate radio buttons for FreeIPA > -- > > Key: AMBARI-18926 > URL: https://issues.apache.org/jira/browse/AMBARI-18926 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: trunk, 2.4.0 >Reporter: Jesus Alvarez >Assignee: Jesus Alvarez >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18926-3.patch, kdc_type_duplicate_ipa.png > > > If the enableIPA flag is set to allow Ambari to use FreeIPA as a KDC, the > kerberos wizard will create duplicate radio buttons if a user navigates Back > from step2 to step1 of the kerberos wizard. > Issue here that in step1_controller.js, options.pushObject(ipaOption) will be > called on every loadStep.. including when navigating back to step1 from a > later step. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733456#comment-15733456
]
Hudson commented on AMBARI-19134:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6192 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6192/])
AMBARI-19134 : Storm start is failing due to ClassNotFoundException (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b2a8edf8edf77ae49d4b922590f6d4dcdedc5e4d])
* (edit)
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
* (edit)
ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/HandleConnectExceptionTest.java
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733414#comment-15733414
]
Hudson commented on AMBARI-19134:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #492 (See
[https://builds.apache.org/job/Ambari-branch-2.5/492/])
AMBARI-19134 : Storm start is failing due to ClassNotFoundException (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=82f9401be0feb30ef59e6c02e8715fe4a05f6f9e])
* (edit)
ambari-metrics/ambari-metrics-common/src/test/java/org/apache/hadoop/metrics2/sink/timeline/cache/HandleConnectExceptionTest.java
* (edit)
ambari-metrics/ambari-metrics-common/src/main/java/org/apache/hadoop/metrics2/sink/timeline/AbstractTimelineMetricsSink.java
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19134:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19142) Services page doesn't load after adding Host to existing config group
Dhanya Balasundaran created AMBARI-19142: Summary: Services page doesn't load after adding Host to existing config group Key: AMBARI-19142 URL: https://issues.apache.org/jira/browse/AMBARI-19142 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Dhanya Balasundaran Fix For: 2.5.0 - Deploy cluster and create a custom config group for each service during deployment - Navigate to Hosts page and choose to Add Host - At the Add host wizard - Configurations page, choose the custom config group for each service - Complete deployment - Navigate to Services Page - Page doesnt load -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1576#comment-1576
]
Siddharth Wagle commented on AMBARI-19134:
--
+1 LGTM
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19135) AMS build artifacts are not uploaded to maven central
[
https://issues.apache.org/jira/browse/AMBARI-19135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19135:
---
Fix Version/s: 2.5.0
> AMS build artifacts are not uploaded to maven central
> -
>
> Key: AMBARI-19135
> URL: https://issues.apache.org/jira/browse/AMBARI-19135
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
>
> Error messages on publishing artifacts:
> {code}
> typeIdsignature-staging
> failureMessageMissing Signature:
> '/org/apache/ambari/ambari-metrics-grafana/2.1.0.0.0/ambari-metrics-grafana-2.1.0.0.0.pom.asc'
> does not exist for 'ambari-metrics-grafana-2.1.0.0.0.pom'.
> failureMessageMissing Signature:
> '/org/apache/ambari/ambari-metrics-hadoop-sink/2.4.2.0.0/ambari-metrics-hadoop-sink-2.4.2.0.0.pom.asc'
> does not exist for 'ambari-metrics-hadoop-sink-2.4.2.0.0.pom'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19135) AMS build artifacts are not uploaded to maven central
[
https://issues.apache.org/jira/browse/AMBARI-19135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19135:
---
Affects Version/s: 2.5.0
> AMS build artifacts are not uploaded to maven central
> -
>
> Key: AMBARI-19135
> URL: https://issues.apache.org/jira/browse/AMBARI-19135
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.5.0
>
>
> Error messages on publishing artifacts:
> {code}
> typeIdsignature-staging
> failureMessageMissing Signature:
> '/org/apache/ambari/ambari-metrics-grafana/2.1.0.0.0/ambari-metrics-grafana-2.1.0.0.0.pom.asc'
> does not exist for 'ambari-metrics-grafana-2.1.0.0.0.pom'.
> failureMessageMissing Signature:
> '/org/apache/ambari/ambari-metrics-hadoop-sink/2.4.2.0.0/ambari-metrics-hadoop-sink-2.4.2.0.0.pom.asc'
> does not exist for 'ambari-metrics-hadoop-sink-2.4.2.0.0.pom'.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733203#comment-15733203
]
Aravindan Vijayan commented on AMBARI-19134:
mvn clean test on ambari-metrics
{code}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] utility ... SUCCESS [8.441s]
[INFO] ambari-metrics SUCCESS [0.824s]
[INFO] Ambari Metrics Common . SUCCESS [4.080s]
[INFO] Ambari Metrics Hadoop Sink SUCCESS [5.018s]
[INFO] Ambari Metrics Flume Sink . SUCCESS [4.235s]
[INFO] Ambari Metrics Kafka Sink . SUCCESS [3.183s]
[INFO] Ambari Metrics Storm Sink . SUCCESS [1.458s]
[INFO] Ambari Metrics Storm Sink (Legacy) SUCCESS [1.370s]
[INFO] Ambari Metrics Collector .. SUCCESS [4:11.298s]
[INFO] Ambari Metrics Monitor SUCCESS [4.566s]
[INFO] Ambari Metrics Grafana SUCCESS [4.375s]
[INFO] Ambari Metrics Assembly ... SUCCESS [8.375s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 4:57.441s
[INFO] Finished at: Thu Dec 08 11:29:33 PST 2016
[INFO] Final Memory: 81M/1296M
[INFO]
{code}
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
>
[jira] [Updated] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19134:
---
Attachment: AMBARI-19134-2.patch
Fixed unit test failure.
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19134:
---
Status: Patch Available (was: Open)
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134-2.patch, AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19134) Storm start is failing due to ClassNotFoundException org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
[
https://issues.apache.org/jira/browse/AMBARI-19134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19134:
---
Status: Open (was: Patch Available)
> Storm start is failing due to ClassNotFoundException
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> ---
>
> Key: AMBARI-19134
> URL: https://issues.apache.org/jira/browse/AMBARI-19134
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19134.patch
>
>
> Storm nimbus start is failing due to following class not found error:
> {code}
> 2016-12-06 07:28:10.116 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: Could not instantiate a class listed in config
> under section storm.cluster.metrics.consumer.register with fully qualified
> name org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at clojure.lang.Reflector.invokeMatchingMethod(Reflector.java:93)
> at
> clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:313)
> at
> org.apache.storm.daemon.nimbus$fn__9762$exec_fn__3656__auto9763.invoke(nimbus.clj:2392)
> at clojure.lang.AFn.applyToHelper(AFn.java:156)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at clojure.core$apply.invoke(core.clj:630)
> at
> org.apache.storm.daemon.nimbus$fn__9762$service_handler__9798.doInvoke(nimbus.clj:2369)
> at clojure.lang.RestFn.invoke(RestFn.java:421)
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2458)
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2491)
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2514)
> at clojure.lang.AFn.applyToHelper(AFn.java:152)
> at clojure.lang.AFn.applyTo(AFn.java:144)
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsReporter
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:190)
> at
> org.apache.storm.metric.ClusterMetricsConsumerExecutor.prepare(ClusterMetricsConsumerExecutor.java:48)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19141) Refinements for AMS whitelisting.
[ https://issues.apache.org/jira/browse/AMBARI-19141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-19141: --- Issue Type: Task (was: Bug) > Refinements for AMS whitelisting. > - > > Key: AMBARI-19141 > URL: https://issues.apache.org/jira/browse/AMBARI-19141 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.5.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.0 > > > Must Haves > Ability to specify metric expressions for whitelisting. > Ability to whitelist/blacklist metrics from entire sources (APP_IDs) > Nice to Haves > Ability to update metric whitelist through AMS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19141) Refinements for AMS whitelisting.
Aravindan Vijayan created AMBARI-19141: -- Summary: Refinements for AMS whitelisting. Key: AMBARI-19141 URL: https://issues.apache.org/jira/browse/AMBARI-19141 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.5.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.5.0 Must Haves Ability to specify metric expressions for whitelisting. Ability to whitelist/blacklist metrics from entire sources (APP_IDs) Nice to Haves Ability to update metric whitelist through AMS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[
https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733171#comment-15733171
]
Hadoop QA commented on AMBARI-19140:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842375/AMBARI-19140.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/9594//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9594//console
This message is automatically generated.
> Ambari Server symbolic links has double // when root dir is just /
> --
>
> Key: AMBARI-19140
> URL: https://issues.apache.org/jira/browse/AMBARI-19140
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Di Li
>Assignee: Di Li
> Attachments: AMBARI-19140.patch
>
>
> Notice the "//" in the symbolic link , where it could have been trimmed to be
> just one leading "/"
> [root]# ll /usr/sbin/ambari-server
> lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server ->
> //etc/init.d/ambari-server
> [root]# clear
> [root]# ll
> total 20
> drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent
> lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons ->
> //usr/lib/ambari-server/lib/ambari_commons
> lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 ->
> //usr/lib/ambari-server/lib/ambari_jinja2
> drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server
> lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson ->
> //usr/lib/ambari-server/lib/ambari_simplejson
> lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management ->
> //usr/lib/ambari-server/lib/resource_management
> drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
[
https://issues.apache.org/jira/browse/AMBARI-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15733090#comment-15733090
]
Hadoop QA commented on AMBARI-19139:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842383/AMBARI-19139.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/9593//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9593//console
This message is automatically generated.
> UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but
> before was 'Falcon Web UI'
> ---
>
> Key: AMBARI-19139
> URL: https://issues.apache.org/jira/browse/AMBARI-19139
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19139.patch
>
>
> STR:
> 1)Deploy cluster
> 2)Check Quick Links from Falcon
> *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon
> Dashboard), but before was Falcon Web UI
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19041: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19041.patch > > > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732964#comment-15732964 ] Hudson commented on AMBARI-19066: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6191 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6191/]) AMBARI-19066. Add more logging around status command report processing (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a27c0dd34608cd99fc47d4a6b2e2ab532f0e03eb]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/AgentRequests.java > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18323_v2.patch, AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732951#comment-15732951 ] Hudson commented on AMBARI-19066: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #491 (See [https://builds.apache.org/job/Ambari-branch-2.5/491/]) AMBARI-19066. Add more logging around status command report processing (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=51c6ef9e157991d96535ff6e0b86a6e9b8878883]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/AgentRequests.java > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18323_v2.patch, AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18937) Allow generic Service Upgrade Packs for all targets
[ https://issues.apache.org/jira/browse/AMBARI-18937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-18937: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Allow generic Service Upgrade Packs for all targets > --- > > Key: AMBARI-18937 > URL: https://issues.apache.org/jira/browse/AMBARI-18937 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18937.patch > > > Currently, a custom service can participate in RU/EU only if it adds an > Upgrade Pack for every target of a stack. If there is a case of the Upgrade > Pack ALWAYS being the same no matter the version, then only one file should > be sufficient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
[ https://issues.apache.org/jira/browse/AMBARI-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732948#comment-15732948 ] Aleksandr Kovalenko commented on AMBARI-19139: -- +1 for the patch > UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but > before was 'Falcon Web UI' > --- > > Key: AMBARI-19139 > URL: https://issues.apache.org/jira/browse/AMBARI-19139 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19139.patch > > > STR: > 1)Deploy cluster > 2)Check Quick Links from Falcon > *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon > Dashboard), but before was Falcon Web UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
[ https://issues.apache.org/jira/browse/AMBARI-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19139: - Status: Patch Available (was: Open) > UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but > before was 'Falcon Web UI' > --- > > Key: AMBARI-19139 > URL: https://issues.apache.org/jira/browse/AMBARI-19139 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19139.patch > > > STR: > 1)Deploy cluster > 2)Check Quick Links from Falcon > *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon > Dashboard), but before was Falcon Web UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
[ https://issues.apache.org/jira/browse/AMBARI-19139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-19139: - Attachment: AMBARI-19139.patch > UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but > before was 'Falcon Web UI' > --- > > Key: AMBARI-19139 > URL: https://issues.apache.org/jira/browse/AMBARI-19139 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19139.patch > > > STR: > 1)Deploy cluster > 2)Check Quick Links from Falcon > *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon > Dashboard), but before was Falcon Web UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732767#comment-15732767 ] Hudson commented on AMBARI-19066: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #490 (See [https://builds.apache.org/job/Ambari-branch-2.5/490/]) Revert "AMBARI-19066. Add more logging around status command report (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8bdb7454690b1af51402a996f63958c004c6ec22]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/AgentRequests.java > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18323_v2.patch, AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732765#comment-15732765 ] Hudson commented on AMBARI-19041: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #490 (See [https://builds.apache.org/job/Ambari-branch-2.5/490/]) AMBARI-19041 Choose services page select/deselect all services not (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=59f520b85df153616cc2010b23542311e59b50cb]) * (edit) ambari-web/app/models/stack_service.js * (edit) ambari-web/test/models/stack_service_test.js > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19041.patch > > > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[ https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19140: --- Status: Patch Available (was: Open) > Ambari Server symbolic links has double // when root dir is just / > -- > > Key: AMBARI-19140 > URL: https://issues.apache.org/jira/browse/AMBARI-19140 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19140.patch > > > Notice the "//" in the symbolic link , where it could have been trimmed to be > just one leading "/" > [root]# ll /usr/sbin/ambari-server > lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> > //etc/init.d/ambari-server > [root]# clear > [root]# ll > total 20 > drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent > lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> > //usr/lib/ambari-server/lib/ambari_commons > lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> > //usr/lib/ambari-server/lib/ambari_jinja2 > drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server > lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> > //usr/lib/ambari-server/lib/ambari_simplejson > lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> > //usr/lib/ambari-server/lib/resource_management > drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
[ https://issues.apache.org/jira/browse/AMBARI-19140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-19140: --- Attachment: AMBARI-19140.patch > Ambari Server symbolic links has double // when root dir is just / > -- > > Key: AMBARI-19140 > URL: https://issues.apache.org/jira/browse/AMBARI-19140 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Di Li >Assignee: Di Li > Attachments: AMBARI-19140.patch > > > Notice the "//" in the symbolic link , where it could have been trimmed to be > just one leading "/" > [root]# ll /usr/sbin/ambari-server > lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> > //etc/init.d/ambari-server > [root]# clear > [root]# ll > total 20 > drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent > lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> > //usr/lib/ambari-server/lib/ambari_commons > lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> > //usr/lib/ambari-server/lib/ambari_jinja2 > drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server > lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> > //usr/lib/ambari-server/lib/ambari_simplejson > lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> > //usr/lib/ambari-server/lib/resource_management > drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19138) Option for getting heap dump for Hive and Tez services.
[
https://issues.apache.org/jira/browse/AMBARI-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732775#comment-15732775
]
Hadoop QA commented on AMBARI-19138:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842339/AMBARI-19138.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/9592//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9592//console
This message is automatically generated.
> Option for getting heap dump for Hive and Tez services.
> ---
>
> Key: AMBARI-19138
> URL: https://issues.apache.org/jira/browse/AMBARI-19138
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19138.patch
>
>
> We need to add the heap dump option for:
> - All Hive services (Hive1/HiveServer2, Hive2/HiveServer2 and Metastore):
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option appended to "Advance hive-env" -> hive-env-template ->
> HADOOP_CLIENT_OPTS environment variable
> - HSI YARN jobs:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to "Advanced hive-interactive-env" -> Llap app java opts. Logs
> will be generated at: /<'Configurable location
> provided'>/java_.hprof on the nodes that failed with OOM.
> - Tez component:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to tez.am.launch.cmd-opts for AM OOM and
> tez.task.launch.cmd-opts for task OOM.
> ** 'Configurable location provided' should be one config where user can
> change the location and consumable by all others.
> Further, whether to keep the heap dump option ENABLED or DISABLED should be
> configurable via Ambari. [~carter] to confirm for this. By default, option
> should be DISABLED.
> ** ENABLING/DISABLING of option will require the above components
> RESATARt for change to take effect.
> ** permissions for dump file can be 600 for :.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19075) Cookie management for Ambari LogSearch Integration
[ https://issues.apache.org/jira/browse/AMBARI-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732766#comment-15732766 ] Hudson commented on AMBARI-19075: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #490 (See [https://builds.apache.org/job/Ambari-branch-2.5/490/]) AMBARI-19075. Cookie management for Ambari LogSearch Integration (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a9a05f76f07df992e4216a2c9e27736239bfdb9a]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImplTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingCookieStore.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/web/listener/LogSearchSessionListener.java * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/LogSearch.java * (edit) ambari-logsearch/docker/test-config/logsearch/log4j.xml * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-log4j.xml.j2 * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImpl.java > Cookie management for Ambari LogSearch Integration > -- > > Key: AMBARI-19075 > URL: https://issues.apache.org/jira/browse/AMBARI-19075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19075.patch > > > Ambari server opens a lot of sessions with LogSearch Portal, because the > integration code does not contain any session handling -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[ https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732769#comment-15732769 ] Hudson commented on AMBARI-18450: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #490 (See [https://builds.apache.org/job/Ambari-branch-2.5/490/]) AMBARI-18450. Putting a service or process in Maintenance Mode does not (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4f3a67d987d759f4ecf28f163cf994a373f4a2ff]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list > --- > > Key: AMBARI-18450 > URL: https://issues.apache.org/jira/browse/AMBARI-18450 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: Vitaly Brodetskyi >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18450.patch > > > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19140) Ambari Server symbolic links has double // when root dir is just /
Di Li created AMBARI-19140: -- Summary: Ambari Server symbolic links has double // when root dir is just / Key: AMBARI-19140 URL: https://issues.apache.org/jira/browse/AMBARI-19140 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.5.0 Reporter: Di Li Assignee: Di Li Notice the "//" in the symbolic link , where it could have been trimmed to be just one leading "/" [root]# ll /usr/sbin/ambari-server lrwxrwxrwx 1 root root 26 Dec 5 11:27 /usr/sbin/ambari-server -> //etc/init.d/ambari-server [root]# clear [root]# ll total 20 drwxrwxr-x 4 root root 8192 Dec 5 11:32 ambari_agent lrwxrwxrwx 1 root root 42 Dec 5 11:27 ambari_commons -> //usr/lib/ambari-server/lib/ambari_commons lrwxrwxrwx 1 root root 41 Dec 5 11:27 ambari_jinja2 -> //usr/lib/ambari-server/lib/ambari_jinja2 drwxrwxr-x 2 root root 4096 Dec 5 11:28 ambari_server lrwxrwxrwx 1 root root 45 Dec 5 11:27 ambari_simplejson -> //usr/lib/ambari-server/lib/ambari_simplejson lrwxrwxrwx 1 root root 47 Dec 5 11:27 resource_management -> //usr/lib/ambari-server/lib/resource_management drwxr-xr-x 5 ams hadoop 83 Dec 6 09:26 resource_monitoring -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19139) UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI'
Antonenko Alexander created AMBARI-19139: Summary: UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was 'Falcon Web UI' Key: AMBARI-19139 URL: https://issues.apache.org/jira/browse/AMBARI-19139 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.5.0 STR: 1)Deploy cluster 2)Check Quick Links from Falcon *Actual result:* UI: Quick Link from Falcon has not correct name (Now: Falcon Dashboard), but before was Falcon Web UI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19131) Manage Journalnode Wizard: incorrect number of installed JournalNodes
[ https://issues.apache.org/jira/browse/AMBARI-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-19131: - Resolution: Fixed Status: Resolved (was: Patch Available) > Manage Journalnode Wizard: incorrect number of installed JournalNodes > - > > Key: AMBARI-19131 > URL: https://issues.apache.org/jira/browse/AMBARI-19131 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.5.0 > > Attachments: AMBARI-19131.patch > > > STR: > 1. Open Manage Journalnode Wizard. > 2. Refresh page on the step1. > It displays current label beside 2 of 4 journalnodes, but actually all 4 > components are currently installed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19127) hbase_regionserver_shutdown_timeout should be editable all the time
[
https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732708#comment-15732708
]
Hadoop QA commented on AMBARI-19127:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842336/AMBARI-19127.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/9591//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9591//console
This message is automatically generated.
> hbase_regionserver_shutdown_timeout should be editable all the time
> ---
>
> Key: AMBARI-19127
> URL: https://issues.apache.org/jira/browse/AMBARI-19127
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19127.patch, AMBARI-19127.patch
>
>
> hbase_regionserver_shutdown_timeout should be editable any time. Its now only
> editable during install.
>
>
>
>
> hbase_regionserver_shutdown_timeout
> 30
> HBase RegionServer shutdown timeout
>
> After this number of seconds waiting for graceful stop of HBase Master it
> will be forced to exit with SIGKILL.
> The timeout is introduced because there is a known bug when from time to
> time HBase RegionServer hangs forever on stop if NN safemode is on.
>
>
> int
> false
> true
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs
[ https://issues.apache.org/jira/browse/AMBARI-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732677#comment-15732677 ] Hudson commented on AMBARI-19058: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #489 (See [https://builds.apache.org/job/Ambari-branch-2.5/489/]) AMBARI-19058. Perf: Deploy 3000 Agent cluster and find perf bugs. Part (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1238674fa500c67ea11d6e929821587043eb6387]) * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > Perf: Deploy 3000 Agent cluster and find perf bugs > -- > > Key: AMBARI-19058 > URL: https://issues.apache.org/jira/browse/AMBARI-19058 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-19058_part1.patch, AMBARI-19058_part2.patch > > > Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and > start finding perf bugs in the following areas. > Agent registration (batches of 600 at a time are still very slow) > Alerts > Commands like starting/restarting/rolling restart, etc. > Memory leaks after letting it run for a week? > We may need to also run a memory profiler on the java process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[ https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732664#comment-15732664 ] Hudson commented on AMBARI-18450: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6190 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6190/]) AMBARI-18450. Putting a service or process in Maintenance Mode does not (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd4a02fb432013147ae7182d6a8286f9c89845a9]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list > --- > > Key: AMBARI-18450 > URL: https://issues.apache.org/jira/browse/AMBARI-18450 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: Vitaly Brodetskyi >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18450.patch > > > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[
https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732648#comment-15732648
]
Hadoop QA commented on AMBARI-19041:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842342/AMBARI-19041.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/9590//console
This message is automatically generated.
> Choose services page select/deselect all services not working while adding
> smartsense to the cluster
>
>
> Key: AMBARI-19041
> URL: https://issues.apache.org/jira/browse/AMBARI-19041
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19041.patch
>
>
> After deleting smartsense, on adding smartsense, on choose services page,
> select/deselect all button does not work as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[
https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732646#comment-15732646
]
Hadoop QA commented on AMBARI-19104:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842361/AMBARI-19104.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/9589//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9589//console
This message is automatically generated.
> Ambari Server - LogSearch integration code SSL support
> --
>
> Key: AMBARI-19104
> URL: https://issues.apache.org/jira/browse/AMBARI-19104
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19104.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19075) Cookie management for Ambari LogSearch Integration
[ https://issues.apache.org/jira/browse/AMBARI-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732599#comment-15732599 ] Hudson commented on AMBARI-19075: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6189 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6189/]) AMBARI-19075. Cookie management for Ambari LogSearch Integration (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8fa1e8bab925bb438311143d710879ac29ea0706]) * (edit) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/LogSearch.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LoggingRequestHelperImplTest.java * (add) ambari-logsearch/ambari-logsearch-portal/src/main/java/org/apache/ambari/logsearch/web/listener/LogSearchSessionListener.java * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/logging/LoggingCookieStore.java * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/properties/logsearch-log4j.xml.j2 * (edit) ambari-logsearch/docker/test-config/logsearch/log4j.xml > Cookie management for Ambari LogSearch Integration > -- > > Key: AMBARI-19075 > URL: https://issues.apache.org/jira/browse/AMBARI-19075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19075.patch > > > Ambari server opens a lot of sessions with LogSearch Portal, because the > integration code does not contain any session handling -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[ https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19104: -- Status: Open (was: Patch Available) > Ambari Server - LogSearch integration code SSL support > -- > > Key: AMBARI-19104 > URL: https://issues.apache.org/jira/browse/AMBARI-19104 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19104.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[ https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19104: -- Status: Patch Available (was: Open) > Ambari Server - LogSearch integration code SSL support > -- > > Key: AMBARI-19104 > URL: https://issues.apache.org/jira/browse/AMBARI-19104 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19104.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[ https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19104: -- Attachment: (was: AMBARI-19104.patch) > Ambari Server - LogSearch integration code SSL support > -- > > Key: AMBARI-19104 > URL: https://issues.apache.org/jira/browse/AMBARI-19104 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19104.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18450) Putting a service or process in Maintenance Mode doesn't take it off of the "Restart All Required" list
[ https://issues.apache.org/jira/browse/AMBARI-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18450: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list > --- > > Key: AMBARI-18450 > URL: https://issues.apache.org/jira/browse/AMBARI-18450 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: amarnathreddy >Assignee: Vitaly Brodetskyi >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-18450.patch > > > Putting a service or process in Maintenance Mode doesn't take it off of the > "Restart All Required" list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19104) Ambari Server - LogSearch integration code SSL support
[ https://issues.apache.org/jira/browse/AMBARI-19104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19104: -- Attachment: AMBARI-19104.patch > Ambari Server - LogSearch integration code SSL support > -- > > Key: AMBARI-19104 > URL: https://issues.apache.org/jira/browse/AMBARI-19104 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19104.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19075) Cookie management for Ambari LogSearch Integration
[
https://issues.apache.org/jira/browse/AMBARI-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-19075:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk:
{code:java}
commit 8fa1e8bab925bb438311143d710879ac29ea0706
Author: oleewere
Date: Thu Dec 8 00:02:50 2016 +0100
AMBARI-19075. Cookie management for Ambari LogSearch Integration (oleewere)
Change-Id: I67395f02705d296e7b1b0dced2fffde69d92482d
{code}
committed to branch-2.5:
{code:java}
commit a9a05f76f07df992e4216a2c9e27736239bfdb9a
Author: oleewere
Date: Thu Dec 8 00:02:50 2016 +0100
AMBARI-19075. Cookie management for Ambari LogSearch Integration (oleewere)
Change-Id: I67395f02705d296e7b1b0dced2fffde69d92482d
{code}
> Cookie management for Ambari LogSearch Integration
> --
>
> Key: AMBARI-19075
> URL: https://issues.apache.org/jira/browse/AMBARI-19075
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch, ambari-server
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19075.patch
>
>
> Ambari server opens a lot of sessions with LogSearch Portal, because the
> integration code does not contain any session handling
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19075) Cookie management for Ambari LogSearch Integration
[ https://issues.apache.org/jira/browse/AMBARI-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19075: -- Attachment: (was: AMBARI-19075.patch) > Cookie management for Ambari LogSearch Integration > -- > > Key: AMBARI-19075 > URL: https://issues.apache.org/jira/browse/AMBARI-19075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19075.patch > > > Ambari server opens a lot of sessions with LogSearch Portal, because the > integration code does not contain any session handling -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19075) Cookie management for Ambari LogSearch Integration
[ https://issues.apache.org/jira/browse/AMBARI-19075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19075: -- Attachment: AMBARI-19075.patch > Cookie management for Ambari LogSearch Integration > -- > > Key: AMBARI-19075 > URL: https://issues.apache.org/jira/browse/AMBARI-19075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19075.patch, AMBARI-19075.patch > > > Ambari server opens a lot of sessions with LogSearch Portal, because the > integration code does not contain any session handling -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732458#comment-15732458 ] Hudson commented on AMBARI-19066: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6188 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6188/]) Revert "AMBARI-19066. Add more logging around status command report (smagyari: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3ffc95607adb2ecd1b2a3ccc84db475351e9a8d3]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/agent/AgentRequests.java > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18323_v2.patch, AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19066: Attachment: AMBARI-18323_v2.patch > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-18323_v2.patch, AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732405#comment-15732405 ] Hudson commented on AMBARI-19041: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6187 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6187/]) AMBARI-19041 Choose services page select/deselect all services not (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=18d1b0cd4acccf04de6f963274d6f4662f92a966]) * (edit) ambari-web/app/models/stack_service.js * (edit) ambari-web/test/models/stack_service_test.js > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19041.patch > > > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-19066) Add more logging around status command report processing on server side
[ https://issues.apache.org/jira/browse/AMBARI-19066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari reopened AMBARI-19066: - > Add more logging around status command report processing on server side > --- > > Key: AMBARI-19066 > URL: https://issues.apache.org/jira/browse/AMBARI-19066 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 2.5.0 > > Attachments: AMBARI-19066.patch > > > Add more INFO level logging in HeartbeatProcessor.processStatusReports, > AgentRequests.setExecutionDetailsRequest to be able to trace status command > report processing and agent request for execution command details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732303#comment-15732303 ] Andrii Babiichuk commented on AMBARI-19041: --- Committed to branch-2.5 and trunk > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19041.patch > > > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[
https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732296#comment-15732296
]
Hadoop QA commented on AMBARI-19041:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842342/AMBARI-19041.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9588//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9588//console
This message is automatically generated.
> Choose services page select/deselect all services not working while adding
> smartsense to the cluster
>
>
> Key: AMBARI-19041
> URL: https://issues.apache.org/jira/browse/AMBARI-19041
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19041.patch
>
>
> After deleting smartsense, on adding smartsense, on choose services page,
> select/deselect all button does not work as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (AMBARI-18738) Perf: Allow components to report their version using distro-select and change configs using conf-select
[ https://issues.apache.org/jira/browse/AMBARI-18738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko reassigned AMBARI-18738: --- Assignee: Dmitry Lysnichenko (was: Alejandro Fernandez) > Perf: Allow components to report their version using distro-select and change > configs using conf-select > --- > > Key: AMBARI-18738 > URL: https://issues.apache.org/jira/browse/AMBARI-18738 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Dmitry Lysnichenko > Fix For: 2.5.0 > > > In preparation for RU/EU, the components will actually need to call > distro-select and conf-select in order to change their symlinks and config > directories. > Each Ambari Agent will have a version.txt file and a symlinks.txt file that > will show the versions currently installed on that agent and the symlinks for > each component. > This will allow EU/RU to change these txt files in order to simulate versions > being installed and switched. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19041: -- Attachment: AMBARI-19041.patch > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19041.patch > > > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19041) Choose services page select/deselect all services not working while adding smartsense to the cluster
[ https://issues.apache.org/jira/browse/AMBARI-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-19041: -- Status: Patch Available (was: Open) > Choose services page select/deselect all services not working while adding > smartsense to the cluster > > > Key: AMBARI-19041 > URL: https://issues.apache.org/jira/browse/AMBARI-19041 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Rathod >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19041.patch > > > After deleting smartsense, on adding smartsense, on choose services page, > select/deselect all button does not work as expected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19058) Perf: Deploy 3000 Agent cluster and find perf bugs
[ https://issues.apache.org/jira/browse/AMBARI-19058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732197#comment-15732197 ] Hudson commented on AMBARI-19058: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6186 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6186/]) AMBARI-19058. Perf: Deploy 3000 Agent cluster and find perf bugs. Part (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=75e182eb19d6c867dd16377c9c4e1c792c568395]) * (edit) contrib/utils/perf/deploy-gce-perf-cluster.py > Perf: Deploy 3000 Agent cluster and find perf bugs > -- > > Key: AMBARI-19058 > URL: https://issues.apache.org/jira/browse/AMBARI-19058 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 2.5.0 > > Attachments: AMBARI-19058_part1.patch, AMBARI-19058_part2.patch > > > Use Ambari 2.5 branch instead of trunk to deploy 2000-3000 agents on GCE and > start finding perf bugs in the following areas. > Agent registration (batches of 600 at a time are still very slow) > Alerts > Commands like starting/restarting/rolling restart, etc. > Memory leaks after letting it run for a week? > We may need to also run a memory profiler on the java process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19127) hbase_regionserver_shutdown_timeout should be editable all the time
[
https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732145#comment-15732145
]
Hadoop QA commented on AMBARI-19127:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12842336/AMBARI-19127.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/9587//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9587//console
This message is automatically generated.
> hbase_regionserver_shutdown_timeout should be editable all the time
> ---
>
> Key: AMBARI-19127
> URL: https://issues.apache.org/jira/browse/AMBARI-19127
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19127.patch, AMBARI-19127.patch
>
>
> hbase_regionserver_shutdown_timeout should be editable any time. Its now only
> editable during install.
>
>
>
>
> hbase_regionserver_shutdown_timeout
> 30
> HBase RegionServer shutdown timeout
>
> After this number of seconds waiting for graceful stop of HBase Master it
> will be forced to exit with SIGKILL.
> The timeout is introduced because there is a known bug when from time to
> time HBase RegionServer hangs forever on stop if NN safemode is on.
>
>
> int
> false
> true
>
>
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18737) Perf: Allow Kerberizing the PERF stack
[ https://issues.apache.org/jira/browse/AMBARI-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732121#comment-15732121 ] Dmytro Sen commented on AMBARI-18737: - Failed unit test were failing before this commit > Perf: Allow Kerberizing the PERF stack > -- > > Key: AMBARI-18737 > URL: https://issues.apache.org/jira/browse/AMBARI-18737 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-18737.patch, AMBARI-18737_2.patch > > > Using multiple Ambari Agents per Host, each will need its unique > /etc/security folder inside its home directory. In order to Kerberize the > PERF stack, we will need to install an actual KDC and have the services > actually kinit with their principals and keytabs. > Because the PERF stack will not actually install any packages, it may have to > create user accounts. > The goal is to be able to run the Kerberos Wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19138) Option for getting heap dump for Hive and Tez services.
[
https://issues.apache.org/jira/browse/AMBARI-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19138:
-
Attachment: AMBARI-19138.patch
> Option for getting heap dump for Hive and Tez services.
> ---
>
> Key: AMBARI-19138
> URL: https://issues.apache.org/jira/browse/AMBARI-19138
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19138.patch
>
>
> We need to add the heap dump option for:
> - All Hive services (Hive1/HiveServer2, Hive2/HiveServer2 and Metastore):
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option appended to "Advance hive-env" -> hive-env-template ->
> HADOOP_CLIENT_OPTS environment variable
> - HSI YARN jobs:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to "Advanced hive-interactive-env" -> Llap app java opts. Logs
> will be generated at: /<'Configurable location
> provided'>/java_.hprof on the nodes that failed with OOM.
> - Tez component:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to tez.am.launch.cmd-opts for AM OOM and
> tez.task.launch.cmd-opts for task OOM.
> ** 'Configurable location provided' should be one config where user can
> change the location and consumable by all others.
> Further, whether to keep the heap dump option ENABLED or DISABLED should be
> configurable via Ambari. [~carter] to confirm for this. By default, option
> should be DISABLED.
> ** ENABLING/DISABLING of option will require the above components
> RESATARt for change to take effect.
> ** permissions for dump file can be 600 for :.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19138) Option for getting heap dump for Hive and Tez services.
[
https://issues.apache.org/jira/browse/AMBARI-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19138:
-
Status: Patch Available (was: Open)
> Option for getting heap dump for Hive and Tez services.
> ---
>
> Key: AMBARI-19138
> URL: https://issues.apache.org/jira/browse/AMBARI-19138
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0
>
> Attachments: AMBARI-19138.patch
>
>
> We need to add the heap dump option for:
> - All Hive services (Hive1/HiveServer2, Hive2/HiveServer2 and Metastore):
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option appended to "Advance hive-env" -> hive-env-template ->
> HADOOP_CLIENT_OPTS environment variable
> - HSI YARN jobs:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to "Advanced hive-interactive-env" -> Llap app java opts. Logs
> will be generated at: /<'Configurable location
> provided'>/java_.hprof on the nodes that failed with OOM.
> - Tez component:
> {code}
> -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
> 'Configurable location provided'>
> {code}
> option added to tez.am.launch.cmd-opts for AM OOM and
> tez.task.launch.cmd-opts for task OOM.
> ** 'Configurable location provided' should be one config where user can
> change the location and consumable by all others.
> Further, whether to keep the heap dump option ENABLED or DISABLED should be
> configurable via Ambari. [~carter] to confirm for this. By default, option
> should be DISABLED.
> ** ENABLING/DISABLING of option will require the above components
> RESATARt for change to take effect.
> ** permissions for dump file can be 600 for :.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19087) Clean up how dfs.cluster.administrators is handled wrt user/group creation
[ https://issues.apache.org/jira/browse/AMBARI-19087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732108#comment-15732108 ] Hudson commented on AMBARI-19087: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6185 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6185/]) AMBARI-19087. Clean up how dfs.cluster.administrators is handled wrt (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c4728f2f71f899ca1be98da0a85bdfcb514e07c8]) * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-ANY/scripts/shared_initialization.py > Clean up how dfs.cluster.administrators is handled wrt user/group creation > -- > > Key: AMBARI-19087 > URL: https://issues.apache.org/jira/browse/AMBARI-19087 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19087.patch > > > dfs.cluster.administrators handles values of the following format: > > > CL for the admins, this configuration is used to control who can access > the default servlets in the namenode, etc. The value should be a comma > separated list of users and groups. The user list comes first and is > separated by a space followed by the group list, e.g. "user1,user2 > group1,group2". Both users and groups are optional, so "user1", " group1", > "", "user1 group1", "user1,user2 group1,group2" are all valid (note the > leading space in " group1"). '*' grants access to all users and groups, e.g. > '*', '* ' and ' *' are all valid. > > Ambari cannot handle * value correctly it will try to create a group or user > named '*'. > Also Ambari cannot correctly create groups if there are multiple spaces > instead of one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18737) Perf: Allow Kerberizing the PERF stack
[ https://issues.apache.org/jira/browse/AMBARI-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732107#comment-15732107 ] Hudson commented on AMBARI-18737: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6185 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6185/]) AMBARI-18737 Perf: Allow Kerberizing the PERF stack (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cdf65c3450c02f96760fab940a074eaa8583be70]) * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/kerberos.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/journalnode.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/configuration/grumpy-site.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/scripts/hbase_regionserver.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/scripts/snow_white.py * (edit) ambari-common/src/main/python/resource_management/libraries/script/dummy.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/scripts/hbase_master.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/nfsgateway.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/krb5-conf.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/nodemanager.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/resourcemanager.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/configuration/sleepy-site.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/package/scripts/dwarf.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_client.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/configuration/cluster-env.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/datanode.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/scripts/phoenix_queryserver.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/service_check.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/package/scripts/dwarf.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/application_timeline_server.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/templates/krb5_conf.j2 * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/utils.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/kerberos.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/historyserver.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/snamenode.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/scripts/dwarf.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/package/scripts/zookeeper_server.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/namenode.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_common.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/params.py > Perf: Allow Kerberizing the PERF stack > -- > > Key: AMBARI-18737 > URL: https://issues.apache.org/jira/browse/AMBARI-18737 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix
[jira] [Commented] (AMBARI-18737) Perf: Allow Kerberizing the PERF stack
[ https://issues.apache.org/jira/browse/AMBARI-18737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732095#comment-15732095 ] Hudson commented on AMBARI-18737: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #488 (See [https://builds.apache.org/job/Ambari-branch-2.5/488/]) AMBARI-18737 Perf: Allow Kerberizing the PERF stack (dsen) (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=338c2c5be000fb6a681bc5c82f8c4cb20c192500]) * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/configuration/snow-site.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/journalnode.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/kerberos.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_common.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/service_check.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/kerberos-env.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/nfsgateway.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/kerberos.json * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/resourcemanager.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/configuration/happy-site.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/package/scripts/dwarf.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/status_params.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/configuration/sleepy-site.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/scripts/hbase_master.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/package/scripts/dwarf.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/templates/krb5_conf.j2 * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/application_timeline_server.py * (edit) ambari-common/src/main/python/resource_management/libraries/script/dummy.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/datanode.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SNOW/package/scripts/snow_white.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/configuration/krb5-conf.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/HAPPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/nodemanager.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/snamenode.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/configuration/cluster-env.xml * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/utils.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/package/scripts/dwarf.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/YARN/package/scripts/historyserver.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/kerberos_client.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/package/scripts/params.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/SLEEPY/kerberos.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/scripts/hbase_regionserver.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HBASE/package/scripts/phoenix_queryserver.py * (add) ambari-server/src/main/resources/stacks/PERF/1.0/services/KERBEROS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/ZOOKEEPER/package/scripts/zookeeper_server.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/HDFS/package/scripts/namenode.py * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/GRUMPY/configuration/grumpy-site.xml > Perf: Allow Kerberizing the PERF stack > -- > > Key: AMBARI-18737 > URL: https://issues.apache.org/jira/browse/AMBARI-18737 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Dmytro Sen > Fix For: 2
[jira] [Updated] (AMBARI-19127) hbase_regionserver_shutdown_timeout should be editable all the time
[ https://issues.apache.org/jira/browse/AMBARI-19127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-19127: - Attachment: AMBARI-19127.patch > hbase_regionserver_shutdown_timeout should be editable all the time > --- > > Key: AMBARI-19127 > URL: https://issues.apache.org/jira/browse/AMBARI-19127 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-19127.patch, AMBARI-19127.patch > > > hbase_regionserver_shutdown_timeout should be editable any time. Its now only > editable during install. > > > > > hbase_regionserver_shutdown_timeout > 30 > HBase RegionServer shutdown timeout > > After this number of seconds waiting for graceful stop of HBase Master it > will be forced to exit with SIGKILL. > The timeout is introduced because there is a known bug when from time to > time HBase RegionServer hangs forever on stop if NN safemode is on. > > > int > false > true > > > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19138) Option for getting heap dump for Hive and Tez services.
Swapan Shridhar created AMBARI-19138:
Summary: Option for getting heap dump for Hive and Tez services.
Key: AMBARI-19138
URL: https://issues.apache.org/jira/browse/AMBARI-19138
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.1
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Fix For: 2.5.0
We need to add the heap dump option for:
- All Hive services (Hive1/HiveServer2, Hive2/HiveServer2 and Metastore):
{code}
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
'Configurable location provided'>
{code}
option appended to "Advance hive-env" -> hive-env-template ->
HADOOP_CLIENT_OPTS environment variable
- HSI YARN jobs:
{code}
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
'Configurable location provided'>
{code}
option added to "Advanced hive-interactive-env" -> Llap app java opts. Logs
will be generated at: /<'Configurable location
provided'>/java_.hprof on the nodes that failed with OOM.
- Tez component:
{code}
-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<'/tmp/' by default or
'Configurable location provided'>
{code}
option added to tez.am.launch.cmd-opts for AM OOM and tez.task.launch.cmd-opts
for task OOM.
** 'Configurable location provided' should be one config where user can
change the location and consumable by all others.
Further, whether to keep the heap dump option ENABLED or DISABLED should be
configurable via Ambari. [~carter] to confirm for this. By default, option
should be DISABLED.
** ENABLING/DISABLING of option will require the above components RESATARt
for change to take effect.
** permissions for dump file can be 600 for :.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
