[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error

[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: AMBARI-18441-02.patch > upgrade ambari to 2.1.1 error > -

[jira] [Commented] (AMBARI-18818) Config changes for Atlas to Support KnoxSSO Authentication

[ https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669520#comment-15669520 ] Hudson commented on AMBARI-18818: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6022 (See

[jira] [Commented] (AMBARI-18818) Config changes for Atlas to Support KnoxSSO Authentication

[ https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669502#comment-15669502 ] Hudson commented on AMBARI-18818: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #333 (See

[jira] [Commented] (AMBARI-18476) Ambari UI changes to support PAM authentication

[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669499#comment-15669499 ] Hadoop QA commented on AMBARI-18476: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication

[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Attachment: AMBARI-18476_2.5patch patch for 2.5 > Ambari UI changes to support

[jira] [Updated] (AMBARI-18818) Config changes for Atlas to Support KnoxSSO Authentication

[ https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18818: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed: trunk -

[jira] [Commented] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes

[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669066#comment-15669066 ] Di Li commented on AMBARI-18852: The test failure listed below is unrelated to the ambari agent python

[jira] [Commented] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669028#comment-15669028 ] Hudson commented on AMBARI-18866: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6021 (See

[jira] [Commented] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15669003#comment-15669003 ] Hudson commented on AMBARI-18866: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #332 (See

[jira] [Commented] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr

[ https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668962#comment-15668962 ] Hadoop QA commented on AMBARI-18898: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18903) Implement Create Alerts: Create a base wizard for all steps

[ https://issues.apache.org/jira/browse/AMBARI-18903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-18903: - Attachment: AMBARI-18903.patch > Implement Create Alerts: Create a base wizard for all steps >

[jira] [Commented] (AMBARI-18890) Enable "Auto Start" feature for services & components by default

[ https://issues.apache.org/jira/browse/AMBARI-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668910#comment-15668910 ] Hudson commented on AMBARI-18890: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6020 (See

[jira] [Commented] (AMBARI-18897) HBase conf directory should not have a copy of core-site.xml and hdfs-site.xml

[ https://issues.apache.org/jira/browse/AMBARI-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668913#comment-15668913 ] Hadoop QA commented on AMBARI-18897: {color:green}+1 overall{color}. Here are the results of

[jira] [Created] (AMBARI-18903) Implement Create Alerts: Create a base wizard for all steps

Xi Wang created AMBARI-18903: Summary: Implement Create Alerts: Create a base wizard for all steps Key: AMBARI-18903 URL: https://issues.apache.org/jira/browse/AMBARI-18903 Project: Ambari

[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18866: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and

[jira] [Commented] (AMBARI-18890) Enable "Auto Start" feature for services & components by default

[ https://issues.apache.org/jira/browse/AMBARI-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668893#comment-15668893 ] Hudson commented on AMBARI-18890: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #331 (See

[jira] [Commented] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr

[ https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668858#comment-15668858 ] Hadoop QA commented on AMBARI-18898: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18846) Custom services should be able to easily specify their own dashboards

[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668850#comment-15668850 ] Hudson commented on AMBARI-18846: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6019 (See

[jira] [Commented] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes

[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668848#comment-15668848 ] Hudson commented on AMBARI-18852: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6019 (See

[jira] [Updated] (AMBARI-18901) Use "Number of LLAP Nodes" selected as the driver for LLAP config calculations.

[ https://issues.apache.org/jira/browse/AMBARI-18901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18901: - Summary: Use "Number of LLAP Nodes" selected as the driver for LLAP config

[jira] [Commented] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668809#comment-15668809 ] Hadoop QA commented on AMBARI-18899: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Resolved] (AMBARI-18890) Enable "Auto Start" feature for services & components by default

[ https://issues.apache.org/jira/browse/AMBARI-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-18890. --- Resolution: Fixed Committed to trunk and 2.5 03bd7a6dab4d4a39e649f2c9361d07efbea1bb64 >

[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668781#comment-15668781 ] Hudson commented on AMBARI-18637: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #6018 (See

[jira] [Commented] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668745#comment-15668745 ] Hadoop QA commented on AMBARI-18866: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)

[ https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668642#comment-15668642 ] Hadoop QA commented on AMBARI-18821: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS

[ https://issues.apache.org/jira/browse/AMBARI-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668581#comment-15668581 ] Hadoop QA commented on AMBARI-18902: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Updated] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr

[ https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18898: Attachment: AMBARI-18898.patch > Multiple kerberos name rules can not be set up for

[jira] [Updated] (AMBARI-18898) Multiple kerberos name rules can not be set up for Ambari Infra Solr

[ https://issues.apache.org/jira/browse/AMBARI-18898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18898: Attachment: (was: AMBARI-18898.patch) > Multiple kerberos name rules can not be set

[jira] [Commented] (AMBARI-18846) Custom services should be able to easily specify their own dashboards

[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668487#comment-15668487 ] Hudson commented on AMBARI-18846: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #330 (See

[jira] [Updated] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes

[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18852: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HostCleanup.py to be able to stop

[jira] [Commented] (AMBARI-18852) HostCleanup.py to be able to stop processes owned by users or java processes

[ https://issues.apache.org/jira/browse/AMBARI-18852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668483#comment-15668483 ] Di Li commented on AMBARI-18852: pushed to trunk as

[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.

[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668479#comment-15668479 ] Jayush Luniya commented on AMBARI-18431: cc: [~swagle] > Storm Ambari view - Fixes to DAG,

[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.

[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668476#comment-15668476 ] Jayush Luniya commented on AMBARI-18431: [~sriharsha] We are almost about to kickoff a 2.4.2

[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.

[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18431: --- Fix Version/s: (was: trunk) 2.5.0 > Storm Ambari view - Fixes to

[jira] [Updated] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS

[ https://issues.apache.org/jira/browse/AMBARI-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18902: --- Attachment: AMBARI-18902.patch > Minor typo fix in TimeliveMetricsStore class in AMS >

[jira] [Updated] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS

[ https://issues.apache.org/jira/browse/AMBARI-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18902: --- Status: Patch Available (was: Open) > Minor typo fix in TimeliveMetricsStore class in AMS >

[jira] [Created] (AMBARI-18902) Minor typo fix in TimeliveMetricsStore class in AMS

Di Li created AMBARI-18902: -- Summary: Minor typo fix in TimeliveMetricsStore class in AMS Key: AMBARI-18902 URL: https://issues.apache.org/jira/browse/AMBARI-18902 Project: Ambari Issue Type: Bug

[jira] [Resolved] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility

[ https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-18380. -- Resolution: Duplicate Dup of AMBARI-18630 > For rolling upgrade of Kafka

[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.

[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668442#comment-15668442 ] Sriharsha Chintalapani commented on AMBARI-18431: - [~jluniya] any reason for changing

[jira] [Commented] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility

[ https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668430#comment-15668430 ] Jayush Luniya commented on AMBARI-18380: [~afernandez] Are you fixing this in 2.4.2? Can we move

[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility

[ https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18380: --- Assignee: Alejandro Fernandez > For rolling upgrade of Kafka 0.10.0.1 we need to configs

[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668355#comment-15668355 ] Hudson commented on AMBARI-18637: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #329 (See

[jira] [Created] (AMBARI-18901) Use "Num of LLAP Node" selected as the driver for LLAP config calculations.

Swapan Shridhar created AMBARI-18901: Summary: Use "Num of LLAP Node" selected as the driver for LLAP config calculations. Key: AMBARI-18901 URL: https://issues.apache.org/jira/browse/AMBARI-18901

[jira] [Updated] (AMBARI-18846) Custom services should be able to easily specify their own dashboards

[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-18846: Resolution: Fixed Status: Resolved (was: Patch Available) > Custom services should be

[jira] [Commented] (AMBARI-18794) Remove PHD stack from Ambari source code

[ https://issues.apache.org/jira/browse/AMBARI-18794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668305#comment-15668305 ] Jayush Luniya commented on AMBARI-18794: Moving out of 2.4.2 > Remove PHD stack from Ambari

[jira] [Updated] (AMBARI-18794) Remove PHD stack from Ambari source code

[ https://issues.apache.org/jira/browse/AMBARI-18794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18794: --- Fix Version/s: (was: 2.4.2) > Remove PHD stack from Ambari source code >

[jira] [Updated] (AMBARI-18770) Service check and Ambari Alerting for RM fails against Yarn with HA and SPNEGO

[ https://issues.apache.org/jira/browse/AMBARI-18770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18770: --- Resolution: Fixed Status: Resolved (was: Patch Available) Resolving since its

[jira] [Updated] (AMBARI-18597) Rename service to "Microsoft R Server" and component to "Microsoft R Node Client"

[ https://issues.apache.org/jira/browse/AMBARI-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18597: --- Resolution: Fixed Status: Resolved (was: Patch Available) Looks like its already

[jira] [Commented] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services

[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668296#comment-15668296 ] Jayush Luniya commented on AMBARI-18666: Moving this out of 2.4.2 as its not a blocker for 2.4.2

[jira] [Updated] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services

[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18666: --- Fix Version/s: (was: 2.4.2) > Move HAWQ and PXF RCO from stacks to common-services >

[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.

[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18431: --- Fix Version/s: (was: 2.4.2) trunk > Storm Ambari view - Fixes to

[jira] [Updated] (AMBARI-18578) Grafana fails to start after deployment

[ https://issues.apache.org/jira/browse/AMBARI-18578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18578: --- Fix Version/s: (was: 2.4.2) 2.5.0 > Grafana fails to start after

[jira] [Resolved] (AMBARI-18317) ambari-agent script does not check for unset variables. (Leading to chown root:root /)

[ https://issues.apache.org/jira/browse/AMBARI-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-18317. Resolution: Fixed > ambari-agent script does not check for unset variables. (Leading to

[jira] [Commented] (AMBARI-18317) ambari-agent script does not check for unset variables. (Leading to chown root:root /)

[ https://issues.apache.org/jira/browse/AMBARI-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668271#comment-15668271 ] Jayush Luniya commented on AMBARI-18317: Looks like this is already in 2.4. Resolving JIRA.

[jira] [Resolved] (AMBARI-18314) Users page after LDAP sync shows blank

[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-18314. Resolution: Incomplete > Users page after LDAP sync shows blank >

[jira] [Commented] (AMBARI-18314) Users page after LDAP sync shows blank

[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668254#comment-15668254 ] Jayush Luniya commented on AMBARI-18314: [~shreyabh...@gmail.com] There is not enough details on

[jira] [Updated] (AMBARI-18314) Users page after LDAP sync shows blank

[ https://issues.apache.org/jira/browse/AMBARI-18314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18314: --- Fix Version/s: (was: 2.4.2) 2.5.0 > Users page after LDAP sync shows

[jira] [Resolved] (AMBARI-15537) Service Level Extensions for Add-On Services

[ https://issues.apache.org/jira/browse/AMBARI-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-15537. Resolution: Fixed > Service Level Extensions for Add-On Services >

[jira] [Updated] (AMBARI-18724) Add dependency of HSI config 'hive.llap.zk.sm.connectionString' on 'enable_hive_interactive', so as to cover the HDP 2.4 -> 2.5 upgrade case, to get 'hive.llap.zk.sm.co

[ https://issues.apache.org/jira/browse/AMBARI-18724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-18724: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add dependency of

[jira] [Commented] (AMBARI-18666) Move HAWQ and PXF RCO from stacks to common-services

[ https://issues.apache.org/jira/browse/AMBARI-18666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668244#comment-15668244 ] Jayush Luniya commented on AMBARI-18666: [~mithmatt] What's the latest on this JIRA? Looks like

[jira] [Updated] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)

[ https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-18821: -- Description: Add some new configuration properties to ambari and logsearch as well to handle

[jira] [Updated] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)

[ https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-18821: -- Attachment: (was: AMBARI-18821.patch) > Logsearch support KNOX SSO (with JWT) >

[jira] [Updated] (AMBARI-18821) Logsearch support KNOX SSO (with JWT)

[ https://issues.apache.org/jira/browse/AMBARI-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-18821: -- Attachment: AMBARI-18821.patch > Logsearch support KNOX SSO (with JWT) >

[jira] [Commented] (AMBARI-16828) Support round-robin scheduling with failover for Sinks with distributed collector

[ https://issues.apache.org/jira/browse/AMBARI-16828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668176#comment-15668176 ] Hudson commented on AMBARI-16828: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-15902) Refactor Metadata manager for supporting distributed collector

[ https://issues.apache.org/jira/browse/AMBARI-15902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668174#comment-15668174 ] Hudson commented on AMBARI-15902: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config

[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668171#comment-15668171 ] Hudson commented on AMBARI-18517: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-17726) ArrayIndexOutOfBounds exception thrown on shard calculation

[ https://issues.apache.org/jira/browse/AMBARI-17726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668170#comment-15668170 ] Hudson commented on AMBARI-17726: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-17716) AMS HA not working in secure cluster

[ https://issues.apache.org/jira/browse/AMBARI-17716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668168#comment-15668168 ] Hudson commented on AMBARI-17716: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode

[ https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668165#comment-15668165 ] Hudson commented on AMBARI-18518: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18171) AMS, Accumulo, Hive metrics do not show up in AMS HA clusters.

[ https://issues.apache.org/jira/browse/AMBARI-18171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668130#comment-15668130 ] Hudson commented on AMBARI-18171: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-16834) Any start command fails if AMS is installed.

[ https://issues.apache.org/jira/browse/AMBARI-16834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668161#comment-15668161 ] Hudson commented on AMBARI-16834: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-15623) Support distributed aggregation for multiple AMS instances

[ https://issues.apache.org/jira/browse/AMBARI-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668159#comment-15668159 ] Hudson commented on AMBARI-15623: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts

[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668157#comment-15668157 ] Hudson commented on AMBARI-18487: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18851) Collector host refresh in Ambari Server is not working in single Metrics collector deployments.

[ https://issues.apache.org/jira/browse/AMBARI-18851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668151#comment-15668151 ] Hudson commented on AMBARI-18851: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-16991) Fix metric sink

[ https://issues.apache.org/jira/browse/AMBARI-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668147#comment-15668147 ] Hudson commented on AMBARI-16991: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-17080) Support Storm 1.0 in Ambari Metrics for Storm

[ https://issues.apache.org/jira/browse/AMBARI-17080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668121#comment-15668121 ] Hudson commented on AMBARI-17080: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18362) Update sinks to read multiple collector hostnames from configs

[ https://issues.apache.org/jira/browse/AMBARI-18362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668144#comment-15668144 ] Hudson commented on AMBARI-18362: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-17184) HBase doesn't start because of lacking of variable

[ https://issues.apache.org/jira/browse/AMBARI-17184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668139#comment-15668139 ] Hudson commented on AMBARI-17184: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18265) Make sure AMS embedded works after AMS HA changes

[ https://issues.apache.org/jira/browse/AMBARI-18265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668135#comment-15668135 ] Hudson commented on AMBARI-18265: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18199) Wrong hostname in timeline.metrics.service.webapp.address breaks AMS HA

[ https://issues.apache.org/jira/browse/AMBARI-18199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668137#comment-15668137 ] Hudson commented on AMBARI-18199: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18012) Metrics Sink unable to connect to zookeeper to locate collector host.

[ https://issues.apache.org/jira/browse/AMBARI-18012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668132#comment-15668132 ] Hudson commented on AMBARI-18012: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18170) Kafka Metrics do not show up in AMS HA enabled cluster

[ https://issues.apache.org/jira/browse/AMBARI-18170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668124#comment-15668124 ] Hudson commented on AMBARI-18170: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #328 (See

[jira] [Commented] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668037#comment-15668037 ] Sumit Mohanty commented on AMBARI-18637: Addendum patch looks good. > Management pack purge

[jira] [Updated] (AMBARI-18637) Management pack purge option should warn user and ask for confirmation before purging

[ https://issues.apache.org/jira/browse/AMBARI-18637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18637: --- Attachment: AMBARI-18637.addendum.patch > Management pack purge option should warn user and

[jira] [Created] (AMBARI-18900) Zookeeper service check fails after deployment

Dhanya Balasundaran created AMBARI-18900: Summary: Zookeeper service check fails after deployment Key: AMBARI-18900 URL: https://issues.apache.org/jira/browse/AMBARI-18900 Project: Ambari

[jira] [Updated] (AMBARI-18889) ambari-server should use persisted status of the stage and request for computation when queried

[ https://issues.apache.org/jira/browse/AMBARI-18889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18889: -- Summary: ambari-server should use persisted status of the stage and request for computation

[jira] [Commented] (AMBARI-18425) Support PAM as an authentication option for Ranger in Ambari

[ https://issues.apache.org/jira/browse/AMBARI-18425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667921#comment-15667921 ] Shi Wang commented on AMBARI-18425: --- This patch adds an authentication option "PAM" in ambari for

[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Attachment: (was: AMBARI-18866.patch) > Stack advisor should

[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Status: Patch Available (was: Open) > Stack advisor should limit

[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Attachment: AMBARI-18866.patch > Stack advisor should limit call

[jira] [Updated] (AMBARI-18866) Stack advisor should limit call history it preserves

[ https://issues.apache.org/jira/browse/AMBARI-18866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-18866: --- Status: Open (was: Patch Available) Will attach a new patch with

[jira] [Commented] (AMBARI-18836) Remove group readable from hdfs headless keytab

[ https://issues.apache.org/jira/browse/AMBARI-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667873#comment-15667873 ] Shi Wang commented on AMBARI-18836: --- Hi [~lpuskas] [~aonishuk] Do you have any suggestion on this

[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Fix Version/s: 2.5.0 > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack

[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Affects Version/s: 2.4.2 > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack

[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Status: Patch Available (was: Open) > Post Upgrade to Ambari 2.4.1 from 2.2.2

[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Attachment: AMBARI-18899.patch > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All

[jira] [Updated] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

[ https://issues.apache.org/jira/browse/AMBARI-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-18899: Component/s: ambari-server > Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All

[jira] [Created] (AMBARI-18899) Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart

Dmitry Lysnichenko created AMBARI-18899: --- Summary: Post Upgrade to Ambari 2.4.1 from 2.2.2 --> All stack component prompted for restart Key: AMBARI-18899 URL:

[jira] [Commented] (AMBARI-18876) Remove old UpgradeCatalog and tests

[ https://issues.apache.org/jira/browse/AMBARI-18876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667785#comment-15667785 ] Hadoop QA commented on AMBARI-18876: {color:red}-1 overall{color}. Here are the results of testing

[jira] [Commented] (AMBARI-18846) Custom services should be able to easily specify their own dashboards

[ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667702#comment-15667702 ] Hadoop QA commented on AMBARI-18846: {color:green}+1 overall{color}. Here are the results of

  1   2   >