[jira] [Created] (AMBARI-18338) Microsoft-R client should work in a secured cluster

Balázs Bence Sári created AMBARI-18338: -- Summary: Microsoft-R client should work in a secured cluster Key: AMBARI-18338 URL: https://issues.apache.org/jira/browse/AMBARI-18338 Project: Ambari

[jira] [Updated] (AMBARI-18310) Refactor logsearch portal code

[ https://issues.apache.org/jira/browse/AMBARI-18310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-18310: -- Component/s: ambari-logsearch > Refactor logsearch portal code >

[jira] [Commented] (AMBARI-18339) Persist UI console errors from Admin View

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

[jira] [Updated] (AMBARI-17456) Support round-robin scheduling with failover for monitors with distributed collector

[ https://issues.apache.org/jira/browse/AMBARI-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17456: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Support

[jira] [Commented] (AMBARI-18308) Ambari UI: Memory leak while adding and removing property

[ https://issues.apache.org/jira/browse/AMBARI-18308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473750#comment-15473750 ] Andrii Tkach commented on AMBARI-18308: --- [~jaimin], Please provide patch for trunk too, I have

[jira] [Updated] (AMBARI-18339) Persist UI console errors from Admin View

[ https://issues.apache.org/jira/browse/AMBARI-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18339: - Attachment: AMBARI-18339.patch > Persist UI console errors from Admin View >

[jira] [Updated] (AMBARI-18340) Kafka acls setup is failing as part of atlas start

[ https://issues.apache.org/jira/browse/AMBARI-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated AMBARI-18340: --- Status: Patch Available (was: Open) > Kafka acls setup is failing as part of atlas start >

[jira] [Updated] (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:all-tabpanel ] Dmytro Sen updated AMBARI-18199: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Wrong

[jira] [Resolved] (AMBARI-16214) Ensure Blueprint deployment can start immediately - after Server start

[ https://issues.apache.org/jira/browse/AMBARI-16214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader resolved AMBARI-16214. --- Resolution: Won't Fix > Ensure Blueprint deployment can start immediately - after

[jira] [Updated] (AMBARI-18340) Kafka acls setup is failing as part of atlas start

[ https://issues.apache.org/jira/browse/AMBARI-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Khan updated AMBARI-18340: --- Attachment: AMBARI-18340.patch > Kafka acls setup is failing as part of atlas start >

[jira] [Updated] (AMBARI-18318) Agent heartbeat handler would always handle 'UNHEALTHY' state as 'UNKNOWN'

[ https://issues.apache.org/jira/browse/AMBARI-18318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18318: - Resolution: Fixed Status: Resolved (was: Patch Available) > Agent heartbeat

[jira] [Updated] (AMBARI-18318) Agent heartbeat handler would always handle 'UNHEALTHY' state as 'UNKNOWN'

[ https://issues.apache.org/jira/browse/AMBARI-18318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18318: - Affects Version/s: 2.2.2 > Agent heartbeat handler would always handle 'UNHEALTHY'

[jira] [Created] (AMBARI-18339) Persist UI console errors from Admin View

Antonenko Alexander created AMBARI-18339: Summary: Persist UI console errors from Admin View Key: AMBARI-18339 URL: https://issues.apache.org/jira/browse/AMBARI-18339 Project: Ambari

[jira] [Created] (AMBARI-18340) Kafka acls setup is failing as part of atlas start

Ayub Khan created AMBARI-18340: -- Summary: Kafka acls setup is failing as part of atlas start Key: AMBARI-18340 URL: https://issues.apache.org/jira/browse/AMBARI-18340 Project: Ambari Issue

[jira] [Updated] (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:all-tabpanel ] Dmytro Sen updated AMBARI-18199: Attachment: AMBARI-18199_2.patch > Wrong hostname in timeline.metrics.service.webapp.address

[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Status: Open (was: Patch Available) > Externalize skip repo url check to ambari.properties instead of

[jira] [Updated] (AMBARI-18339) Persist UI console errors from Admin View

[ https://issues.apache.org/jira/browse/AMBARI-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18339: - Status: Patch Available (was: Open) > Persist UI console errors from Admin

[jira] [Commented] (AMBARI-18339) Persist UI console errors from Admin View

[ https://issues.apache.org/jira/browse/AMBARI-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15473577#comment-15473577 ] Aleksandr Kovalenko commented on AMBARI-18339: -- +1 for the patch > Persist UI console

[jira] [Updated] (AMBARI-17456) Support round-robin scheduling with failover for monitors with distributed collector

[ https://issues.apache.org/jira/browse/AMBARI-17456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-17456: Attachment: AMBARI-17456_2.patch > Support round-robin scheduling with failover for monitors with

[jira] [Updated] (AMBARI-18318) Agent heartbeat handler would always handle 'UNHEALTHY' state as 'UNKNOWN'

[ https://issues.apache.org/jira/browse/AMBARI-18318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18318: - Fix Version/s: trunk > Agent heartbeat handler would always handle 'UNHEALTHY' state as

[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Status: Patch Available (was: Open) > Externalize skip repo url check to ambari.properties instead of

[jira] [Commented] (AMBARI-18339) Persist UI console errors from Admin View

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

[jira] [Updated] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed

[ https://issues.apache.org/jira/browse/AMBARI-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18341: --- Status: Patch Available (was: Open) > Need to validate behaviour and show warn

[jira] [Updated] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed

[ https://issues.apache.org/jira/browse/AMBARI-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18341: --- Attachment: AMBARI-18341.patch > Need to validate behaviour and show warn message

[jira] [Resolved] (AMBARI-16217) Command execution by single python executor.

[ https://issues.apache.org/jira/browse/AMBARI-16217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader resolved AMBARI-16217. --- Resolution: Duplicate Duplicate of AMBARI-16222 > Command execution by single

[jira] [Updated] (AMBARI-18340) Kafka acls setup is failing as part of atlas start

[ https://issues.apache.org/jira/browse/AMBARI-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-18340: --- Priority: Critical (was: Major) > Kafka acls setup is failing as part of atlas start >

[jira] [Created] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed

Vitaly Brodetskyi created AMBARI-18341: -- Summary: Need to validate behaviour and show warn message for user after hcat user was removed Key: AMBARI-18341 URL:

[jira] [Commented] (AMBARI-18340) Kafka acls setup is failing as part of atlas start

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

[jira] [Updated] (AMBARI-18339) Persist UI console errors from Admin View

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

[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=15473918#comment-15473918 ] Hudson commented on AMBARI-18199: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5636 (See

[jira] [Commented] (AMBARI-18318) Agent heartbeat handler would always handle 'UNHEALTHY' state as 'UNKNOWN'

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

[jira] [Updated] (AMBARI-18338) Microsoft-R client should work in a secured cluster

[ https://issues.apache.org/jira/browse/AMBARI-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-18338: --- Status: Patch Available (was: In Progress) > Microsoft-R client should work in a

[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=15473972#comment-15473972 ] Dmytro Sen commented on AMBARI-18199: - {code} FAIL: test_update_open_files_ulimit

[jira] [Commented] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties

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

[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties

[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18335: -- Attachment: AMBARI-18335_trunk_02.patch > After upgrading cluster from HDP-2.4.x to HDP-2.5.x

[jira] [Updated] (AMBARI-18331) JMX metric retrieval method may unnecessarily refresh metrics at a high rate

[ https://issues.apache.org/jira/browse/AMBARI-18331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18331: - Resolution: Fixed Status: Resolved (was: Patch Available) > JMX metric

[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties

[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18335: -- Attachment: AMBARI-18335_trunk_02.patch AMBARI-18335_branch-2.4_02.patch >

[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties

[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-18335: -- Attachment: (was: AMBARI-18335_trunk_02.patch) > After upgrading cluster from HDP-2.4.x

[jira] [Updated] (AMBARI-18318) Agent heartbeat handler would always handle 'UNHEALTHY' state as 'UNKNOWN'

[ https://issues.apache.org/jira/browse/AMBARI-18318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-18318: - Fix Version/s: 2.4.1 > Agent heartbeat handler would always handle 'UNHEALTHY' state as

[jira] [Commented] (AMBARI-18338) Microsoft-R client should work in a secured cluster

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

[jira] [Commented] (AMBARI-18318) Agent heartbeat handler would always handle 'UNHEALTHY' state as 'UNKNOWN'

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

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

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

[jira] [Updated] (AMBARI-16213) Initial Start All should be similar to a later Start All

[ https://issues.apache.org/jira/browse/AMBARI-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16213: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Initial Start All should be

[jira] [Updated] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs

[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17285: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Custom service repos in

[jira] [Updated] (AMBARI-18340) Kafka acls setup is failing as part of atlas start

[ https://issues.apache.org/jira/browse/AMBARI-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18340: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Kafka acls setup is failing as

[jira] [Updated] (AMBARI-16221) AMS/LogSearch service should be outside the cluster and shared across clusters

[ https://issues.apache.org/jira/browse/AMBARI-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16221: --- Fix Version/s: (was: 2.4.1) 2.4.2 > AMS/LogSearch service should be

[jira] [Updated] (AMBARI-16215) Ambari starts the right component when multi instances are deployed (e.g. AMS)

[ https://issues.apache.org/jira/browse/AMBARI-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16215: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Ambari starts the right

[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.1) 2.4.2 > Users page after LDAP sync shows

[jira] [Updated] (AMBARI-18294) Ambari Server Start/Stop fails on Centos 7.1+

[ https://issues.apache.org/jira/browse/AMBARI-18294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18294: --- Priority: Blocker (was: Major) > Ambari Server Start/Stop fails on Centos 7.1+ >

[jira] [Updated] (AMBARI-18290) Ambari does not support HBase on HTTPS mode

[ https://issues.apache.org/jira/browse/AMBARI-18290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18290: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to trunk. >

[jira] [Updated] (AMBARI-16213) Initial Start All should be similar to a later Start All

[ https://issues.apache.org/jira/browse/AMBARI-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16213: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Initial Start All should

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Status: Patch Available (was: Open) > Unit Tests failure:

[jira] [Commented] (AMBARI-18339) Persist UI console errors from Admin View

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

[jira] [Updated] (AMBARI-16226) Execute topology tasks in parallel by hosts.

[ https://issues.apache.org/jira/browse/AMBARI-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16226: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Execute topology tasks in

[jira] [Updated] (AMBARI-18316) Ambari upgrade to Ambari 2.4.0 failed during DB upgrade due to incorrect TEZ view regex

[ https://issues.apache.org/jira/browse/AMBARI-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18316: --- Priority: Blocker (was: Major) > Ambari upgrade to Ambari 2.4.0 failed during DB upgrade

[jira] [Updated] (AMBARI-18285) Ambari upgrade from 2.4.0.x version fails.

[ https://issues.apache.org/jira/browse/AMBARI-18285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18285: --- Priority: Blocker (was: Major) > Ambari upgrade from 2.4.0.x version fails. >

[jira] [Updated] (AMBARI-18323) Cluster creation complete is missing from ambari-server log

[ https://issues.apache.org/jira/browse/AMBARI-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-18323: -- Fix Version/s: (was: 2.5.0) trunk > Cluster creation complete

[jira] [Resolved] (AMBARI-18291) Ambari tempory path configuration

[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy resolved AMBARI-18291. Resolution: Fixed Fix Version/s: 2.4.0 This is already available in 2.4.0 , hence

[jira] [Updated] (AMBARI-18271) Multiple Aggregate Alerts For JournalNode Exist With Some Being Incorrect

[ https://issues.apache.org/jira/browse/AMBARI-18271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Sposetti updated AMBARI-18271: --- Fix Version/s: 2.4.1 > Multiple Aggregate Alerts For JournalNode Exist With Some Being

[jira] [Updated] (AMBARI-16221) AMS/LogSearch service should be outside the cluster and shared across clusters

[ https://issues.apache.org/jira/browse/AMBARI-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16221: -- Fix Version/s: (was: 2.4.2) 3.0.0 > AMS/LogSearch service

[jira] [Updated] (AMBARI-16219) Agent computes the DAG due to RCO and executes

[ https://issues.apache.org/jira/browse/AMBARI-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16219: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Agent computes the DAG due

[jira] [Commented] (AMBARI-18341) Need to validate behaviour and show warn message for user after hcat user was removed

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

[jira] [Updated] (AMBARI-18191) "Restart all required" services operation failed at Metrics Collector since HDFS was not yet up

[ https://issues.apache.org/jira/browse/AMBARI-18191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Sposetti updated AMBARI-18191: --- Fix Version/s: 2.4.1 > "Restart all required" services operation failed at Metrics

[jira] [Updated] (AMBARI-16215) Ambari starts the right component when multi instances are deployed (e.g. AMS)

[ https://issues.apache.org/jira/browse/AMBARI-16215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16215: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Ambari starts the right

[jira] [Updated] (AMBARI-16218) Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done during start

[ https://issues.apache.org/jira/browse/AMBARI-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16218: -- Fix Version/s: (was: 2.4.2) 2.5.0 > Identify Starts (e.g.

[jira] [Updated] (AMBARI-16219) Agent computes the DAG due to RCO and executes

[ https://issues.apache.org/jira/browse/AMBARI-16219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16219: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Agent computes the DAG due to

[jira] [Updated] (AMBARI-16218) Identify Starts (e.g. NN/Oozie) that are the longest and optimize work done during start

[ https://issues.apache.org/jira/browse/AMBARI-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16218: --- Fix Version/s: (was: 2.4.1) 2.4.2 > Identify Starts (e.g. NN/Oozie)

[jira] [Updated] (AMBARI-16226) Execute topology tasks in parallel by hosts.

[ https://issues.apache.org/jira/browse/AMBARI-16226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-16226: -- Fix Version/s: (was: 2.4.2) 3.0.0 > Execute topology tasks in

[jira] [Created] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

Nahappan Somasundaram created AMBARI-18342: -- Summary: Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain) Key: AMBARI-18342 URL: https://issues.apache.org/jira/browse/AMBARI-18342

[jira] [Commented] (AMBARI-18291) Ambari tempory path configuration

[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15474425#comment-15474425 ] amarnathreddy commented on AMBARI-18291: This bug is already fixed in Ambari2.4.0 , hence

[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties

[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18335: --- Fix Version/s: (was: 2.4.1) 2.4.2 > After upgrading cluster from

[jira] [Updated] (AMBARI-18291) Ambari tempory path configuration

[ https://issues.apache.org/jira/browse/AMBARI-18291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] amarnathreddy updated AMBARI-18291: --- Affects Version/s: (was: 2.4.0) > Ambari tempory path configuration >

[jira] [Created] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster

Andrew Onischuk created AMBARI-18343: Summary: Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster Key: AMBARI-18343 URL:

[jira] [Updated] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster

[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18343: - Attachment: AMBARI-18343.patch > Ambari server start fails after upgrade due to missing

[jira] [Updated] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster

[ https://issues.apache.org/jira/browse/AMBARI-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18343: - Status: Patch Available (was: Open) > Ambari server start fails after upgrade due to

[jira] [Updated] (AMBARI-18335) After upgrading cluster from HDP-2.4.x to HDP-2.5.x and added atlas service - missing kafka security properties

[ https://issues.apache.org/jira/browse/AMBARI-18335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18335: --- Fix Version/s: (was: 2.4.2) 2.4.1 > After upgrading cluster from

[jira] [Commented] (AMBARI-18331) JMX metric retrieval method may unnecessarily refresh metrics at a high rate

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

[jira] [Updated] (AMBARI-18325) Ambari cannot install HDP from mirror list

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

[jira] [Updated] (AMBARI-18321) atlas hook for hive and storm fail to push metadeta

[ https://issues.apache.org/jira/browse/AMBARI-18321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Sposetti updated AMBARI-18321: --- Fix Version/s: 2.4.1 > atlas hook for hive and storm fail to push metadeta >

[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Status: Open (was: Patch Available) > Externalize skip repo url check to ambari.properties instead of

[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Status: Patch Available (was: Open) > Externalize skip repo url check to ambari.properties instead of

[jira] [Updated] (AMBARI-18324) Externalize skip repo url check to ambari.properties instead of hardcoding it in Ambari Java code

[ https://issues.apache.org/jira/browse/AMBARI-18324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18324: --- Attachment: AMBARI-18324_rebase.patch > Externalize skip repo url check to ambari.properties instead of

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Attachment: rb51733.patch > Unit Tests failure:

[jira] [Updated] (AMBARI-15538) Support service-specific repo for add-on services

[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-15538: --- Fix Version/s: 2.4.2 > Support service-specific repo for add-on services >

[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6

[ https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18337: - Status: Patch Available (was: Open) > Syntax Error in Ambari HAWQ Unit test with

[jira] [Updated] (AMBARI-18322) [Grafana] Add Apache NiFi - Hosts dashboard

[ https://issues.apache.org/jira/browse/AMBARI-18322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prajwal Rao updated AMBARI-18322: - Fix Version/s: (was: 2.5.0) trunk > [Grafana] Add Apache NiFi - Hosts

[jira] [Commented] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)

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

[jira] [Commented] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6

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

[jira] [Commented] (AMBARI-18343) Ambari server start fails after upgrade due to missing krb5JAASLogin.conf file on WireEncrypted cluster

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

[jira] [Updated] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)

[ https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18348: Attachment: AMBARI-18348.patch > Ranger audit log collection is not used in Log Search

[jira] [Updated] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)

[ https://issues.apache.org/jira/browse/AMBARI-18348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-18348: Status: Patch Available (was: In Progress) > Ranger audit log collection is not used in

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Status: Patch Available (was: Open) > Unit Tests failure:

[jira] [Updated] (AMBARI-18342) Unit Tests failure: test_update_open_files_ulimit (TestMain.TestMain)

[ https://issues.apache.org/jira/browse/AMBARI-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18342: --- Attachment: rb51733 (2).patch > Unit Tests failure:

[jira] [Updated] (AMBARI-18344) Metrics data is not available - AMS in distributed mode

[ https://issues.apache.org/jira/browse/AMBARI-18344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18344: --- Status: Patch Available (was: Open) > Metrics data is not available - AMS in

[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install

[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18346: Attachment: AMBARI-18346.v0.patch > SmartSense Mandatory Install

[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6

[ https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18337: - Attachment: AMBARI-18337.patch Attach a patch > Syntax Error in Ambari HAWQ Unit test

[jira] [Commented] (AMBARI-18346) SmartSense Mandatory Install

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

[jira] [Commented] (AMBARI-18345) 'Stack advisor' validation code reports error while trying to access 'yarn.nodemanager.resource.memory-mb' config.

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

[jira] [Created] (AMBARI-18348) Ranger audit log collection is not used in Log Search (managed by ambari)

Miklos Gergely created AMBARI-18348: --- Summary: Ranger audit log collection is not used in Log Search (managed by ambari) Key: AMBARI-18348 URL: https://issues.apache.org/jira/browse/AMBARI-18348

[jira] [Commented] (AMBARI-15538) Support service-specific repo for add-on services

[ https://issues.apache.org/jira/browse/AMBARI-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15475155#comment-15475155 ] Tim Thorpe commented on AMBARI-15538: - Will the repos folder be linked to all services? I guess

  1   2   >