[jira] [Commented] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086893#comment-16086893
]
Hadoop QA commented on AMBARI-21471:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12877234/AMBARI-21471.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11782//console
This message is automatically generated.
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21471:
---
Attachment: (was: AMBARI-21471.patch)
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21471:
---
Attachment: AMBARI-21471.patch
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21471:
---
Status: Patch Available (was: Open)
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086882#comment-16086882
]
Siddharth Wagle edited comment on AMBARI-21471 at 7/14/17 5:30 AM:
---
+1 LGTM, however this could be handled by the upper layers.
was (Author: swagle):
+1 LGTM
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086882#comment-16086882
]
Siddharth Wagle commented on AMBARI-21471:
--
+1 LGTM
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty reassigned AMBARI-21471:
--
Assignee: Sumit Mohanty
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21471:
---
Attachment: AMBARI-21471.patch
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
> Fix For: 2.5.2
>
> Attachments: AMBARI-21471.patch
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086874#comment-16086874
]
Sumit Mohanty commented on AMBARI-21471:
This is because the following config property has a wrong value
{code}
yarn.timeline-service.entity-group-fs-store.group-id-plugin-classpath
{HDP:/usr/hdp}/${hdp.version}/spark/hdpLib/*
{code}
This is because the stack advisor needs a logic to parse out the root path per
stack.
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
> Fix For: 2.5.2
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
> ... 7 more
> 2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status -1
> 2017-07-12 02:48:01,551 INFO
> applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45))
> - SHUTDOWN_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
[
https://issues.apache.org/jira/browse/AMBARI-21471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-21471:
---
Description:
ATS is going down with
{code}
2017-07-12 02:48:01,542 FATAL
applicationhistoryservice.ApplicationHistoryServer
(ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
ApplicationHistoryServer
java.lang.RuntimeException: No class defined for
org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
at
org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
at
org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
Caused by: java.lang.ClassNotFoundException:
org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at
org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
at
org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at
org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:243)
... 7 more
2017-07-12 02:48:01,544 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
Exiting with status -1
2017-07-12 02:48:01,551 INFO
applicationhistoryservice.ApplicationHistoryServer (LogAdapter.java:info(45)) -
SHUTDOWN_MSG:
{code}
> ATS going down due to missing
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
>
>
> Key: AMBARI-21471
> URL: https://issues.apache.org/jira/browse/AMBARI-21471
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Sumit Mohanty
> Fix For: 2.5.2
>
>
> ATS is going down with
> {code}
> 2017-07-12 02:48:01,542 FATAL
> applicationhistoryservice.ApplicationHistoryServer
> (ApplicationHistoryServer.java:launchAppHistoryServer(177)) - Error starting
> ApplicationHistoryServer
> java.lang.RuntimeException: No class defined for
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.loadPlugIns(EntityGroupFSTimelineStore.java:256)
> at
> org.apache.hadoop.yarn.server.timeline.EntityGroupFSTimelineStore.serviceInit(EntityGroupFSTimelineStore.java:196)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.serviceInit(ApplicationHistoryServer.java:111)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.launchAppHistoryServer(ApplicationHistoryServer.java:174)
> at
> org.apache.hadoop.yarn.server.applicationhistoryservice.ApplicationHistoryServer.main(ApplicationHistoryServer.java:184)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:197)
> at
> org.apache.hadoop.util.ApplicationClassLoader.loadClass(ApplicationClassLoader.java:165)
> at java.lang.Class.forName0(Native
[jira] [Created] (AMBARI-21471) ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin
Sumit Mohanty created AMBARI-21471: -- Summary: ATS going down due to missing org.apache.spark.deploy.history.yarn.plugin.SparkATSPlugin Key: AMBARI-21471 URL: https://issues.apache.org/jira/browse/AMBARI-21471 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: 2.5.2 Reporter: Sumit Mohanty Fix For: 2.5.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086645#comment-16086645
]
Hudson commented on AMBARI-21463:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1684 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1684/])
AMBARI-21463. Cross-stack upgrade, Oozie restart fails with ext-2.2.zip
(afernandez:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2c6d53f70bcaa6aee789e6d026cc06990acd16c])
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py
* (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/metainfo.xml
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_tools.py
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-21463.
--
Resolution: Fixed
Pushed to branch-2.5,
commit d2c6d53f70bcaa6aee789e6d026cc06990acd16c
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21470) Kafka Sink does not exclude excluded metrics of type 'guage'
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21470: --- Summary: Kafka Sink does not exclude excluded metrics of type 'guage' (was: Kafka Broker Metrics show no data) > Kafka Sink does not exclude excluded metrics of type 'guage' > > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21470) Kafka Broker Metrics show no data
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086600#comment-16086600 ] Siddharth Wagle commented on AMBARI-21470: -- +1 for the patch. > Kafka Broker Metrics show no data > - > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21470) Kafka Broker Metrics show no data
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086599#comment-16086599 ] Siddharth Wagle commented on AMBARI-21470: -- Can you change title to reflect patch adds value to the excluded field? Nothing in the patch reflects fixing functionality. > Kafka Broker Metrics show no data > - > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Description:
Oozie Server restart failed due to this: Unable to copy
/usr/share/HDP-oozie/ext-2.2.zip because it does not exist
Doesn't look like HDP rpms created this path:
{code}
[root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
-rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
[root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
-rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
/usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
{code}
The ext2js rpm seems to come from IOPUtils:
{code}
[root@sid-test-2 oozie]# yum list | grep extjs
extjs.noarch 2.2_IBM_2-1
@IOP-UTILS-1.3
[root@sid-test-2 oozie]# rpm -qa | grep extjs
extjs-2.2_IBM_2-1.noarch
{code}
We should swap the source from
{noformat}
/usr/share/HDP-oozie/ext-2.2.zip
{noformat}
to
{noformat}
/usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
{noformat}
since the latter does exist.
Also, restarting Oozie Clients during EU is failing because stack_tools.py is
missing the "get_stack_name" function in the __all__ variable.
Lastly, disable showing the BigInsights stack by default in the UI.
was:
Oozie Server restart failed due to this: Unable to copy
/usr/share/HDP-oozie/ext-2.2.zip because it does not exist
Doesn't look like HDP rpms created this path:
{code}
[root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
-rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
[root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
-rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
/usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
{code}
The ext2js rpm seems to come from IOPUtils:
{code}
[root@sid-test-2 oozie]# yum list | grep extjs
extjs.noarch 2.2_IBM_2-1
@IOP-UTILS-1.3
[root@sid-test-2 oozie]# rpm -qa | grep extjs
extjs-2.2_IBM_2-1.noarch
{code}
We should swap the source from
{noformat}
/usr/share/HDP-oozie/ext-2.2.zip
{noformat}
to
{noformat}
/usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
{noformat}
since the latter does exist.
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
> Also, restarting Oozie Clients during EU is failing because stack_tools.py is
> missing the "get_stack_name" function in the __all__ variable.
> Lastly, disable showing the BigInsights stack by default in the UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21463) Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
[
https://issues.apache.org/jira/browse/AMBARI-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21463:
-
Summary: Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing
error, stack_tools.py is missing get_stack_name in __all__, disable BigInsights
in UI (was: Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing
error)
> Cross-stack upgrade, Oozie restart fails with ext-2.2.zip missing error,
> stack_tools.py is missing get_stack_name in __all__, disable BigInsights in UI
> ---
>
> Key: AMBARI-21463
> URL: https://issues.apache.org/jira/browse/AMBARI-21463
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
>
> Oozie Server restart failed due to this: Unable to copy
> /usr/share/HDP-oozie/ext-2.2.zip because it does not exist
> Doesn't look like HDP rpms created this path:
> {code}
> [root@sid-test-2 ~]# ls -l /var/lib/oozie/ext-2.2.zip
> -rwxr-xr-x. 1 oozie hadoop 6800612 Jul 5 18:03 /var/lib/oozie/ext-2.2.zip
> [root@sid-test-2 ~]# ls -l /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> -rw-r--r--. 1 oozie hadoop 6800612 Jul 6 16:36
> /usr/hdp/2.6.1.0-129/oozie/libext/ext-2.2.zip
> {code}
> The ext2js rpm seems to come from IOPUtils:
> {code}
> [root@sid-test-2 oozie]# yum list | grep extjs
> extjs.noarch 2.2_IBM_2-1
> @IOP-UTILS-1.3
> [root@sid-test-2 oozie]# rpm -qa | grep extjs
> extjs-2.2_IBM_2-1.noarch
> {code}
> We should swap the source from
> {noformat}
> /usr/share/HDP-oozie/ext-2.2.zip
> {noformat}
> to
> {noformat}
> /usr/share/BIGINSIGHTS-oozie/ext-2.2.zip
> {noformat}
> since the latter does exist.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21436) Create pre-requisite check for components missing from the target stack
[ https://issues.apache.org/jira/browse/AMBARI-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086517#comment-16086517 ] Hudson commented on AMBARI-21436: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1683 (See [https://builds.apache.org/job/Ambari-branch-2.5/1683/]) AMBARI-21436 - Add a Prerequisite Check To Ensure that the Target Stack (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=113b381ecc530e7b1daf9a4cd7e546c1631df451]) * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/ComponentsExistInRepoCheck.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/host/HostImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/ComponentExistsInRepoCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Host.java > Create pre-requisite check for components missing from the target stack > --- > > Key: AMBARI-21436 > URL: https://issues.apache.org/jira/browse/AMBARI-21436 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Doroszlai, Attila >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21436.patch > > > When upgrading from a stack which contains a component that doesn't exist in > the target stack, the upgrade will run into a problem while attempting to > restart that component. There should be a pre-requisite check which > guarantees that components/services missing from the target stack are removed > before upgrading. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21469) Stop Spark fails due to missing stack selector
[
https://issues.apache.org/jira/browse/AMBARI-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086452#comment-16086452
]
Hudson commented on AMBARI-21469:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1682 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1682/])
AMBARI-21469. Stop Spark fails due to missing stack selector (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7dbcb7542e0d6d58fe11b6549e3c2c07574258a6])
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2/services/HBASE/package/scripts/params.py
* (edit)
ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SPARK/package/scripts/params.py
> Stop Spark fails due to missing stack selector
> --
>
> Key: AMBARI-21469
> URL: https://issues.apache.org/jira/browse/AMBARI-21469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21469.patch
>
>
> BigInsights 4.2 stack has hard-coded call to {{iop-select}} in Spark and
> HBase scripts. This causes failure stopping services during cross stack-name
> upgrade, when {{iop-select}} is already removed.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
> line 167, in
> JobHistoryServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
> line 55, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/params.py",
> line 42, in
> iop_full_version = get_iop_version()
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/spark.py",
> line 345, in get_iop_version
> 'Unable to determine the current version because of a non-zero return
> code of {0}'.format(str(return_code)))
> resource_management.core.exceptions.Fail: Unable to determine the current
> version because of a non-zero return code of 127
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21436) Create pre-requisite check for components missing from the target stack
[ https://issues.apache.org/jira/browse/AMBARI-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21436: - Attachment: AMBARI-21436.patch > Create pre-requisite check for components missing from the target stack > --- > > Key: AMBARI-21436 > URL: https://issues.apache.org/jira/browse/AMBARI-21436 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Doroszlai, Attila >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21436.patch > > > When upgrading from a stack which contains a component that doesn't exist in > the target stack, the upgrade will run into a problem while attempting to > restart that component. There should be a pre-requisite check which > guarantees that components/services missing from the target stack are removed > before upgrading. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21436) Create pre-requisite check for components missing from the target stack
[ https://issues.apache.org/jira/browse/AMBARI-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21436: - Resolution: Fixed Status: Resolved (was: Patch Available) > Create pre-requisite check for components missing from the target stack > --- > > Key: AMBARI-21436 > URL: https://issues.apache.org/jira/browse/AMBARI-21436 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Doroszlai, Attila >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21436.patch > > > When upgrading from a stack which contains a component that doesn't exist in > the target stack, the upgrade will run into a problem while attempting to > restart that component. There should be a pre-requisite check which > guarantees that components/services missing from the target stack are removed > before upgrading. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21436) Create pre-requisite check for components missing from the target stack
[ https://issues.apache.org/jira/browse/AMBARI-21436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-21436: - Status: Patch Available (was: In Progress) > Create pre-requisite check for components missing from the target stack > --- > > Key: AMBARI-21436 > URL: https://issues.apache.org/jira/browse/AMBARI-21436 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Doroszlai, Attila >Assignee: Jonathan Hurley >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21436.patch > > > When upgrading from a stack which contains a component that doesn't exist in > the target stack, the upgrade will run into a problem while attempting to > restart that component. There should be a pre-requisite check which > guarantees that components/services missing from the target stack are removed > before upgrading. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21470) Kafka Broker Metrics show no data
[
https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086385#comment-16086385
]
Aravindan Vijayan commented on AMBARI-21470:
mvn clean test passed.
{code}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] utility SUCCESS [ 2.081 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 4.405 s]
[INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.997 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 8.676 s
[INFO] Finished at: 2017-07-13T13:24:09-07:00
[INFO] Final Memory: 58M/1333M
[INFO]
{code}
> Kafka Broker Metrics show no data
> -
>
> Key: AMBARI-21470
> URL: https://issues.apache.org/jira/browse/AMBARI-21470
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.2
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 2.5.2
>
> Attachments: AMBARI-21470.patch
>
>
> Preparing this patch on behalf of [~qinliu] who fixed the bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21470) Kafka Broker Metrics show no data
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21470: --- Status: Patch Available (was: Open) > Kafka Broker Metrics show no data > - > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21470) Kafka Broker Metrics show no data
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21470: --- Attachment: AMBARI-21470.patch > Kafka Broker Metrics show no data > - > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21470) Kafka Broker Metrics show no data
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086383#comment-16086383 ] Aravindan Vijayan commented on AMBARI-21470: [~swagle] / [~dsen] Can you review the minor changes? > Kafka Broker Metrics show no data > - > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21470) Kafka Broker Metrics show no data
Aravindan Vijayan created AMBARI-21470: -- Summary: Kafka Broker Metrics show no data Key: AMBARI-21470 URL: https://issues.apache.org/jira/browse/AMBARI-21470 Project: Ambari Issue Type: Bug Affects Versions: 2.5.2 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 2.5.2 Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandana Mirashi updated AMBARI-21325: -- Status: Patch Available (was: Open) > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandana Mirashi updated AMBARI-21325: -- Attachment: (was: AMBARI-21325) > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandana Mirashi updated AMBARI-21325: -- Attachment: AMBARI-21325.patch > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandana Mirashi updated AMBARI-21325: -- Status: Open (was: Patch Available) > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21469) Stop Spark fails due to missing stack selector
[
https://issues.apache.org/jira/browse/AMBARI-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21469:
---
Status: Patch Available (was: In Progress)
> Stop Spark fails due to missing stack selector
> --
>
> Key: AMBARI-21469
> URL: https://issues.apache.org/jira/browse/AMBARI-21469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21469.patch
>
>
> BigInsights 4.2 stack has hard-coded call to {{iop-select}} in Spark and
> HBase scripts. This causes failure stopping services during cross stack-name
> upgrade, when {{iop-select}} is already removed.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
> line 167, in
> JobHistoryServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
> line 55, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/params.py",
> line 42, in
> iop_full_version = get_iop_version()
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/spark.py",
> line 345, in get_iop_version
> 'Unable to determine the current version because of a non-zero return
> code of {0}'.format(str(return_code)))
> resource_management.core.exceptions.Fail: Unable to determine the current
> version because of a non-zero return code of 127
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21469) Stop Spark fails due to missing stack selector
[
https://issues.apache.org/jira/browse/AMBARI-21469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21469:
---
Attachment: AMBARI-21469.patch
> Stop Spark fails due to missing stack selector
> --
>
> Key: AMBARI-21469
> URL: https://issues.apache.org/jira/browse/AMBARI-21469
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21469.patch
>
>
> BigInsights 4.2 stack has hard-coded call to {{iop-select}} in Spark and
> HBase scripts. This causes failure stopping services during cross stack-name
> upgrade, when {{iop-select}} is already removed.
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
> line 167, in
> JobHistoryServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
> line 55, in stop
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/params.py",
> line 42, in
> iop_full_version = get_iop_version()
> File
> "/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/spark.py",
> line 345, in get_iop_version
> 'Unable to determine the current version because of a non-zero return
> code of {0}'.format(str(return_code)))
> resource_management.core.exceptions.Fail: Unable to determine the current
> version because of a non-zero return code of 127
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21456) Fix unit tests in branch-feature-AMBARI-14714 after merging latest trunk
[ https://issues.apache.org/jira/browse/AMBARI-21456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan resolved AMBARI-21456. Resolution: Fixed > Fix unit tests in branch-feature-AMBARI-14714 after merging latest trunk > > > Key: AMBARI-21456 > URL: https://issues.apache.org/jira/browse/AMBARI-21456 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21469) Stop Spark fails due to missing stack selector
Doroszlai, Attila created AMBARI-21469:
--
Summary: Stop Spark fails due to missing stack selector
Key: AMBARI-21469
URL: https://issues.apache.org/jira/browse/AMBARI-21469
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Blocker
Fix For: 2.5.2
BigInsights 4.2 stack has hard-coded call to {{iop-select}} in Spark and HBase
scripts. This causes failure stopping services during cross stack-name
upgrade, when {{iop-select}} is already removed.
{noformat}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
line 167, in
JobHistoryServer().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 329, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/job_history_server.py",
line 55, in stop
import params
File
"/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/params.py",
line 42, in
iop_full_version = get_iop_version()
File
"/var/lib/ambari-agent/cache/stacks/BigInsights/4.2/services/SPARK/package/scripts/spark.py",
line 345, in get_iop_version
'Unable to determine the current version because of a non-zero return code
of {0}'.format(str(return_code)))
resource_management.core.exceptions.Fail: Unable to determine the current
version because of a non-zero return code of 127
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21461) Spark thrift server restart fails during migration EU
[ https://issues.apache.org/jira/browse/AMBARI-21461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086160#comment-16086160 ] Hudson commented on AMBARI-21461: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1681 (See [https://builds.apache.org/job/Ambari-branch-2.5/1681/]) AMBARI-21461 Spark thrift server restart fails during migration EU (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=33c279cf272e824d1efdea1aec7bba667b618596]) * (add) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SPARK/package/scripts/spark_thrift_server.py * (add) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/SPARK/package/scripts/spark_thrift_server.py * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SPARK/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/SPARK/metainfo.xml * (delete) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/SPARK/package/scripts/thrift_server.py * (delete) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/SPARK/package/scripts/thrift_server.py > Spark thrift server restart fails during migration EU > - > > Key: AMBARI-21461 > URL: https://issues.apache.org/jira/browse/AMBARI-21461 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: branch-feature-AMBARI-21348 >Reporter: Di Li >Assignee: Di Li > Fix For: branch-feature-AMBARI-21348 > > Attachments: AMBARI-21461.patch > > > Spark in IOP 4.2 BigInsights stack uses script name "thrift_server.py" > instead of "spark_thrift_server.py" used by the common service Spark and the > IOP 4.2.5 BigInsights stack. > This seemed to have caused the following error during migration EU where > Spark thrift server failed to restart. > """ > Caught an exception while executing custom service command: 'ambari_agent.AgentException.AgentException'>: 'Script > /var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/thrift_server.py > does not exist'; 'Script > /var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/thrift_server.py > does not exist' > """ > We should be able to fix it by renaming "thrift_server.py" used in BI 4.2 > stack to "spark_thrift_server.py" and updating metainfo.xml files > accordingly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21453) Restart Hive after Install Packages fails with err on Condition with name 'should_install_mysl_connector'
[ https://issues.apache.org/jira/browse/AMBARI-21453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086101#comment-16086101 ] Hudson commented on AMBARI-21453: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1680 (See [https://builds.apache.org/job/Ambari-branch-2.5/1680/]) AMBARI-21453 Restart Hive after Install Packages fails with err on (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c5f2efa0b870590aeb28baaefed2fac8d88bf38d]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.0/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/services/SQOOP/metainfo.xml > Restart Hive after Install Packages fails with err on Condition with name > 'should_install_mysl_connector' > - > > Key: AMBARI-21453 > URL: https://issues.apache.org/jira/browse/AMBARI-21453 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: branch-feature-AMBARI-21348 >Reporter: Di Li >Assignee: Di Li > Fix For: branch-feature-AMBARI-21348 > > Attachments: AMBARI-21453.patch > > > Restart Hive after Install Packages fails with err on Condition with name > 'should_install_mysl_connector' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21419) EU to auto switch to HDP tomcat for Oozie
[ https://issues.apache.org/jira/browse/AMBARI-21419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086102#comment-16086102 ] Hudson commented on AMBARI-21419: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1680 (See [https://builds.apache.org/job/Ambari-branch-2.5/1680/]) AMBARI-21419 EU to auto switch to HDP tomcat for Oozie - updated config (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=94eb0ddf5b3da68e239a9600bf5393f5de5677ec]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml > EU to auto switch to HDP tomcat for Oozie > - > > Key: AMBARI-21419 > URL: https://issues.apache.org/jira/browse/AMBARI-21419 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: branch-feature-AMBARI-21348 >Reporter: Di Li >Assignee: Di Li > Fix For: branch-feature-AMBARI-21348 > > Attachments: AMBARI-21419.patch > > > Oozie in IOP 4.2.5 uses Tomcat 7 while HDP 2.6 Oozie uses Tomcat 6. EU > needs to switch Tomcat so Oozie can restart during and post EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21461) Spark thrift server restart fails during migration EU
[ https://issues.apache.org/jira/browse/AMBARI-21461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086085#comment-16086085 ] Di Li commented on AMBARI-21461: pushed to branch-2.5 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=33c279cf272e824d1efdea1aec7bba667b618596 > Spark thrift server restart fails during migration EU > - > > Key: AMBARI-21461 > URL: https://issues.apache.org/jira/browse/AMBARI-21461 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: branch-feature-AMBARI-21348 >Reporter: Di Li >Assignee: Di Li > Fix For: branch-feature-AMBARI-21348 > > Attachments: AMBARI-21461.patch > > > Spark in IOP 4.2 BigInsights stack uses script name "thrift_server.py" > instead of "spark_thrift_server.py" used by the common service Spark and the > IOP 4.2.5 BigInsights stack. > This seemed to have caused the following error during migration EU where > Spark thrift server failed to restart. > """ > Caught an exception while executing custom service command: 'ambari_agent.AgentException.AgentException'>: 'Script > /var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/thrift_server.py > does not exist'; 'Script > /var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/thrift_server.py > does not exist' > """ > We should be able to fix it by renaming "thrift_server.py" used in BI 4.2 > stack to "spark_thrift_server.py" and updating metainfo.xml files > accordingly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21461) Spark thrift server restart fails during migration EU
[ https://issues.apache.org/jira/browse/AMBARI-21461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21461: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Spark thrift server restart fails during migration EU > - > > Key: AMBARI-21461 > URL: https://issues.apache.org/jira/browse/AMBARI-21461 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: branch-feature-AMBARI-21348 >Reporter: Di Li >Assignee: Di Li > Fix For: branch-feature-AMBARI-21348 > > Attachments: AMBARI-21461.patch > > > Spark in IOP 4.2 BigInsights stack uses script name "thrift_server.py" > instead of "spark_thrift_server.py" used by the common service Spark and the > IOP 4.2.5 BigInsights stack. > This seemed to have caused the following error during migration EU where > Spark thrift server failed to restart. > """ > Caught an exception while executing custom service command: 'ambari_agent.AgentException.AgentException'>: 'Script > /var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/thrift_server.py > does not exist'; 'Script > /var/lib/ambari-agent/cache/common-services/SPARK/1.2.1/package/scripts/thrift_server.py > does not exist' > """ > We should be able to fix it by renaming "thrift_server.py" used in BI 4.2 > stack to "spark_thrift_server.py" and updating metainfo.xml files > accordingly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21355) Upgrade to Ambari Server 2.5.1 breaks common-services provided by MPacks
[
https://issues.apache.org/jira/browse/AMBARI-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi resolved AMBARI-21355.
Resolution: Duplicate
> Upgrade to Ambari Server 2.5.1 breaks common-services provided by MPacks
>
>
> Key: AMBARI-21355
> URL: https://issues.apache.org/jira/browse/AMBARI-21355
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-upgrade
>Affects Versions: 2.5.0
> Environment: Ubuntu Linux 14.04
>Reporter: David Kaspar
>Assignee: Vitaly Brodetskyi
>
> *How to reproduce:*
> * Have your own MPack that is similar to one that is located at
> "contrib/management-packs/microsoft-r_mpack" in Ambari source code
> * Have an Ambari Server 2.4.3 with the MPack installed in a cluster
> * Upgrade Ambari-Server to 2.5.1 version
> *Expected Behavior:*
> Ambari Server is upgraded and MPack is still installed and used
> *Actual Behavior:*
> When running {{ambari-server upgrade}}, it fails with the following error
> message:
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> ERROR: Unexpected OSError: [Errno 17] File exists
> For more info run ambari-server with -v or --verbose option
> {code}
> *The following steps are used for Ambari-Server upgrade:*
> {code}
> service ambari-server stop
> ambari-agent stop
> wget -nv
> http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.5.1.0/ambari.list
> -O /etc/apt/sources.list.d/ambari.list
> apt-get clean all
> apt-get update
> apt-get install ambari-server
> apt-get install ambari-agent
> ambari-server upgrade
> {code}
> *Analyses:*
> Usually when such a common service is installed from MPack, a new directory
> (named by the service) is created in
> {{/var/lib/ambari-server/resources/common-services/}} directory. The service
> directory contain a single symbolic link (named by the version of the
> service) and targets
> {{/var/lib/ambari-server/resources/mpacks/-/common-services//}}
> It seems that the whole upgrade process works correctly until
> {code}ambari-server upgrade{code} command runs
> {{find_and_copy_custom_services}} function that re-creates common-services
> from the backup directory that is created during {{apt-get install
> ambari-server}}. The backup directory is correctly having the symbolic link
> in it while the newly created
> {{/var/lib/ambari-server/resources/common-services/}} is NOT having the
> symbolic link. Instead it contains full-deep copy of the directory targeted
> by the original symbolic link.
> *Proposed Solution:*
> Replace the following line in
> {{ambari-server/src/main/python/ambari_server/serverUpgrade.py}}:
> {code}
> shutil.copytree(backup_service,
> os.path.join(current_base_service_dir,service_name))
> {code}
> with:
> {code}
> shutil.copytree(backup_service,
> os.path.join(current_base_service_dir,service_name), True)
> {code}
> so the service directory gets copied while keeping symbolic links.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21355) Upgrade to Ambari Server 2.5.1 breaks common-services provided by MPacks
[
https://issues.apache.org/jira/browse/AMBARI-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-21355:
---
Fix Version/s: 2.5.3
> Upgrade to Ambari Server 2.5.1 breaks common-services provided by MPacks
>
>
> Key: AMBARI-21355
> URL: https://issues.apache.org/jira/browse/AMBARI-21355
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-upgrade
>Affects Versions: 2.5.0
> Environment: Ubuntu Linux 14.04
>Reporter: David Kaspar
>Assignee: Vitaly Brodetskyi
> Fix For: 2.5.3
>
>
> *How to reproduce:*
> * Have your own MPack that is similar to one that is located at
> "contrib/management-packs/microsoft-r_mpack" in Ambari source code
> * Have an Ambari Server 2.4.3 with the MPack installed in a cluster
> * Upgrade Ambari-Server to 2.5.1 version
> *Expected Behavior:*
> Ambari Server is upgraded and MPack is still installed and used
> *Actual Behavior:*
> When running {{ambari-server upgrade}}, it fails with the following error
> message:
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> ERROR: Unexpected OSError: [Errno 17] File exists
> For more info run ambari-server with -v or --verbose option
> {code}
> *The following steps are used for Ambari-Server upgrade:*
> {code}
> service ambari-server stop
> ambari-agent stop
> wget -nv
> http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.5.1.0/ambari.list
> -O /etc/apt/sources.list.d/ambari.list
> apt-get clean all
> apt-get update
> apt-get install ambari-server
> apt-get install ambari-agent
> ambari-server upgrade
> {code}
> *Analyses:*
> Usually when such a common service is installed from MPack, a new directory
> (named by the service) is created in
> {{/var/lib/ambari-server/resources/common-services/}} directory. The service
> directory contain a single symbolic link (named by the version of the
> service) and targets
> {{/var/lib/ambari-server/resources/mpacks/-/common-services//}}
> It seems that the whole upgrade process works correctly until
> {code}ambari-server upgrade{code} command runs
> {{find_and_copy_custom_services}} function that re-creates common-services
> from the backup directory that is created during {{apt-get install
> ambari-server}}. The backup directory is correctly having the symbolic link
> in it while the newly created
> {{/var/lib/ambari-server/resources/common-services/}} is NOT having the
> symbolic link. Instead it contains full-deep copy of the directory targeted
> by the original symbolic link.
> *Proposed Solution:*
> Replace the following line in
> {{ambari-server/src/main/python/ambari_server/serverUpgrade.py}}:
> {code}
> shutil.copytree(backup_service,
> os.path.join(current_base_service_dir,service_name))
> {code}
> with:
> {code}
> shutil.copytree(backup_service,
> os.path.join(current_base_service_dir,service_name), True)
> {code}
> so the service directory gets copied while keeping symbolic links.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21355) Upgrade to Ambari Server 2.5.1 breaks common-services provided by MPacks
[
https://issues.apache.org/jira/browse/AMBARI-21355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi reassigned AMBARI-21355:
--
Assignee: Vitaly Brodetskyi
> Upgrade to Ambari Server 2.5.1 breaks common-services provided by MPacks
>
>
> Key: AMBARI-21355
> URL: https://issues.apache.org/jira/browse/AMBARI-21355
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-upgrade
>Affects Versions: 2.5.0
> Environment: Ubuntu Linux 14.04
>Reporter: David Kaspar
>Assignee: Vitaly Brodetskyi
>
> *How to reproduce:*
> * Have your own MPack that is similar to one that is located at
> "contrib/management-packs/microsoft-r_mpack" in Ambari source code
> * Have an Ambari Server 2.4.3 with the MPack installed in a cluster
> * Upgrade Ambari-Server to 2.5.1 version
> *Expected Behavior:*
> Ambari Server is upgraded and MPack is still installed and used
> *Actual Behavior:*
> When running {{ambari-server upgrade}}, it fails with the following error
> message:
> {code}
> Using python /usr/bin/python
> Upgrading ambari-server
> INFO: Upgrade Ambari Server
> INFO: Updating Ambari Server properties in ambari.properties ...
> INFO: Updating Ambari Server properties in ambari-env.sh ...
> WARNING: Original file ambari-env.sh kept
> ERROR: Unexpected OSError: [Errno 17] File exists
> For more info run ambari-server with -v or --verbose option
> {code}
> *The following steps are used for Ambari-Server upgrade:*
> {code}
> service ambari-server stop
> ambari-agent stop
> wget -nv
> http://public-repo-1.hortonworks.com/ambari/ubuntu14/2.x/updates/2.5.1.0/ambari.list
> -O /etc/apt/sources.list.d/ambari.list
> apt-get clean all
> apt-get update
> apt-get install ambari-server
> apt-get install ambari-agent
> ambari-server upgrade
> {code}
> *Analyses:*
> Usually when such a common service is installed from MPack, a new directory
> (named by the service) is created in
> {{/var/lib/ambari-server/resources/common-services/}} directory. The service
> directory contain a single symbolic link (named by the version of the
> service) and targets
> {{/var/lib/ambari-server/resources/mpacks/-/common-services//}}
> It seems that the whole upgrade process works correctly until
> {code}ambari-server upgrade{code} command runs
> {{find_and_copy_custom_services}} function that re-creates common-services
> from the backup directory that is created during {{apt-get install
> ambari-server}}. The backup directory is correctly having the symbolic link
> in it while the newly created
> {{/var/lib/ambari-server/resources/common-services/}} is NOT having the
> symbolic link. Instead it contains full-deep copy of the directory targeted
> by the original symbolic link.
> *Proposed Solution:*
> Replace the following line in
> {{ambari-server/src/main/python/ambari_server/serverUpgrade.py}}:
> {code}
> shutil.copytree(backup_service,
> os.path.join(current_base_service_dir,service_name))
> {code}
> with:
> {code}
> shutil.copytree(backup_service,
> os.path.join(current_base_service_dir,service_name), True)
> {code}
> so the service directory gets copied while keeping symbolic links.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21234) Ambari rack awareness for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ambud Sharma updated AMBARI-21234: -- Attachment: AMBARI-21234-2.5.diff AMBARI-21234-trunk.diff > Ambari rack awareness for Kafka > --- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Ambud Sharma >Assignee: Sebastian Toader > Fix For: 2.5.2 > > Attachments: AMBARI-21234-2.5.diff, AMBARI-21234-trunk.diff > > > As an operations person it would be nice to manage Kafka rack awareness via > Ambari. Ambari allows node rack information to be configured and this > information can then be pulled in the Kafka stack and populated in the > server.properties file for Kafka. > Design: > This stack change uses the /clusterHostInfo/all_hosts and > /clusterHostInfo/all_racks paths and materializes them to a variable. Then it > uses linear search to find this node in the list of all hosts and it's > corresponding rack id. This information is then stored in a variable called > rack and which is materialized during the configure method of the broker > scripts. > This stack change relies on the node rack information stored in Ambari > therefore will enable both Ambari UI and Blueprints to be used for setting up > Kafka broker rack information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21234) Ambari rack awareness for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ambud Sharma updated AMBARI-21234: -- Attachment: (was: AMBARI-21234-trunk.diff) > Ambari rack awareness for Kafka > --- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Ambud Sharma >Assignee: Sebastian Toader > Fix For: 2.5.2 > > > As an operations person it would be nice to manage Kafka rack awareness via > Ambari. Ambari allows node rack information to be configured and this > information can then be pulled in the Kafka stack and populated in the > server.properties file for Kafka. > Design: > This stack change uses the /clusterHostInfo/all_hosts and > /clusterHostInfo/all_racks paths and materializes them to a variable. Then it > uses linear search to find this node in the list of all hosts and it's > corresponding rack id. This information is then stored in a variable called > rack and which is materialized during the configure method of the broker > scripts. > This stack change relies on the node rack information stored in Ambari > therefore will enable both Ambari UI and Blueprints to be used for setting up > Kafka broker rack information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21234) Ambari rack awareness for Kafka
[ https://issues.apache.org/jira/browse/AMBARI-21234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ambud Sharma updated AMBARI-21234: -- Attachment: (was: AMBARI-21234-2.5.diff) > Ambari rack awareness for Kafka > --- > > Key: AMBARI-21234 > URL: https://issues.apache.org/jira/browse/AMBARI-21234 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Ambud Sharma >Assignee: Sebastian Toader > Fix For: 2.5.2 > > > As an operations person it would be nice to manage Kafka rack awareness via > Ambari. Ambari allows node rack information to be configured and this > information can then be pulled in the Kafka stack and populated in the > server.properties file for Kafka. > Design: > This stack change uses the /clusterHostInfo/all_hosts and > /clusterHostInfo/all_racks paths and materializes them to a variable. Then it > uses linear search to find this node in the list of all hosts and it's > corresponding rack id. This information is then stored in a variable called > rack and which is materialized during the configure method of the broker > scripts. > This stack change relies on the node rack information stored in Ambari > therefore will enable both Ambari UI and Blueprints to be used for setting up > Kafka broker rack information. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086017#comment-16086017 ] Hudson commented on AMBARI-21462: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1679 (See [https://builds.apache.org/job/Ambari-branch-2.5/1679/]) AMBARI-21462. Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights - (adoroszlai: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a389f85b6e2a0cb23ff7fcf629fd55ab4e203560]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/TITAN/configuration/titan-hbase-solr.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/TITAN/configuration/titan-env.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/services/TITAN/configuration/titan-log4j.xml * (edit) ambari-server/src/main/resources/common-services/JNBG/0.2.0/configuration/jnbg-env.xml > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462_addendum.patch, AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21468) Knox restart fails during EU due to wrong location to the Knox data directory
[
https://issues.apache.org/jira/browse/AMBARI-21468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21468:
---
Resolution: Duplicate
Status: Resolved (was: Patch Available)
> Knox restart fails during EU due to wrong location to the Knox data directory
> -
>
> Key: AMBARI-21468
> URL: https://issues.apache.org/jira/browse/AMBARI-21468
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: branch-feature-AMBARI-21348
>Reporter: Di Li
>Assignee: Di Li
> Fix For: branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21468.patch
>
>
> Knox fails the restart during EU with error
> """
> resource_management.core.exceptions.ExecutionFailed: Execution of 'cp -R -p
> -f /usr/hdp/4.2.0.0/knox/data/. /usr/hdp/current/knox-server/data' returned
> 1. cp: cannot stat '/usr/hdp/4.2.0.0/knox/data/.': No such file or directory
> """
> This is because the common service Knox Py script assumes data dir is under
> stack_root which is /usr/hdp by the time it's Knox to restart during EU. But
> it also attaches the "current_version" obtained from command json file that
> points to 4.2.0.0 (or 4.2.5.0-) for the migration cluster. So the result
> root dir /usr/hdp/4.2. does not exist.
> """
> ambari-server\src\main\resources\common-services\KNOX\0.5.0.2.2\package\scripts\upgrade.py
> # /2.3.0.0-1234/knox/data/.
> source_data_dir = os.path.join(params.stack_root,
> params.upgrade_from_version, "knox", "data", ".")
> ambari-server\src\main\resources\common-services\KNOX\0.5.0.2.2\package\scripts\params_linux.py
> upgrade_from_version = default("/hostLevelParams/current_version", None)
> """
> """
> "hostLevelParams": {
> "agent_stack_retry_on_unavailability": "false",
> "stack_name": "HDP",
> "group_list": "[\"spark\",\"hadoop\",\"users\",\"knox\"]",
> "host_sys_prepped": "false",
> "ambari_db_rca_username": "mapred",
> "current_version": "4.2.0.0",
> """
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21466) Knox upgrade fails due to wrong stack root
[
https://issues.apache.org/jira/browse/AMBARI-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085963#comment-16085963
]
Hudson commented on AMBARI-21466:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1678 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1678/])
AMBARI-21466. KNOX upgrade fails due to wrong stack root (adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a7b6d5a0fc72c3d20c50210e887b7294007b0dba])
* (edit)
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py
* (edit)
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/ChangeStackReferencesAction.java
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/stack_tools.py
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/ChangeStackReferencesActionTest.java
> Knox upgrade fails due to wrong stack root
> --
>
> Key: AMBARI-21466
> URL: https://issues.apache.org/jira/browse/AMBARI-21466
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21466.patch
>
>
> {{common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py}} assumes old and
> new stacks have the same stack root directory. This causes failure of
> {{seed_current_data_directory}} in cross stack-name upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21468) Knox restart fails during EU due to wrong location to the Knox data directory
[
https://issues.apache.org/jira/browse/AMBARI-21468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Di Li updated AMBARI-21468:
---
Attachment: AMBARI-21468.patch
> Knox restart fails during EU due to wrong location to the Knox data directory
> -
>
> Key: AMBARI-21468
> URL: https://issues.apache.org/jira/browse/AMBARI-21468
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: branch-feature-AMBARI-21348
>Reporter: Di Li
>Assignee: Di Li
> Fix For: branch-feature-AMBARI-21348
>
> Attachments: AMBARI-21468.patch
>
>
> Knox fails the restart during EU with error
> """
> resource_management.core.exceptions.ExecutionFailed: Execution of 'cp -R -p
> -f /usr/hdp/4.2.0.0/knox/data/. /usr/hdp/current/knox-server/data' returned
> 1. cp: cannot stat '/usr/hdp/4.2.0.0/knox/data/.': No such file or directory
> """
> This is because the common service Knox Py script assumes data dir is under
> stack_root which is /usr/hdp by the time it's Knox to restart during EU. But
> it also attaches the "current_version" obtained from command json file that
> points to 4.2.0.0 (or 4.2.5.0-) for the migration cluster. So the result
> root dir /usr/hdp/4.2. does not exist.
> """
> ambari-server\src\main\resources\common-services\KNOX\0.5.0.2.2\package\scripts\upgrade.py
> # /2.3.0.0-1234/knox/data/.
> source_data_dir = os.path.join(params.stack_root,
> params.upgrade_from_version, "knox", "data", ".")
> ambari-server\src\main\resources\common-services\KNOX\0.5.0.2.2\package\scripts\params_linux.py
> upgrade_from_version = default("/hostLevelParams/current_version", None)
> """
> """
> "hostLevelParams": {
> "agent_stack_retry_on_unavailability": "false",
> "stack_name": "HDP",
> "group_list": "[\"spark\",\"hadoop\",\"users\",\"knox\"]",
> "host_sys_prepped": "false",
> "ambari_db_rca_username": "mapred",
> "current_version": "4.2.0.0",
> """
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21468) Knox restart fails during EU due to wrong location to the Knox data directory
Di Li created AMBARI-21468:
--
Summary: Knox restart fails during EU due to wrong location to the
Knox data directory
Key: AMBARI-21468
URL: https://issues.apache.org/jira/browse/AMBARI-21468
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: branch-feature-AMBARI-21348
Reporter: Di Li
Assignee: Di Li
Fix For: branch-feature-AMBARI-21348
Knox fails the restart during EU with error
"""
resource_management.core.exceptions.ExecutionFailed: Execution of 'cp -R -p -f
/usr/hdp/4.2.0.0/knox/data/. /usr/hdp/current/knox-server/data' returned 1. cp:
cannot stat '/usr/hdp/4.2.0.0/knox/data/.': No such file or directory
"""
This is because the common service Knox Py script assumes data dir is under
stack_root which is /usr/hdp by the time it's Knox to restart during EU. But
it also attaches the "current_version" obtained from command json file that
points to 4.2.0.0 (or 4.2.5.0-) for the migration cluster. So the result
root dir /usr/hdp/4.2. does not exist.
"""
ambari-server\src\main\resources\common-services\KNOX\0.5.0.2.2\package\scripts\upgrade.py
# /2.3.0.0-1234/knox/data/.
source_data_dir = os.path.join(params.stack_root,
params.upgrade_from_version, "knox", "data", ".")
ambari-server\src\main\resources\common-services\KNOX\0.5.0.2.2\package\scripts\params_linux.py
upgrade_from_version = default("/hostLevelParams/current_version", None)
"""
"""
"hostLevelParams": {
"agent_stack_retry_on_unavailability": "false",
"stack_name": "HDP",
"group_list": "[\"spark\",\"hadoop\",\"users\",\"knox\"]",
"host_sys_prepped": "false",
"ambari_db_rca_username": "mapred",
"current_version": "4.2.0.0",
"""
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085927#comment-16085927 ] Doroszlai, Attila commented on AMBARI-21462: Committed addendum to [branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/a389f85b6e]. > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462_addendum.patch, AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21466) Knox upgrade fails due to wrong stack root
[
https://issues.apache.org/jira/browse/AMBARI-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21466:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/a7b6d5a0fc].
> Knox upgrade fails due to wrong stack root
> --
>
> Key: AMBARI-21466
> URL: https://issues.apache.org/jira/browse/AMBARI-21466
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21466.patch
>
>
> {{common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py}} assumes old and
> new stacks have the same stack root directory. This causes failure of
> {{seed_current_data_directory}} in cross stack-name upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Status: Patch Available (was: In Progress)
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085915#comment-16085915 ] Jonathan Hurley commented on AMBARI-21462: -- +1 for addendum patch. > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462_addendum.patch, AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Attachment: AMBARI-19038_branch-2.5_01.patch
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Description:
After PAM has been declared as the authentication mechanism for Ambari clients
(for example, the Ambari Server web-based UI) where previously the mechanism
was LDAP, a migration process is needed to converts the LDAP users and groups
to PAM users and groups.
This facility may be invoked using:
{noformat}
ambari-server migrate-ldap-pam
{noformat}
was:
Story to address migration of LDAP users & groups to PAM.
Note: LDAP usesids that collide with existing PAM userids in Ambari metastore
will not be migrated.
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Fix Version/s: (was: trunk) 2.5.2 > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: 2.5.2 > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Status: Open (was: Patch Available) Cancelling the out-dated patch for this. > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: trunk > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Affects Version/s: (was: trunk) > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: 2.5.2 > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Affects Version/s: (was: 2.5.0) 2.5.2 > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: 2.5.2 > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas reassigned AMBARI-19038: - Assignee: Robert Levas (was: Vishal Ghugare) > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: trunk > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21425) Software Registry REST API
[ https://issues.apache.org/jira/browse/AMBARI-21425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-21425. Resolution: Fixed > Software Registry REST API > -- > > Key: AMBARI-21425 > URL: https://issues.apache.org/jira/browse/AMBARI-21425 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21467) Json Software Registry Implementation
Jayush Luniya created AMBARI-21467: -- Summary: Json Software Registry Implementation Key: AMBARI-21467 URL: https://issues.apache.org/jira/browse/AMBARI-21467 Project: Ambari Issue Type: Bug Reporter: Jayush Luniya -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21467) Json Software Registry Implementation
[ https://issues.apache.org/jira/browse/AMBARI-21467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-21467: -- Assignee: Jayush Luniya > Json Software Registry Implementation > - > > Key: AMBARI-21467 > URL: https://issues.apache.org/jira/browse/AMBARI-21467 > Project: Ambari > Issue Type: Bug >Reporter: Jayush Luniya >Assignee: Jayush Luniya > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21460) Add new kafka client properties to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21460: Attachment: AMBARI-21460_branch-2.5.patch AMBARI-21460_trunk.patch > Add new kafka client properties to the ambari managed atlas config > -- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460_branch-2.5.patch, AMBARI-21460.patch, > AMBARI-21460_trunk.patch > > > As part of this > [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62], > below new kafka client properties are introduced, need to add this to the > ambari managed atlas config. > atlas.kafka.enable.auto.commit=false > atlas.kafka.session.timeout.ms=3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21460) Add new kafka client properties to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21460: Status: Patch Available (was: Open) > Add new kafka client properties to the ambari managed atlas config > -- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460_branch-2.5.patch, AMBARI-21460.patch, > AMBARI-21460_trunk.patch > > > As part of this > [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62], > below new kafka client properties are introduced, need to add this to the > ambari managed atlas config. > atlas.kafka.enable.auto.commit=false > atlas.kafka.session.timeout.ms=3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21460) Add new kafka client properties to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21460: Summary: Add new kafka client properties to the ambari managed atlas config (was: Add kafka client properties to the ambari managed atlas config) > Add new kafka client properties to the ambari managed atlas config > -- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460.patch > > > As part of this > [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62], > below new kafka client properties are introduced, need to add this to the > ambari managed atlas config. > atlas.kafka.enable.auto.commit=false > atlas.kafka.session.timeout.ms=3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21460) Add kafka client properties to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21460: Summary: Add kafka client properties to the ambari managed atlas config (was: Add kafka client property "atlas.kafka.enable.auto.commit=false" to the ambari managed atlas config) > Add kafka client properties to the ambari managed atlas config > -- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460.patch > > > As part of this > [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62], > below new kafka client properties are introduced, need to add this to the > ambari managed atlas config. > atlas.kafka.enable.auto.commit=false > atlas.kafka.session.timeout.ms=3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21460) Add kafka client property "atlas.kafka.enable.auto.commit=false" to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated AMBARI-21460: Description: As part of this [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62], below new kafka client properties are introduced, need to add this to the ambari managed atlas config. atlas.kafka.enable.auto.commit=false atlas.kafka.session.timeout.ms=3 was:As part of this commit(https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62), new kafka client property"atlas.kafka.enable.auto.commit" is introduced, adding this to the ambari managed atlas config. > Add kafka client property "atlas.kafka.enable.auto.commit=false" to the > ambari managed atlas config > --- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460.patch > > > As part of this > [commit|https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62], > below new kafka client properties are introduced, need to add this to the > ambari managed atlas config. > atlas.kafka.enable.auto.commit=false > atlas.kafka.session.timeout.ms=3 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21420) HBase master crashed during/post EU on an IOP4.2.5/HDP2.6 migrated cluster
[ https://issues.apache.org/jira/browse/AMBARI-21420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085671#comment-16085671 ] Di Li commented on AMBARI-21420: It should be, as both IOP 4.2 GA and IOP 4.2.5 have HBase at version 1.2 and above, while HDP 2.6 has HBase 1.1.x. There is no downgrade from HBase 1.2 to 1.1 per HBase community. Thus the issue, and the last resort approach on moving the WAL dir away. > HBase master crashed during/post EU on an IOP4.2.5/HDP2.6 migrated cluster > -- > > Key: AMBARI-21420 > URL: https://issues.apache.org/jira/browse/AMBARI-21420 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: branch-feature-AMBARI-21348 >Reporter: Di Li >Assignee: Di Li > Fix For: branch-feature-AMBARI-21348 > > Attachments: AMBARI-21420.patch > > > HBase in IOP 4.2.5 is of higher version than the one shipped in HDP 2.6. > HBase master appeared as if it had started according to the Ambari action log > but later crashed with error: > 2017-07-05 09:28:08,952 FATAL [hats1:16000.activeMasterManager] > master.HMaster: Failed to become active masterjava.io.IOException: The > procedure class org.apache.hadoop.hbase.master.procedure.ServerCrashProcedure > must be accessible and have an empty constructorat > org.apache.hadoop.hbase.procedure2.Procedure.newInstance(Procedure.java:663)at > org.apache.hadoop.hbase.procedure2.Procedure.convert(Procedure.java:789)at > org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormatReader.read(ProcedureWALFormatReader.java:111)at > > org.apache.hadoop.hbase.procedure2.store.wal.ProcedureWALFormat.load(ProcedureWALFormat.java:81)at > > org.apache.hadoop.hbase.procedure2.store.wal.WALProcedureStore.load(WALProcedureStore.java:374)at > > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.load(ProcedureExecutor.java:297)at > > org.apache.hadoop.hbase.procedure2.ProcedureExecutor.start(ProcedureExecutor.java:464)at > > org.apache.hadoop.hbase.master.HMaster.startProcedureExecutor(HMaster.java:1297)at > org.apache.hadoop.hbase.master.HMaster.startServiceThreads(HMaster.java:1196) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[
https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16085597#comment-16085597
]
Doroszlai, Attila commented on AMBARI-21462:
The additional patch [^AMBARI-21462_addendum.patch] fixes
{{ServicePropertiesTest}} failure due to missing {{}} tags:
{noformat}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.02 sec - in
org.apache.ambari.server.state.ServicePropertiesTest
{noformat}
[~afernandez], [~swagle], can you please review?
> Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during
> EU and imports
> ---
>
> Key: AMBARI-21462
> URL: https://issues.apache.org/jira/browse/AMBARI-21462
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Labels: AMBARI-21348
> Fix For: 2.5.2
>
> Attachments: AMBARI-21462_addendum.patch, AMBARI-21462.patch
>
>
> Services to be deleted (in-order of delete after Ambari upgrade)
> TITAN
> R4ML
> SYSTEMML
> JNBG
> Fix imports in HBase and the "take_snapshot" function called during EU.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21462) Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during EU and imports
[ https://issues.apache.org/jira/browse/AMBARI-21462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-21462: --- Attachment: AMBARI-21462_addendum.patch > Readd TITAN, R4ML, SYSTEMML, JNBG to BigInsights and fix HBase backup during > EU and imports > --- > > Key: AMBARI-21462 > URL: https://issues.apache.org/jira/browse/AMBARI-21462 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.2 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez >Priority: Blocker > Labels: AMBARI-21348 > Fix For: 2.5.2 > > Attachments: AMBARI-21462_addendum.patch, AMBARI-21462.patch > > > Services to be deleted (in-order of delete after Ambari upgrade) > TITAN > R4ML > SYSTEMML > JNBG > Fix imports in HBase and the "take_snapshot" function called during EU. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21466) Knox upgrade fails due to wrong stack root
[
https://issues.apache.org/jira/browse/AMBARI-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21466:
---
Attachment: AMBARI-21466.patch
> Knox upgrade fails due to wrong stack root
> --
>
> Key: AMBARI-21466
> URL: https://issues.apache.org/jira/browse/AMBARI-21466
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21466.patch
>
>
> {{common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py}} assumes old and
> new stacks have the same stack root directory. This causes failure of
> {{seed_current_data_directory}} in cross stack-name upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21466) Knox upgrade fails due to wrong stack root
[
https://issues.apache.org/jira/browse/AMBARI-21466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21466:
---
Status: Patch Available (was: In Progress)
> Knox upgrade fails due to wrong stack root
> --
>
> Key: AMBARI-21466
> URL: https://issues.apache.org/jira/browse/AMBARI-21466
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21466.patch
>
>
> {{common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py}} assumes old and
> new stacks have the same stack root directory. This causes failure of
> {{seed_current_data_directory}} in cross stack-name upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21466) Knox upgrade fails due to wrong stack root
Doroszlai, Attila created AMBARI-21466:
--
Summary: Knox upgrade fails due to wrong stack root
Key: AMBARI-21466
URL: https://issues.apache.org/jira/browse/AMBARI-21466
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Doroszlai, Attila
Assignee: Doroszlai, Attila
Priority: Blocker
Fix For: 2.5.2
{{common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py}} assumes old and
new stacks have the same stack root directory. This causes failure of
{{seed_current_data_directory}} in cross stack-name upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21460) Add kafka client property "atlas.kafka.enable.auto.commit=false" to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Pathan reassigned AMBARI-21460: Assignee: Vishal Suvagia (was: Ayub Pathan) > Add kafka client property "atlas.kafka.enable.auto.commit=false" to the > ambari managed atlas config > --- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460.patch > > > As part of this > commit(https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62), > new kafka client property"atlas.kafka.enable.auto.commit" is introduced, > adding this to the ambari managed atlas config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21460) Add kafka client property "atlas.kafka.enable.auto.commit=false" to the ambari managed atlas config
[ https://issues.apache.org/jira/browse/AMBARI-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ayub Pathan updated AMBARI-21460: - Status: Open (was: Patch Available) > Add kafka client property "atlas.kafka.enable.auto.commit=false" to the > ambari managed atlas config > --- > > Key: AMBARI-21460 > URL: https://issues.apache.org/jira/browse/AMBARI-21460 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Ayub Pathan >Assignee: Vishal Suvagia > Fix For: trunk, 2.5.2 > > Attachments: AMBARI-21460.patch > > > As part of this > commit(https://github.com/apache/incubator-atlas/commit/0e7f8ea4603c858cc295259bbd1a22314b732f62), > new kafka client property"atlas.kafka.enable.auto.commit" is introduced, > adding this to the ambari managed atlas config. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21448) atlas_hbase_setup.rb scripts is executed only in secure or ranger enabled cluster. It is not executed on unsecure/simple cluster.
[
https://issues.apache.org/jira/browse/AMBARI-21448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Pathan updated AMBARI-21448:
-
Resolution: Not A Problem
Status: Resolved (was: Patch Available)
> atlas_hbase_setup.rb scripts is executed only in secure or ranger enabled
> cluster. It is not executed on unsecure/simple cluster.
> -
>
> Key: AMBARI-21448
> URL: https://issues.apache.org/jira/browse/AMBARI-21448
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk
>Reporter: Ayub Pathan
>Assignee: Ayub Pathan
> Fix For: trunk
>
> Attachments: AMBARI-21448.patch
>
>
> atlas_hbase_setup.rb scripts is executed only in secure or ranger enabled
> cluster. It is not executed on unsecure/simple cluster, Is this intentional?
> we need to create the hbase table required for atlas in unsecure cluster as
> well.
> Reference:
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/ATLAS/0.7.0.3.0/package/scripts/metadata_server.py#L93
> {code}
> if check_stack_feature(StackFeature.ATLAS_HBASE_SETUP,
> effective_version):
> if params.security_enabled and params.has_hbase_master:
> Execute(secure_atlas_hbase_setup_command,
> tries = 5,
> try_sleep = 10,
> user=params.hbase_user
> )
> elif params.enable_ranger_hbase and not params.security_enabled:
> Execute(atlas_hbase_setup_command,
> tries = 5,
> try_sleep = 10,
> user=params.hbase_user
> )
> {code}
> The above condition should be
> {noformat}
> if check_stack_feature(StackFeature.ATLAS_HBASE_SETUP,
> effective_version):
> if params.security_enabled and params.has_hbase_master:
> Execute(secure_atlas_hbase_setup_command,
> tries = 5,
> try_sleep = 10,
> user=params.hbase_user
> )
> elif params.enable_ranger_hbase or not params.security_enabled:
> Execute(atlas_hbase_setup_command,
> tries = 5,
> try_sleep = 10,
> user=params.hbase_user
> )
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21465) Setting for comments to be required when saving configuration
[ https://issues.apache.org/jira/browse/AMBARI-21465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bjorn Olsen updated AMBARI-21465: - Description: When configuration changes are saved to an Ambari-managed service, the Save Configuration dialog appears and asks "What did you change?". Currently a user does not need to populate any comment here, and the configuration can still be saved. It would be preferable to have a setting in Ambari to require a minimum length for this field. This would encourage Ambari users to populate meaningful comments when changing service configurations, which makes the configuration version history easier to understand. This is especially useful in multi-user or production environments. The setting could be set to 0 length to support current functionality of not requiring a comment to be populated when configurations are changed. was: When configuration changes are saved to an Ambari-managed service, the Save Configuration dialog appears and asks "What did you change?". Currently a user does not need to populate any comment here, and the configuration can still be saved. It would be preferable to have a setting in Ambari to require a minimum length for this field. This would encourage Ambari users to populate meaningful comments when changing service configurations, which makes the configuration version history easier to understand. This is especially useful in multi-user or production environments. > Setting for comments to be required when saving configuration > - > > Key: AMBARI-21465 > URL: https://issues.apache.org/jira/browse/AMBARI-21465 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Bjorn Olsen >Priority: Minor > > When configuration changes are saved to an Ambari-managed service, the Save > Configuration dialog appears and asks "What did you change?". Currently a > user does not need to populate any comment here, and the configuration can > still be saved. > It would be preferable to have a setting in Ambari to require a minimum > length for this field. This would encourage Ambari users to populate > meaningful comments when changing service configurations, which makes the > configuration version history easier to understand. This is especially useful > in multi-user or production environments. > The setting could be set to 0 length to support current functionality of not > requiring a comment to be populated when configurations are changed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21465) Setting for comments to be required when saving configuration
Bjorn Olsen created AMBARI-21465: Summary: Setting for comments to be required when saving configuration Key: AMBARI-21465 URL: https://issues.apache.org/jira/browse/AMBARI-21465 Project: Ambari Issue Type: Improvement Components: ambari-server Reporter: Bjorn Olsen Priority: Minor When configuration changes are saved to an Ambari-managed service, the Save Configuration dialog appears and asks "What did you change?". Currently a user does not need to populate any comment here, and the configuration can still be saved. It would be preferable to have a setting in Ambari to require a minimum length for this field. This would encourage Ambari users to populate meaningful comments when changing service configurations, which makes the configuration version history easier to understand. This is especially useful in multi-user or production environments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
