[jira] [Reopened] (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 reopened AMBARI-15538: Please commit this to branch-2.4 too so that it is in 2.4.2 release. > Support

[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=15494453#comment-15494453 ] Jayush Luniya commented on AMBARI-15538: Ok. But at some stage we will add support multiple

[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=15494441#comment-15494441 ] Jayush Luniya commented on AMBARI-15538: Yes reopened so its not missed. cc: [~bsari] > Support

[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: --- Priority: Critical (was: Major) > Support service-specific repo for add-on services >

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[ https://issues.apache.org/jira/browse/AMBARI-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489471#comment-15489471 ] Jayush Luniya commented on AMBARI-18385: Trunk commit 37e71db741cacb5acc4113131a27d2c1b7ac5791

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[ https://issues.apache.org/jira/browse/AMBARI-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489010#comment-15489010 ] Jayush Luniya commented on AMBARI-18385: [~sumitmohanty] [~mahadev] Can you review the patch for

[jira] [Comment Edited] (AMBARI-18385) Add HDF management pack

[ https://issues.apache.org/jira/browse/AMBARI-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489008#comment-15489008 ] Jayush Luniya edited comment on AMBARI-18385 at 9/14/16 1:16 AM: - {code}

[jira] [Commented] (AMBARI-18385) Add HDF management pack

[ https://issues.apache.org/jira/browse/AMBARI-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15489008#comment-15489008 ] Jayush Luniya commented on AMBARI-18385: {code} mvn clean apache-rat:check cd

[jira] [Updated] (AMBARI-18385) Add HDF management pack

[ https://issues.apache.org/jira/browse/AMBARI-18385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18385: --- Attachment: AMBARI-18385.patch > Add HDF management pack > --- > >

[jira] [Created] (AMBARI-18385) Add HDF management pack

Jayush Luniya created AMBARI-18385: -- Summary: Add HDF management pack Key: AMBARI-18385 URL: https://issues.apache.org/jira/browse/AMBARI-18385 Project: Ambari Issue Type: Bug

[jira] [Comment Edited] (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=15488361#comment-15488361 ] Jayush Luniya edited comment on AMBARI-15538 at 9/13/16 8:42 PM: - [~Tim

[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=15488361#comment-15488361 ] Jayush Luniya commented on AMBARI-15538: [~Tim Thorpe] Latest patch submitted by [~bsari]

[jira] [Resolved] (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 resolved AMBARI-17285. Resolution: Duplicate AMBARI-15538 should address this issue. > Custom service repos in

[jira] [Commented] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484609#comment-15484609 ] Jayush Luniya commented on AMBARI-17728: commit e4cb41e0ab469788180f3ac5741d331706b46ea0 Author:

[jira] [Updated] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user

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

[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-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: --- Priority: Blocker (was: Major) > After upgrading cluster from HDP-2.4.x to HDP-2.5.x and

[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] [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-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-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-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-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-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-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-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-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-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-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-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] [Commented] (AMBARI-18282) By default 2.3.ECS stack should be disabled for HDP

[ https://issues.apache.org/jira/browse/AMBARI-18282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15450473#comment-15450473 ] Jayush Luniya commented on AMBARI-18282: +1 > By default 2.3.ECS stack should be disabled for

[jira] [Updated] (AMBARI-18252) Storm service check fails after disabling kerberos

[ https://issues.apache.org/jira/browse/AMBARI-18252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18252: --- Fix Version/s: (was: 2.4.0) trunk > Storm service check fails after

[jira] [Resolved] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-18239. Resolution: Fixed > oozie.py is reading invalid 'version' attribute which results in not

[jira] [Commented] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433926#comment-15433926 ] Jayush Luniya commented on AMBARI-18239: Trunk commit 6b969905215f32ef333ec9d7b01f43af9c55ba47

[jira] [Commented] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433900#comment-15433900 ] Jayush Luniya commented on AMBARI-18239: Previous patch wouldnt address the issue. New patch

[jira] [Updated] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18239: --- Attachment: (was: AMBARI-18239.patch) > oozie.py is reading invalid 'version' attribute

[jira] [Updated] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18239: --- Attachment: AMBARI-18239.trunk.patch > oozie.py is reading invalid 'version' attribute

[jira] [Updated] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18239: --- Attachment: AMBARI-18239.patch > oozie.py is reading invalid 'version' attribute which

[jira] [Updated] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18239: --- Priority: Critical (was: Major) > oozie.py is reading invalid 'version' attribute which

[jira] [Assigned] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-18239: -- Assignee: Jayush Luniya (was: Ayub Khan) > oozie.py is reading invalid 'version'

[jira] [Updated] (AMBARI-18239) oozie.py is reading invalid 'version' attribute which results in not copying required atlas hook jars

[ https://issues.apache.org/jira/browse/AMBARI-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18239: --- Status: Open (was: Patch Available) > oozie.py is reading invalid 'version' attribute

[jira] [Commented] (AMBARI-18244) Add Service for Atlas did not call conf-select, so failed to find /etc/atlas/conf/users-credentials.properties

[ https://issues.apache.org/jira/browse/AMBARI-18244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15433890#comment-15433890 ] Jayush Luniya commented on AMBARI-18244: +1 > Add Service for Atlas did not call conf-select,

[jira] [Updated] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

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

[jira] [Commented] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

[ https://issues.apache.org/jira/browse/AMBARI-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431297#comment-15431297 ] Jayush Luniya commented on AMBARI-18217: Branch-2.4 commit

[jira] [Commented] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

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

[jira] [Comment Edited] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

[ https://issues.apache.org/jira/browse/AMBARI-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431282#comment-15431282 ] Jayush Luniya edited comment on AMBARI-18217 at 8/22/16 5:52 PM: -

[jira] [Updated] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

[ https://issues.apache.org/jira/browse/AMBARI-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18217: --- Priority: Blocker (was: Critical) > Zeppelin service check fails after enabling SSL for

[jira] [Commented] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

[ https://issues.apache.org/jira/browse/AMBARI-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431282#comment-15431282 ] Jayush Luniya commented on AMBARI-18217: Putting this JIRA back into 2.4 release. > Zeppelin

[jira] [Updated] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

[ https://issues.apache.org/jira/browse/AMBARI-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18217: --- Labels: 240RMApproved (was: ) > Zeppelin service check fails after enabling SSL for

[jira] [Updated] (AMBARI-18217) Zeppelin service check fails after enabling SSL for Zeppelin

[ https://issues.apache.org/jira/browse/AMBARI-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18217: --- Fix Version/s: (was: trunk) 2.4.0 > Zeppelin service check fails

[jira] [Updated] (AMBARI-18219) Ambari should use oozied.sh for stopping oozie so that optional catalina args can be provided

[ https://issues.apache.org/jira/browse/AMBARI-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18219: --- Labels: 240RMApproved (was: ) > Ambari should use oozied.sh for stopping oozie so that

[jira] [Updated] (AMBARI-18221) Oozie server start fails while enabling wire encryption

[ https://issues.apache.org/jira/browse/AMBARI-18221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18221: --- Labels: 240RMApproved (was: ) > Oozie server start fails while enabling wire encryption >

[jira] [Updated] (AMBARI-18213) RU: Storm components were stopped during RU and can not be started

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

[jira] [Commented] (AMBARI-18213) RU: Storm components were stopped during RU and can not be started

[ https://issues.apache.org/jira/browse/AMBARI-18213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429122#comment-15429122 ] Jayush Luniya commented on AMBARI-18213: Looks like this is already committed but the Apache

[jira] [Updated] (AMBARI-18208) Bug Fixing in HueMigration View

[ https://issues.apache.org/jira/browse/AMBARI-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18208: --- Fix Version/s: (was: 2.4.0) trunk > Bug Fixing in HueMigration View

[jira] [Commented] (AMBARI-18208) Bug Fixing in HueMigration View

[ https://issues.apache.org/jira/browse/AMBARI-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429113#comment-15429113 ] Jayush Luniya commented on AMBARI-18208: Moving this out of 2.4.0 since its not a blocker. We

[jira] [Updated] (AMBARI-18213) RU: Storm components were stopped during RU and can not be started

[ https://issues.apache.org/jira/browse/AMBARI-18213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18213: --- Affects Version/s: 2.4.0 > RU: Storm components were stopped during RU and can not be

[jira] [Updated] (AMBARI-18213) RU: Storm components were stopped during RU and can not be started

[ https://issues.apache.org/jira/browse/AMBARI-18213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18213: --- Priority: Blocker (was: Major) > RU: Storm components were stopped during RU and can not

[jira] [Updated] (AMBARI-18213) RU: Storm components were stopped during RU and can not be started

[ https://issues.apache.org/jira/browse/AMBARI-18213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18213: --- Labels: 240RMApproved (was: ) > RU: Storm components were stopped during RU and can not be

[jira] [Commented] (AMBARI-18188) Typo in stack_advisor.py for KAFKA

[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427345#comment-15427345 ] Jayush Luniya commented on AMBARI-18188: commit 2d6ade5a21f2c055ef73a5b8d321a4265c41c6f9 Author:

[jira] [Commented] (AMBARI-18188) Typo in stack_advisor.py for KAFKA

[ https://issues.apache.org/jira/browse/AMBARI-18188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427332#comment-15427332 ] Jayush Luniya commented on AMBARI-18188: -1 for 2.4.0. Backing this out from 2.4 branch as it

[jira] [Resolved] (AMBARI-18197) HBase region server start fails after disabling kerberos

[ https://issues.apache.org/jira/browse/AMBARI-18197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-18197. Resolution: Duplicate > HBase region server start fails after disabling kerberos >

[jira] [Resolved] (AMBARI-18195) HST server down after deploy

[ https://issues.apache.org/jira/browse/AMBARI-18195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-18195. Resolution: Invalid Smartsense was explicitly stopped > HST server down after deploy >

[jira] [Updated] (AMBARI-18142) Define keytab/principal for Spark Thrift Server

[ https://issues.apache.org/jira/browse/AMBARI-18142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18142: --- Labels: 240RMApproved (was: ) > Define keytab/principal for Spark Thrift Server >

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426994#comment-15426994 ] Jayush Luniya commented on AMBARI-18157: 2.4 commit f5b3c238b84c4225603412d69b46bcc8243d56fb

[jira] [Updated] (AMBARI-18157) Hive service check is failing after cluster Kerberization

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

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426992#comment-15426992 ] Jayush Luniya commented on AMBARI-18157: Trunk commit 0e5fb8ee8e205ccb9da889e44ba77ffbde3f86dd

[jira] [Assigned] (AMBARI-18157) Hive service check is failing after cluster Kerberization

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-18157: -- Assignee: Jayush Luniya (was: Dmitry Lysnichenko) > Hive service check is failing

[jira] [Updated] (AMBARI-18202) On UI Sometimes: after clicking delete property button, property does not deleted instead Configuration Group window is opened

[ https://issues.apache.org/jira/browse/AMBARI-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18202: --- Labels: 240RMApproved (was: ) > On UI Sometimes: after clicking delete property button,

[jira] [Updated] (AMBARI-18184) Hive Metastore restart failed during EU with 'Internal credentials cache error' while running kinit

[ https://issues.apache.org/jira/browse/AMBARI-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18184: --- Labels: 240RMApproved (was: ) > Hive Metastore restart failed during EU with 'Internal

[jira] [Updated] (AMBARI-18189) All storm commands failed

[ https://issues.apache.org/jira/browse/AMBARI-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18189: --- Labels: 240RMApproved (was: ) > All storm commands failed > - > >

[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=15425008#comment-15425008 ] Jayush Luniya commented on AMBARI-18157: [~dmitriusan] can you help with getting this fix

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18157: --- Assignee: Dmitry Lysnichenko > Hive service check is failing after RU >

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18157: --- External issue ID: (was: BUG-64471) > Hive service check is failing after RU >

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18157: --- Labels: 240RMApproved system_test (was: system_test) > Hive service check is failing after

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18157: --- Fix Version/s: (was: 2.5.0) 2.4.0 > Hive service check is failing

[jira] [Updated] (AMBARI-18182) After the upgrade of jetty, zeppelin-view fails to load

[ https://issues.apache.org/jira/browse/AMBARI-18182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18182: --- Labels: 240RMApproved (was: ) > After the upgrade of jetty, zeppelin-view fails to load >

[jira] [Updated] (AMBARI-18178) yarn capacity scheduler queue issue

[ https://issues.apache.org/jira/browse/AMBARI-18178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18178: --- Labels: 240RMApproved (was: ) > yarn capacity scheduler queue issue >

[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 ] Jayush Luniya updated AMBARI-18172: --- Labels: 240RMApproved (was: ) > Hive Service check is failing after moving webhcat server

[jira] [Updated] (AMBARI-16028) Namenode marked as INITIAL standby could potentially never start if other namenode is down

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

[jira] [Commented] (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:comment-tabpanel=15423973#comment-15423973 ] Jayush Luniya commented on AMBARI-18172: Please send email to d...@apache.ambari.org for

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

[ https://issues.apache.org/jira/browse/AMBARI-18157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18157: --- Fix Version/s: (was: 2.4.0) 2.5.0 > Hive service check is failing

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

[ https://issues.apache.org/jira/browse/AMBARI-18134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18134: --- Fix Version/s: (was: 2.4.0) 2.5.0 > Hive metastore stop failed >

[jira] [Updated] (AMBARI-18080) EU/RU merges empty storm.topology.submission.notifier.plugin.class which cause service check to fail

[ https://issues.apache.org/jira/browse/AMBARI-18080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-18080: --- Fix Version/s: (was: 2.4.0) 2.5.0 > EU/RU merges empty

[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] [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] [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] [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-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] [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

<    2   3   4   5   6   7   8   9   10   11   >