[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes in installer wizard

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18173: --- Labels: 240RMApproved (was: ) > HSI is not started even when "Enable Interactive Query" is

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes in installer wizard

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18173: Summary: HSI is not started even when "Enable Interactive Query" is set to Yes in

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes in installer wizard

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18173: Resolution: Fixed Status: Resolved (was: Patch Available) Received +1 on review

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18173: Status: Patch Available (was: Open) > HSI is not started even when "Enable Interactive

[jira] [Created] (AMBARI-18176) Support removing Hive Metastore password from Hive configuration

Bing Li created AMBARI-18176: Summary: Support removing Hive Metastore password from Hive configuration Key: AMBARI-18176 URL: https://issues.apache.org/jira/browse/AMBARI-18176 Project: Ambari

[jira] [Commented] (AMBARI-18074) umask value should less than 18 when check hosts in the step 3 of install ambari

[ https://issues.apache.org/jira/browse/AMBARI-18074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423779#comment-15423779 ] wuhui commented on AMBARI-18074: Dear Jayush Luniya： Thanks for your attention！should I upload a

[jira] [Commented] (AMBARI-17805) the history versions of config can't be showed in the screen fully

[ https://issues.apache.org/jira/browse/AMBARI-17805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423780#comment-15423780 ] wuhui commented on AMBARI-17805: Dear Jayush Luniya： Thanks for your attention！should I upload a

[jira] [Created] (AMBARI-18174) Add configuration and monitoring for XeonPhi

Ben Markham created AMBARI-18174: Summary: Add configuration and monitoring for XeonPhi Key: AMBARI-18174 URL: https://issues.apache.org/jira/browse/AMBARI-18174 Project: Ambari Issue Type:

[jira] [Created] (AMBARI-18175) Add configuration and monitoring for GPU

Ben Markham created AMBARI-18175: Summary: Add configuration and monitoring for GPU Key: AMBARI-18175 URL: https://issues.apache.org/jira/browse/AMBARI-18175 Project: Ambari Issue Type: Epic

[jira] [Updated] (AMBARI-17875) Add configuration to monitoring to LustreFS

[ https://issues.apache.org/jira/browse/AMBARI-17875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Markham updated AMBARI-17875: - Summary: Add configuration to monitoring to LustreFS (was: Add monitoring to LustreFS,

[jira] [Commented] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423704#comment-15423704 ] Jaimin D Jetly commented on AMBARI-18173: - This is a regression and blocks one of the flow of

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18173: Attachment: AMBARI-18173.patch > HSI is not started even when "Enable Interactive Query"

[jira] [Updated] (AMBARI-18173) HSI is not started even when "Enable Interactive Query" is set to Yes

[ https://issues.apache.org/jira/browse/AMBARI-18173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin D Jetly updated AMBARI-18173: Summary: HSI is not started even when "Enable Interactive Query" is set to Yes (was: HSI

[jira] [Created] (AMBARI-18173) HSI is not started even when enable_hive_interactive is set to Yes

Jaimin D Jetly created AMBARI-18173: --- Summary: HSI is not started even when enable_hive_interactive is set to Yes Key: AMBARI-18173 URL: https://issues.apache.org/jira/browse/AMBARI-18173 Project:

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Attachment: AMBARI-18151.patch > Oozie Hive actions fail when Atlas is

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Status: Open (was: Patch Available) > Oozie Hive actions fail when Atlas is

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Attachment: (was: AMBARI-18151.patch) > Oozie Hive actions fail when Atlas

[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server

[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Status: Patch Available (was: Open) > Hive Service check is failing after moving webhcat

[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server

[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Attachment: AMBARI-18172.v0.patch Modified unit test. Local ambari-web test passed. 29932

[jira] [Commented] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation

[ https://issues.apache.org/jira/browse/AMBARI-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423642#comment-15423642 ] Masahiro Tanaka commented on AMBARI-18126: -- Thanks! > Refactor Configuration To Allow For

[jira] [Commented] (AMBARI-17213) Create ambari workflow designer contrib view

[ https://issues.apache.org/jira/browse/AMBARI-17213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423623#comment-15423623 ] Christine commented on AMBARI-17213: Description of Workflow Designer objectives > Create ambari

[jira] [Commented] (AMBARI-18166) configs.sh script updates

[ https://issues.apache.org/jira/browse/AMBARI-18166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423618#comment-15423618 ] Aravindan Vijayan commented on AMBARI-18166: +1 > configs.sh script updates >

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

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

[jira] [Updated] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS

[ https://issues.apache.org/jira/browse/AMBARI-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li-Wei Tseng updated AMBARI-17591: -- Attachment: AMBARI-17591.patch > Collect JVM Heap, GC and thread pool metrics from Ambari

[jira] [Updated] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS

[ https://issues.apache.org/jira/browse/AMBARI-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li-Wei Tseng updated AMBARI-17591: -- Status: Patch Available (was: Open) > Collect JVM Heap, GC and thread pool metrics from

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18170: --- Status: In Progress (was: Patch Available) > Kafka Metrics do not show up in AMS

[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=15423589#comment-15423589 ] Siddharth Wagle commented on AMBARI-18171: -- +1 LGTM > AMS, Accumulo, Hive metrics do not show

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18171: --- Status: Patch Available (was: Open) > AMS, Accumulo, Hive metrics do not show up

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18170: --- Status: Patch Available (was: Open) > Kafka Metrics do not show up in AMS HA

[jira] [Commented] (AMBARI-17591) Collect JVM Heap, GC and thread pool metrics from Ambari Server and push to AMS

[ https://issues.apache.org/jira/browse/AMBARI-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423585#comment-15423585 ] Aravindan Vijayan commented on AMBARI-17591: Please attach the patch to the jira [~ltseng]

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration should be configurable via Ambari

[ https://issues.apache.org/jira/browse/AMBARI-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18169: Attachment: AMBARI-18169-2.patch > Falcon log4j configuration should be

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18170: --- Attachment: AMBARI-18170.patch > Kafka Metrics do not show up in AMS HA enabled

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18171: --- Attachment: AMBARI-18171.patch > AMS, Accumulo, Hive metrics do not show up in AMS

[jira] [Updated] (AMBARI-18166) configs.sh script updates

[ https://issues.apache.org/jira/browse/AMBARI-18166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18166: - Attachment: AMBARI-18166.patch > configs.sh script updates > -

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

Aravindan Vijayan created AMBARI-18171: -- Summary: AMS, Accumulo, Hive metrics do not show up in AMS HA clusters. Key: AMBARI-18171 URL: https://issues.apache.org/jira/browse/AMBARI-18171

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

Aravindan Vijayan created AMBARI-18170: -- Summary: Kafka Metrics do not show up in AMS HA enabled cluster Key: AMBARI-18170 URL: https://issues.apache.org/jira/browse/AMBARI-18170 Project: Ambari

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Status: Patch Available (was: Open) > Oozie Hive actions fail when Atlas is

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Attachment: AMBARI-18151.patch > Oozie Hive actions fail when Atlas is

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Attachment: (was: AMBARI-18151.patch) > Oozie Hive actions fail when Atlas

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18151: - Status: Open (was: Patch Available) > Oozie Hive actions fail when Atlas is

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18012: --- Fix Version/s: (was: 2.5.0) trunk > Metrics Sink unable to

[jira] [Updated] (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:all-tabpanel ] Aravindan Vijayan updated AMBARI-18012: --- Affects Version/s: (was: 2.5.0) trunk > Metrics Sink

[jira] [Commented] (AMBARI-18168) Create Atlas log4j changes for failed notifications

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

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration should be configurable via Ambari

[ https://issues.apache.org/jira/browse/AMBARI-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18169: Summary: Falcon log4j configuration should be configurable via Ambari (was:

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration is not configurable

[ https://issues.apache.org/jira/browse/AMBARI-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18169: Status: Patch Available (was: In Progress) > Falcon log4j configuration is not

[jira] [Updated] (AMBARI-18169) Falcon log4j configuration is not configurable

[ https://issues.apache.org/jira/browse/AMBARI-18169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkat Ranganathan updated AMBARI-18169: Attachment: AMBARI-18169.patch > Falcon log4j configuration is not configurable >

[jira] [Created] (AMBARI-18169) Falcon log4j configuration is not configurable

Venkat Ranganathan created AMBARI-18169: --- Summary: Falcon log4j configuration is not configurable Key: AMBARI-18169 URL: https://issues.apache.org/jira/browse/AMBARI-18169 Project: Ambari

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[ https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423391#comment-15423391 ] Jayush Luniya commented on AMBARI-18167: +1 for the patch. The Hadoop QA failure is not related.

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[ https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18167: --- Resolution: Fixed Status: Resolved (was: Patch Available) > RU: Kafka brokers

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[ https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423396#comment-15423396 ] Jayush Luniya commented on AMBARI-18167: Trunk commit 43457696137486daa338f39cef5e899554f025b3

[jira] [Commented] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

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

[jira] [Commented] (AMBARI-18042) Query execution takes a long time in hive view version1.5.0

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

[jira] [Commented] (AMBARI-18152) 'ambari-server --help' not working

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

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Create

[jira] [Updated] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[ https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lav Jain updated AMBARI-17717: -- Status: Open (was: Patch Available) The patch was not favored by Ambari community. Will explore

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18151: --- Labels: 240RMApproved (was: ) > Oozie Hive actions fail when Atlas is installed since

[jira] [Updated] (AMBARI-18165) Hbase RegionServer start fails

[ https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18165: --- Labels: 240RMApproved (was: ) > Hbase RegionServer start fails >

[jira] [Commented] (AMBARI-17717) Ambari should have a script to add new repository and service to existing stack

[ https://issues.apache.org/jira/browse/AMBARI-17717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423262#comment-15423262 ] Lav Jain commented on AMBARI-17717: --- [~Tim Thorpe] Please feel free to update/close this Jira when

[jira] [Updated] (AMBARI-18135) Enable Namenode HA failing at install journal nodes with cluster operator user

[ https://issues.apache.org/jira/browse/AMBARI-18135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18135: --- Labels: 240RMApproved rbac (was: rbac) > Enable Namenode HA failing at install journal

[jira] [Issue Comment Deleted] (AMBARI-18135) Enable Namenode HA failing at install journal nodes with cluster operator user

[ https://issues.apache.org/jira/browse/AMBARI-18135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18135: --- Comment: was deleted (was: Pushing out non-blocker JIRAs from 2.4.0 to 2.5.0 ) > Enable

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[ https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18167: --- Labels: 240RMApproved (was: ) > RU: Kafka brokers restart was stopped during downgrade

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18168: --- Labels: 240RMApproved (was: ) > Create Atlas log4j changes for failed notifications >

[jira] [Commented] (AMBARI-17938) Ambari should not recursively chown for HAWQ hdfs upon every start

[ https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423246#comment-15423246 ] Lav Jain commented on AMBARI-17938: --- Confirmed. Thanks [~jluniya] for taking care of this. > Ambari

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Attachment: rb51144.patch > Create Atlas log4j changes for failed

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Status: Patch Available (was: Open) > Create Atlas log4j changes for

[jira] [Updated] (AMBARI-18168) Create Atlas log4j changes for failed notifications

[ https://issues.apache.org/jira/browse/AMBARI-18168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18168: --- Description: Create Atlas log4j in

[jira] [Created] (AMBARI-18168) Create Atlas log4j changes for failed notifications

Nahappan Somasundaram created AMBARI-18168: -- Summary: Create Atlas log4j changes for failed notifications Key: AMBARI-18168 URL: https://issues.apache.org/jira/browse/AMBARI-18168 Project:

[jira] [Commented] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

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

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[ https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18167: - Status: Patch Available (was: In Progress) > RU: Kafka brokers restart was stopped

[jira] [Commented] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

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

[jira] [Updated] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

[ https://issues.apache.org/jira/browse/AMBARI-18167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated AMBARI-18167: - Attachment: AMBARI-18167.patch > RU: Kafka brokers restart was stopped during downgrade

[jira] [Created] (AMBARI-18167) RU: Kafka brokers restart was stopped during downgrade cluster

Mugdha Varadkar created AMBARI-18167: Summary: RU: Kafka brokers restart was stopped during downgrade cluster Key: AMBARI-18167 URL: https://issues.apache.org/jira/browse/AMBARI-18167 Project:

[jira] [Updated] (AMBARI-18042) Query execution takes a long time in hive view version1.5.0

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

[jira] [Commented] (AMBARI-16764) When "Use Local Repository" option is selected, the stack cannot be changed

[ https://issues.apache.org/jira/browse/AMBARI-16764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423174#comment-15423174 ] Jayush Luniya commented on AMBARI-16764: [~onechiporenko] Moving this out of 2.4.0 to 2.5.0.

[jira] [Updated] (AMBARI-16764) When "Use Local Repository" option is selected, the stack cannot be changed

[ https://issues.apache.org/jira/browse/AMBARI-16764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-16764: --- Fix Version/s: (was: 2.4.0) 2.5.0 > When "Use Local Repository"

[jira] [Created] (AMBARI-18166) configs.sh script updates

Siddharth Wagle created AMBARI-18166: Summary: configs.sh script updates Key: AMBARI-18166 URL: https://issues.apache.org/jira/browse/AMBARI-18166 Project: Ambari Issue Type: Improvement

[jira] [Updated] (AMBARI-18166) configs.sh script updates

[ https://issues.apache.org/jira/browse/AMBARI-18166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-18166: - Affects Version/s: 2.0.0 > configs.sh script updates > - > >

[jira] [Commented] (AMBARI-17888) Create configuration flag to prevent changing of directory permissions

[ https://issues.apache.org/jira/browse/AMBARI-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423153#comment-15423153 ] Siddharth Wagle commented on AMBARI-17888: -- Yes this went into 2.4 branch. cc:[~jluniya] >

[jira] [Updated] (AMBARI-18152) 'ambari-server --help' not working

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

[jira] [Commented] (AMBARI-18165) Hbase RegionServer start fails

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

[jira] [Updated] (AMBARI-18165) Hbase RegionServer start fails

[ https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18165: --- Status: Patch Available (was: Open) > Hbase RegionServer start fails >

[jira] [Updated] (AMBARI-18165) Hbase RegionServer start fails

[ https://issues.apache.org/jira/browse/AMBARI-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18165: --- Attachment: AMBARI-18165.patch > Hbase RegionServer start fails >

[jira] [Created] (AMBARI-18165) Hbase RegionServer start fails

Vitaly Brodetskyi created AMBARI-18165: -- Summary: Hbase RegionServer start fails Key: AMBARI-18165 URL: https://issues.apache.org/jira/browse/AMBARI-18165 Project: Ambari Issue Type:

[jira] [Commented] (AMBARI-18159) Cover widget views with unit tests

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

[jira] [Commented] (AMBARI-18162) Tracebacks of exceptions should always be available

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

[jira] [Resolved] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[ https://issues.apache.org/jira/browse/AMBARI-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-18164. -- Resolution: Fixed > Enable Interactive Query should not be available in Add

[jira] [Commented] (AMBARI-18037) Supervisor service check and restart is failing

[ https://issues.apache.org/jira/browse/AMBARI-18037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423061#comment-15423061 ] Jayush Luniya commented on AMBARI-18037: [~shreyabh...@gmail.com] Can you assign the JIRA to the

[jira] [Commented] (AMBARI-18134) Hive metastore stop failed

[ https://issues.apache.org/jira/browse/AMBARI-18134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423057#comment-15423057 ] Jayush Luniya commented on AMBARI-18134: [~shreyabh...@gmail.com] Can you assign the JIRA to the

[jira] [Commented] (AMBARI-18157) Hive service check is failing after RU

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423058#comment-15423058 ] Jayush Luniya commented on AMBARI-18157: [~shreyabh...@gmail.com] Can you assign the JIRA to the

[jira] [Updated] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[ https://issues.apache.org/jira/browse/AMBARI-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18164: - Status: In Progress (was: Patch Available) committed to trunk and branch-2.4

[jira] [Updated] (AMBARI-17661) Support YARN timeline plugin classpath config

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

[jira] [Updated] (AMBARI-18151) Oozie Hive actions fail when Atlas is installed since Atlas Hive Hooks need to be copied to Oozie Share Lib in HDFS

[ https://issues.apache.org/jira/browse/AMBARI-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18151: --- Priority: Blocker (was: Major) > Oozie Hive actions fail when Atlas is installed since

[jira] [Commented] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

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

[jira] [Updated] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[ https://issues.apache.org/jira/browse/AMBARI-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18164: - Attachment: AMBARI-18164.patch > Enable Interactive Query should not be

[jira] [Updated] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

[ https://issues.apache.org/jira/browse/AMBARI-18164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-18164: - Status: Patch Available (was: Open) > Enable Interactive Query should not be

[jira] [Created] (AMBARI-18164) Enable Interactive Query should not be available in Add Service Wizard

Aleksandr Kovalenko created AMBARI-18164: Summary: Enable Interactive Query should not be available in Add Service Wizard Key: AMBARI-18164 URL: https://issues.apache.org/jira/browse/AMBARI-18164

[jira] [Updated] (AMBARI-18144) Fix Hive JDBC unit tests

[ https://issues.apache.org/jira/browse/AMBARI-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18144: --- Fix Version/s: (was: trunk) 2.4.0 > Fix Hive JDBC unit tests >

[jira] [Commented] (AMBARI-18144) Fix Hive JDBC unit tests

[ https://issues.apache.org/jira/browse/AMBARI-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422972#comment-15422972 ] Jayush Luniya commented on AMBARI-18144: [~dbhowmick] Since this is purely unit test changes we

[jira] [Updated] (AMBARI-17065) Memory leak on ambari-agent

[ https://issues.apache.org/jira/browse/AMBARI-17065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-17065: --- Fix Version/s: (was: 2.5.0) 2.4.0 > Memory leak on ambari-agent >

[jira] [Updated] (AMBARI-18140) Avoid hardcoded values in blueprint for hive and oozie

[ https://issues.apache.org/jira/browse/AMBARI-18140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18140: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Avoid hardcoded values in blueprint

  1   2   >