[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21045: Attachment: AMBARI-21045-2.5-maint.patch > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045-2.5-maint.patch, > AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21136) Upgrading Ambari to 2.5.1 stops Storm's nimbus in secure mode.
[ https://issues.apache.org/jira/browse/AMBARI-21136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21136: Attachment: AMBARI-21136.patch > Upgrading Ambari to 2.5.1 stops Storm's nimbus in secure mode. > -- > > Key: AMBARI-21136 > URL: https://issues.apache.org/jira/browse/AMBARI-21136 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21136.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21136) Upgrading Ambari to 2.5.1 stops Storm's nimbus in secure mode.
Sriharsha Chintalapani created AMBARI-21136: --- Summary: Upgrading Ambari to 2.5.1 stops Storm's nimbus in secure mode. Key: AMBARI-21136 URL: https://issues.apache.org/jira/browse/AMBARI-21136 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical Fix For: 2.5.2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21129) Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and cluster is then Kerberized
[
https://issues.apache.org/jira/browse/AMBARI-21129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025174#comment-16025174
]
Sriharsha Chintalapani commented on AMBARI-21129:
-
+1. LGTM.
> Nimbus fails to start when Ambari is upgraded to 2.5.1, EU to HDP 2.6.1, and
> cluster is then Kerberized
> ---
>
> Key: AMBARI-21129
> URL: https://issues.apache.org/jira/browse/AMBARI-21129
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Denis Tarasyuk
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21129.2.5-maint.patch
>
>
> STR:
> # Ambari 2.5.0 with Storm and HDP 2.6 and Storm
> # Upgrade Ambari to 2.5.1
> # EU to HDP 2.6.1
> # Kerberize the cluster
> The exception found in nimbus.log:
> {code}
> 2017-05-25 11:31:10.235 o.a.s.n.NimbusInfo [INFO] Nimbus figures out its name
> to natu146-fpas-dlm30tofnsec-u14-re-re-4.openstacklocal
> 2017-05-25 11:31:10.247 o.a.s.d.nimbus [ERROR] Error on initialization of
> server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException:
> org.apache.storm.hdfs.security.AutoHDFS
> at
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at
> org.apache.storm.daemon.nimbus$fn__9066$exec_fn__2832__auto9067.invoke(nimbus.clj:2416)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
> at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
> at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at clojure.lang.AFn.applyToHelper(AFn.java:152) ~[clojure-1.7.0.jar:?]
> at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
> at org.apache.storm.daemon.nimbus.main(Unknown Source)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> Caused by: java.lang.ClassNotFoundException:
> org.apache.storm.hdfs.security.AutoHDFS
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366) ~[?:1.7.0_67]
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355) ~[?:1.7.0_67]
> at java.security.AccessController.doPrivileged(Native Method)
> ~[?:1.7.0_67]
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> ~[?:1.7.0_67]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425) ~[?:1.7.0_67]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> ~[?:1.7.0_67]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ~[?:1.7.0_67]
> at java.lang.Class.forName0(Native Method) ~[?:1.7.0_67]
> at java.lang.Class.forName(Class.java:190) ~[?:1.7.0_67]
> at
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:181)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> ... 13 more
> 2017-05-25 11:31:10.295 o.a.s.util [ERROR] Halting process: ("Error on
> initialization")
> java.lang.RuntimeException: ("Error on initialization")
> at org.apache.storm.util$exit_process_BANG_.doInvoke(util.clj:341)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at clojure.lang.RestFn.invoke(RestFn.java:423) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.nimbus$fn__9066$service_handler__9099.doInvoke(nimbus.clj:2413)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at clojure.lang.RestFn.invoke(RestFn.java:421) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.nimbus$launch_server_BANG_.invoke(nimbus.clj:2501)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at org.apache.storm.daemon.nimbus$_launch.invoke(nimbus.clj:2534)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at org.apache.storm.daemon.nimbus$_main.invoke(nimbus.clj:2557)
> ~[storm-core-1.1.0.2.6.1.0-109.jar:1.1.0.2.6.1.0-109]
> at
[jira] [Updated] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21121: Status: Patch Available (was: Open) > Missing storm-site.xml in HDP-2.6 stack > --- > > Key: AMBARI-21121 > URL: https://issues.apache.org/jira/browse/AMBARI-21121 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21121.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21121: Attachment: AMBARI-21121.patch > Missing storm-site.xml in HDP-2.6 stack > --- > > Key: AMBARI-21121 > URL: https://issues.apache.org/jira/browse/AMBARI-21121 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21121.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
Sriharsha Chintalapani created AMBARI-21121: --- Summary: Missing storm-site.xml in HDP-2.6 stack Key: AMBARI-21121 URL: https://issues.apache.org/jira/browse/AMBARI-21121 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Blocker Fix For: 2.5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21118) HDP + HDF cluster cannot save configs for Storm when Streamline is installed due to missing configs
[
https://issues.apache.org/jira/browse/AMBARI-21118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023934#comment-16023934
]
Sriharsha Chintalapani commented on AMBARI-21118:
-
+1
> HDP + HDF cluster cannot save configs for Storm when Streamline is installed
> due to missing configs
> ---
>
> Key: AMBARI-21118
> URL: https://issues.apache.org/jira/browse/AMBARI-21118
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21118.2.5-maint.patch
>
>
> STR:
> * Install Ambari 2.5.1 with HDP 2.6.1 plus Storm and Streamline (from HDF
> MPack)
> * Attempt to change configs for Storm
> Ambari: 2.5.1.0-146
> HDF: 3.0.0.0-358
> HDP: 2.6.1.0-110
> This is happening because Storm does not have Streamline as a dependent
> service, so the UI does not pass the Streamline configs to the
> recommendations endpoint when calling Stack Advisor for Storm.
> {code}
> '), ('yarn.scheduler.capacity.root.accessible-node-labels', '*'),
> ('yarn.scheduler.capacity.root.capacity', '100'),
> ('yarn.scheduler.capacity.maximum-am-resource-percent', '0.2'),
> ('yarn.scheduler.capacity.maximum-applications', '1'),
> ('yarn.scheduler.capacity.root.de
> fault.user-limit-factor', '1'),
> ('yarn.scheduler.capacity.node-locality-delay', '40'),
> ('yarn.scheduler.capacity.root.default.acl_submit_applications', 'yarn'),
> ('yarn.scheduler.capacity.root.default.state', 'RUNNING'),
> ('yarn.scheduler.capacity.root.default.capacity', '1
> 00'), ('yarn.scheduler.capacity.root.acl_administer_queue', 'yarn'),
> ('yarn.scheduler.capacity.root.default.maximum-capacity', '100'),
> ('yarn.scheduler.capacity.root.queues', 'default'),
> ('yarn.scheduler.capacity.root.acl_administer_jobs', 'yarn'), ('', ''),
> ('yarn.schedu
> ler.capacity.root.default.acl_administer_jobs', 'yarn'),
> ('yarn.scheduler.capacity.resource-calculator',
> 'org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator')]
> Error occured in stack advisor.
> Error details: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686 INFO [ambari-client-thread-31]
> StackAdvisorRunner:71 - advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116,
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 775, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
> line 68, in recommendSTORMConfigurations
> _streamline_principal_name = streamline_env['streamline_principal_name']
> if 'streamline_principal_name' in streamline_env else None
> TypeError: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686 WARN [ambari-client-thread-31]
> AbstractResourceProvider:97 - Error occured during recommendation
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: argument of type 'NoneType' is
> not iterable
> StdOut file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.err
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:295)
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
>
[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21045: Attachment: AMBARI-21045.branch-2.5.patch > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21045: Attachment: AMBARI-21045-v2.patch > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-21045.patch, AMBARI-21045-v2.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21074) Storm XML File has Invalid Characters Causing Exceptions on Server Startup
[
https://issues.apache.org/jira/browse/AMBARI-21074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017471#comment-16017471
]
Sriharsha Chintalapani commented on AMBARI-21074:
-
+1
cc [~jonathan.hurley]
> Storm XML File has Invalid Characters Causing Exceptions on Server Startup
> --
>
> Key: AMBARI-21074
> URL: https://issues.apache.org/jira/browse/AMBARI-21074
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.1
>
> Attachments: AMBARI-21074.patch
>
>
> Ambari server is failing to start on D7 due to multiple exceptions during
> ambari-server schema upgrade.
> The first exception thrown is
> {code:None}
> 19 May 2017 10:01:42,268 INFO [main] ServiceDirectory:419 - Role command
> order info was loaded from file:
> /var/lib/ambari-server/resources/common-services/DRUID/0.9.2/role_command_order.json
> 19 May 2017 10:01:42,434 ERROR [main] ModuleFileUnmarshaller:141 - Cannot
> parse
> /var/lib/ambari-server/resources/common-services/STORM/0.9.1/configuration/storm-env.xml
> 19 May 2017 10:01:42,435 ERROR [main] ModuleFileUnmarshaller:143 - The entity
> name must immediately follow the '&' in the entity reference.
> org.xml.sax.SAXParseException; systemId:
> file:/var/lib/ambari-server/resources/common-services/STORM/0.9.1/configuration/storm-env.xml;
> lineNumber: 131; columnNumber: 64; The entity name must immediately follow
> the '&' in the entity reference.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
> at
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> at
> com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(XMLDocumentFragmentScannerImpl.java:1846)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3061)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
> at
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:841)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:770)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)
> at
> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:216)
> at
> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:189)
> at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:157)
> at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:162)
> at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:171)
> at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:189)
> at
> org.apache.ambari.server.stack.ModuleFileUnmarshaller.unmarshal(ModuleFileUnmarshaller.java:136)
> at
> org.apache.ambari.server.stack.ModuleFileUnmarshaller.unmarshal(ModuleFileUnmarshaller.java:81)
> at
> org.apache.ambari.server.stack.ConfigurationDirectory.parsePath(ConfigurationDirectory.java:103)
> at
> org.apache.ambari.server.stack.ConfigurationDirectory.(ConfigurationDirectory.java:79)
> at
> org.apache.ambari.server.stack.StackDefinitionDirectory.getConfigurationDirectory(StackDefinitionDirectory.java:72)
> at
> org.apache.ambari.server.stack.ServiceModule.populateConfigurationModules(ServiceModule.java:393)
> at
>
[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21045: Attachment: AMBARI-21045.patch > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-21045.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21045: Status: Patch Available (was: Open) > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
Sriharsha Chintalapani created AMBARI-21045: --- Summary: Enable Storm's AutoTGT configs in secure mode Key: AMBARI-21045 URL: https://issues.apache.org/jira/browse/AMBARI-21045 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical Fix For: 2.5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21015) Add RegistryClient Jaas section to storm_jaas.conf
[ https://issues.apache.org/jira/browse/AMBARI-21015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21015: Attachment: AMBARI-21015.patch > Add RegistryClient Jaas section to storm_jaas.conf > -- > > Key: AMBARI-21015 > URL: https://issues.apache.org/jira/browse/AMBARI-21015 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-21015.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21015) Add RegistryClient Jaas section to storm_jaas.conf
Sriharsha Chintalapani created AMBARI-21015: --- Summary: Add RegistryClient Jaas section to storm_jaas.conf Key: AMBARI-21015 URL: https://issues.apache.org/jira/browse/AMBARI-21015 Project: Ambari Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical Fix For: 2.5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20791) Storm Ambari view doesn't work for non-admin users
[ https://issues.apache.org/jira/browse/AMBARI-20791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15995300#comment-15995300 ] Sriharsha Chintalapani commented on AMBARI-20791: - Merged into trunk and brach-2.5 > Storm Ambari view doesn't work for non-admin users > -- > > Key: AMBARI-20791 > URL: https://issues.apache.org/jira/browse/AMBARI-20791 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah >Priority: Critical > Fix For: 2.5.0 > > Attachments: > 0001-AMBARI-20791-Storm-Ambari-view-doesn-t-work-for-non-.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20791) Storm Ambari view doesn't work for non-admin users
[ https://issues.apache.org/jira/browse/AMBARI-20791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-20791: Resolution: Fixed Status: Resolved (was: Patch Available) > Storm Ambari view doesn't work for non-admin users > -- > > Key: AMBARI-20791 > URL: https://issues.apache.org/jira/browse/AMBARI-20791 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah >Priority: Critical > Fix For: 2.5.0 > > Attachments: > 0001-AMBARI-20791-Storm-Ambari-view-doesn-t-work-for-non-.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20791) Storm Ambari view doesn't work for non-admin users
Sriharsha Chintalapani created AMBARI-20791: --- Summary: Storm Ambari view doesn't work for non-admin users Key: AMBARI-20791 URL: https://issues.apache.org/jira/browse/AMBARI-20791 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Sriharsha Chintalapani Assignee: Sanket Shah Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20786) Installation fails when trying to install Hive with Mysql as metastore db
Sriharsha Chintalapani created AMBARI-20786: --- Summary: Installation fails when trying to install Hive with Mysql as metastore db Key: AMBARI-20786 URL: https://issues.apache.org/jira/browse/AMBARI-20786 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Madhuvanthi Radhakrishnan Priority: Critical When I tried select Hive and configured meta store to use mysql running into below exception = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call raise ExecutionFailed(err_msg, code, out, err) resource_management.core.exceptions.ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 -y install 'hive_package None is not installed'' returned 1. Error: Nothing to do -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20667) Storm metrics sink can't connect Ambari metrics collector
[
https://issues.apache.org/jira/browse/AMBARI-20667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954528#comment-15954528
]
Sriharsha Chintalapani commented on AMBARI-20667:
-
Thanks [~kabhwan] for the quick fix. +1.
> Storm metrics sink can't connect Ambari metrics collector
> -
>
> Key: AMBARI-20667
> URL: https://issues.apache.org/jira/browse/AMBARI-20667
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0, 2.5.1
>Reporter: Jungtaek Lim
>Assignee: Jungtaek Lim
>Priority: Critical
> Attachments: AMBARI-20667-branch-2.5.patch
>
>
> From Storm's worker log:
> {code}
> 2017-04-03 07:00:07.643
> o.a.h.m.s.t.a.MetricSinkWriteShardHostnameHashingStrategy [INFO] Calculated
> collector shard vett-hdf-sam2.field.hortonworks.com based on hostname:
> vett-hdf-sam8.field.hortonworks.com
> 2017-04-03 07:00:07.774 o.a.h.m.s.s.StormTimelineMetricsSink [INFO] Unable to
> connect to collector, null
> This exceptions will be ignored for next 100 times
> 2017-04-03 07:00:07.775 o.a.h.m.s.s.StormTimelineMetricsSink [WARN] Unable to
> send metrics to collector by address:null
> {code}
> I guess AMBARI-16828 is applied well for trunk, but there seems a mistake for
> backporting the patch to branch-2.5. Please compare two links below:
> For trunk:
> https://github.com/apache/ambari/blob/trunk/ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java#L74
> For branch-2.5:
> https://github.com/apache/ambari/blob/branch-2.5/ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsSink.java#L74
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-20451) Storm Ambari view fails with SSL enabled Storm UI
[ https://issues.apache.org/jira/browse/AMBARI-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-20451: --- Assignee: Sriharsha Chintalapani (was: Sanket Shah) > Storm Ambari view fails with SSL enabled Storm UI > - > > Key: AMBARI-20451 > URL: https://issues.apache.org/jira/browse/AMBARI-20451 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.0 > > Attachments: 0001-adding-SSL-Enabled-property-for-storm-view.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20451) Storm Ambari view fails with SSL enabled Storm UI
[ https://issues.apache.org/jira/browse/AMBARI-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-20451: --- Assignee: Sanket Shah (was: Sriharsha Chintalapani) > Storm Ambari view fails with SSL enabled Storm UI > - > > Key: AMBARI-20451 > URL: https://issues.apache.org/jira/browse/AMBARI-20451 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah >Priority: Blocker > Fix For: 2.5.0 > > Attachments: 0001-adding-SSL-Enabled-property-for-storm-view.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20451) Storm Ambari view fails with SSL enabled Storm UI
[ https://issues.apache.org/jira/browse/AMBARI-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-20451: Attachment: 0001-adding-SSL-Enabled-property-for-storm-view.patch > Storm Ambari view fails with SSL enabled Storm UI > - > > Key: AMBARI-20451 > URL: https://issues.apache.org/jira/browse/AMBARI-20451 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah >Priority: Blocker > Fix For: 2.5.0 > > Attachments: 0001-adding-SSL-Enabled-property-for-storm-view.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20451) Storm Ambari view fails with SSL enabled Storm UI
[ https://issues.apache.org/jira/browse/AMBARI-20451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-20451: Status: Patch Available (was: Open) > Storm Ambari view fails with SSL enabled Storm UI > - > > Key: AMBARI-20451 > URL: https://issues.apache.org/jira/browse/AMBARI-20451 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah >Priority: Blocker > Fix For: 2.5.0 > > Attachments: 0001-adding-SSL-Enabled-property-for-storm-view.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20451) Storm Ambari view fails with SSL enabled Storm UI
Sriharsha Chintalapani created AMBARI-20451: --- Summary: Storm Ambari view fails with SSL enabled Storm UI Key: AMBARI-20451 URL: https://issues.apache.org/jira/browse/AMBARI-20451 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sanket Shah Priority: Blocker Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20238) Add Streamline Stack definition
Sriharsha Chintalapani created AMBARI-20238: --- Summary: Add Streamline Stack definition Key: AMBARI-20238 URL: https://issues.apache.org/jira/browse/AMBARI-20238 Project: Ambari Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20239) Add Registry stack definition
Sriharsha Chintalapani created AMBARI-20239: --- Summary: Add Registry stack definition Key: AMBARI-20239 URL: https://issues.apache.org/jira/browse/AMBARI-20239 Project: Ambari Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-17817) Storm Ambari View should use proxy for secure clusters
[ https://issues.apache.org/jira/browse/AMBARI-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-17817: --- Assignee: Sanket Shah (was: Sriharsha Chintalapani) > Storm Ambari View should use proxy for secure clusters > -- > > Key: AMBARI-17817 > URL: https://issues.apache.org/jira/browse/AMBARI-17817 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah > Attachments: AMBARI-17817.patch > > > We observed that in secure cluster where ambari has SSL configured. Storm > Ambari view fails to make http calls to Storm REST API as it won't be allowed > to make calls from https origin to http destination. > When we used ambari proxy this issue resolved. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani reassigned AMBARI-18431: --- Assignee: Sanket Shah (was: Sriharsha Chintalapani) > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sanket Shah > Fix For: 2.5.0 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker log directory
[
https://issues.apache.org/jira/browse/AMBARI-19860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani reassigned AMBARI-19860:
---
Assignee: Arun Mahadevan
> Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker
> log directory
> --
>
> Key: AMBARI-19860
> URL: https://issues.apache.org/jira/browse/AMBARI-19860
> Project: Ambari
> Issue Type: Bug
>Reporter: Arun Mahadevan
>Assignee: Arun Mahadevan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19860.patch
>
>
> During upgrade the storm worker.xml and cluster.xml files should have updated
> path.
> {noformat}
>
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker log directory
[
https://issues.apache.org/jira/browse/AMBARI-19860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated AMBARI-19860:
Resolution: Fixed
Fix Version/s: 2.5.0
Status: Resolved (was: Patch Available)
> Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker
> log directory
> --
>
> Key: AMBARI-19860
> URL: https://issues.apache.org/jira/browse/AMBARI-19860
> Project: Ambari
> Issue Type: Bug
>Reporter: Arun Mahadevan
>Assignee: Arun Mahadevan
> Fix For: 2.5.0
>
> Attachments: AMBARI-19860.patch
>
>
> During upgrade the storm worker.xml and cluster.xml files should have updated
> path.
> {noformat}
>
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-18431: Resolution: Fixed Status: Resolved (was: Patch Available) > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.5.0 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15668442#comment-15668442 ] Sriharsha Chintalapani commented on AMBARI-18431: - [~jluniya] any reason for changing the fix version. The patch is tested and reviewed. Can you merge it in? > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: trunk > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-18431: Fix Version/s: 2.4.2 > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.4.2 > > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated AMBARI-18380:
Fix Version/s: 2.4.2
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
> Fix For: 2.4.2
>
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated AMBARI-18380:
Assignee: Alejandro Fernandez (was: Sriharsha Chintalapani)
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15569547#comment-15569547
]
Sriharsha Chintalapani commented on AMBARI-18380:
-
[~afernandez] appreciate if you take this up
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Alejandro Fernandez
>Priority: Blocker
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-18431: Status: Patch Available (was: Open) > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18431) Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes.
[ https://issues.apache.org/jira/browse/AMBARI-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-18431: Attachment: 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > Storm Ambari view - Fixes to DAG, kafka offset info , Misc fixes. > - > > Key: AMBARI-18431 > URL: https://issues.apache.org/jira/browse/AMBARI-18431 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: > 0001-Changed-topology-DAG-Fixed-Kafka-Spout-Lag-data-form.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
[
https://issues.apache.org/jira/browse/AMBARI-18380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487862#comment-15487862
]
Sriharsha Chintalapani commented on AMBARI-18380:
-
cc [~mahadev] [~sumitmohanty]
> For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward
> compatibility
>
>
> Key: AMBARI-18380
> URL: https://issues.apache.org/jira/browse/AMBARI-18380
> Project: Ambari
> Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
>Priority: Blocker
>
> following properties need to be set
> {code}
> inter.broker.protocol.version=0.9.0.0
> log.message.format.version=0.9.0.0
> {code}
> after upgrade is done we should delte the inter.broker.protocol.version.
> Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18380) For rolling upgrade of Kafka 0.10.0.1 we need to configs for backward compatibility
Sriharsha Chintalapani created AMBARI-18380:
---
Summary: For rolling upgrade of Kafka 0.10.0.1 we need to configs
for backward compatibility
Key: AMBARI-18380
URL: https://issues.apache.org/jira/browse/AMBARI-18380
Project: Ambari
Issue Type: Bug
Reporter: Sriharsha Chintalapani
Assignee: Sriharsha Chintalapani
Priority: Blocker
following properties need to be set
{code}
inter.broker.protocol.version=0.9.0.0
log.message.format.version=0.9.0.0
{code}
after upgrade is done we should delte the inter.broker.protocol.version.
Users should remove log.message.format.version once they update their clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17324) kafka should set zookeeper.set.acl to true when kerberos enabled
[ https://issues.apache.org/jira/browse/AMBARI-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17324: Fix Version/s: (was: 2.4.1) 2.4.0 > kafka should set zookeeper.set.acl to true when kerberos enabled > > > Key: AMBARI-17324 > URL: https://issues.apache.org/jira/browse/AMBARI-17324 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17324.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17952) Add nimbus.impersontation.acl on upgrade
[ https://issues.apache.org/jira/browse/AMBARI-17952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17952: Attachment: AMBARI-17952.patch > Add nimbus.impersontation.acl on upgrade > > > Key: AMBARI-17952 > URL: https://issues.apache.org/jira/browse/AMBARI-17952 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17952.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17952) Add nimbus.impersontation.acl on upgrade
[ https://issues.apache.org/jira/browse/AMBARI-17952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17952: Status: Patch Available (was: Open) > Add nimbus.impersontation.acl on upgrade > > > Key: AMBARI-17952 > URL: https://issues.apache.org/jira/browse/AMBARI-17952 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17952.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17952) Add nimbus.impersontation.acl on upgrade
Sriharsha Chintalapani created AMBARI-17952: --- Summary: Add nimbus.impersontation.acl on upgrade Key: AMBARI-17952 URL: https://issues.apache.org/jira/browse/AMBARI-17952 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Blocker Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17694) Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos is enabled
[ https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398053#comment-15398053 ] Sriharsha Chintalapani commented on AMBARI-17694: - [~anitajebaraj] [~rlevas] This fix is breaking general deployments of kafka itself. It looks like this patch only addressed moving the listeners change to stack_advisor. We had to add a follow-up patch fix the inter.security.broker.protocol config change and now we are seeing the security.protocol is not being set in the broker side in listeners propery when kerberos is deployed. Ideally we need to make all the security related to changes thats defined in kafka kerberos.json to stack_advisor so that the config changes are reflected back in Ambari Kafka config page. We need re-open and address the issue better. For now lets revert this patch as it causing deployment failures. > Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos > is enabled > --- > > Key: AMBARI-17694 > URL: https://issues.apache.org/jira/browse/AMBARI-17694 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: 2.4.0 > > Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch, > AMBARI-17694.patch > > > When kerberos is enabled, the protocol for listeners in > /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL, > even though the Ambari UI shows otherwise -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394348#comment-15394348 ] Sriharsha Chintalapani commented on AMBARI-16027: - [~sumitmohanty] [~afernandez] added addendum patch to remove the tasks from upgrades as we don't need them anymore. > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Attachment: AMBARI-16027.addendum.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.addendum.patch, > AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17839) Ambari URLStreamProvider doesn't store the cookies
[ https://issues.apache.org/jira/browse/AMBARI-17839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved AMBARI-17839. - Resolution: Works for Me > Ambari URLStreamProvider doesn't store the cookies > --- > > Key: AMBARI-17839 > URL: https://issues.apache.org/jira/browse/AMBARI-17839 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Rohit Choudhary >Priority: Blocker > Fix For: 2.4.0 > > > Views generally makes calls via Ambari Proxy Server using URLStreamProvider. > This is necessary as making direct calls to the Service REST-APIs is not > desirable especially incase if ambari server is running with HTTPS and where > as service rest apis are running with HTTP, these calls won't work. > URLStreamProvider currently doesn't store any cookies from the responses. > This is required, In case of Storm where we use SPNEGO auth it returns a > "hadoop-auth" cookie but it doesn't get stored and we get auth exceptions. > This works fine if we open the storm-ui directly in the browser which drops > hadoop-auth cookie and ambari-server is able to read this cookie and send it > to the storm-ui server . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
[ https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390782#comment-15390782 ] Sriharsha Chintalapani commented on AMBARI-17861: - [~sumitmohanty] [~afernandez] Added addendum patch can you please review. > Ambari principal should be part of nimbus.admins for Storm View > --- > > Key: AMBARI-17861 > URL: https://issues.apache.org/jira/browse/AMBARI-17861 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17861-II.patch, AMBARI-17861.addendum.patch, > AMBARI-17861.patch, AMBARI-17861.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
[ https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17861: Attachment: AMBARI-17861.addendum.patch > Ambari principal should be part of nimbus.admins for Storm View > --- > > Key: AMBARI-17861 > URL: https://issues.apache.org/jira/browse/AMBARI-17861 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17861-II.patch, AMBARI-17861.addendum.patch, > AMBARI-17861.patch, AMBARI-17861.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
[
https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390778#comment-15390778
]
Sriharsha Chintalapani commented on AMBARI-17861:
-
[~sumitmohanty] [~afernandez] when the user upgrade from HDP 2.4 to 2.5 we
don't get ambari_server_principal in cluster configs here is the output of
println(config['configurations']['cluster-env'])
{code}
{'security_enabled': 'true', 'stack_root': '/usr/hdp', 'ignore_bad_mounts':
'false', 'override_uid': 'true', 'recovery_window_in_minutes': '60',
'fetch_nonlocal_groups': 'true', 'managed_hdfs_resource_property_names': '',
'one_dir_per_partition': 'false', 'user_group': 'hadoop', 'stack_tools': '{\n
"stack_selector": ["hdp-select", "/usr/bin/hdp-select", "hdp-select"],\n
"conf_selector": ["conf-select", "/usr/bin/conf-select", "conf-select"]\n}',
'recovery_retry_interval': '5', 'repo_ubuntu_template': '{{package_type}}
{{base_url}} {{components}}', 'stack_features': '{\n "stack_features": [\n
{\n "name": "snappy",\n "description": "Snappy
compressor/decompressor support",\n "min_version": "2.0.0.0",\n
"max_version": "2.2.0.0"\n},\n{\n "name": "lzo",\n
"description": "LZO libraries support",\n "min_version": "2.2.1.0"\n
},\n{\n "name": "express_upgrade",\n "description": "Express
upgrade support",\n "min_version": "2.1.0.0"\n},\n{\n "name":
"rolling_upgrade",\n "description": "Rolling upgrade support",\n
"min_version": "2.2.0.0"\n},\n{\n "name": "config_versioning",\n
"description": "Configurable versions support",\n "min_version":
"2.3.0.0"\n},\n{\n "name": "datanode_non_root",\n
"description": "DataNode running as non-root support (AMBARI-7615)",\n
"min_version": "2.2.0.0"\n},\n{\n "name":
"remove_ranger_hdfs_plugin_env",\n "description": "HDFS removes Ranger env
files (AMBARI-14299)",\n "min_version": "2.3.0.0"\n},\n{\n
"name": "ranger",\n "description": "Ranger Service support",\n
"min_version": "2.2.0.0"\n},\n{\n "name":
"ranger_tagsync_component",\n "description": "Ranger Tagsync component
support (AMBARI-14383)",\n "min_version": "2.5.0.0"\n},\n{\n
"name": "phoenix",\n "description": "Phoenix Service support",\n
"min_version": "2.3.0.0"\n},\n{\n "name": "nfs",\n
"description": "NFS support",\n "min_version": "2.3.0.0"\n},\n{\n
"name": "tez_for_spark",\n "description": "Tez dependency for
Spark",\n "min_version": "2.2.0.0",\n "max_version": "2.3.0.0"\n
},\n{\n "name": "timeline_state_store",\n "description": "Yarn
application timeline-service supports state store property (AMBARI-11442)",\n
"min_version": "2.2.0.0"\n},\n{\n "name":
"copy_tarball_to_hdfs",\n "description": "Copy tarball to HDFS support
(AMBARI-12113)",\n "min_version": "2.2.0.0"\n},\n{\n "name":
"spark_16plus",\n "description": "Spark 1.6+",\n "min_version":
"2.4.0.0"\n},\n{\n "name": "spark_thriftserver",\n
"description": "Spark Thrift Server",\n "min_version": "2.3.2.0"\n},\n
{\n "name": "storm_kerberos",\n "description": "Storm Kerberos
support (AMBARI-7570)",\n "min_version": "2.2.0.0"\n},\n{\n
"name": "storm_ams",\n "description": "Storm AMS integration
(AMBARI-10710)",\n "min_version": "2.2.0.0"\n},\n{\n "name":
"create_kafka_broker_id",\n "description": "Ambari should create Kafka
Broker Id (AMBARI-12678)",\n "min_version": "2.2.0.0",\n
"max_version": "2.3.0.0"\n},\n{\n "name": "kafka_listeners",\n
"description": "Kafka listeners (AMBARI-10984)",\n "min_version":
"2.3.0.0"\n},\n{\n "name": "kafka_kerberos",\n "description":
"Kafka Kerberos support (AMBARI-10984)",\n "min_version": "2.3.0.0"\n
},\n{\n "name": "pig_on_tez",\n "description": "Pig on Tez
support (AMBARI-7863)",\n "min_version": "2.2.0.0"\n},\n{\n
"name": "ranger_usersync_non_root",\n "description": "Ranger Usersync as
non-root user (AMBARI-10416)",\n "min_version": "2.3.0.0"\n},\n{\n
"name": "ranger_audit_db_support",\n "description": "Ranger Audit to
DB support",\n "min_version": "2.2.0.0",\n "max_version": "2.5.0.0"\n
},\n{\n "name": "accumulo_kerberos_user_auth",\n
"description": "Accumulo Kerberos User Auth (AMBARI-10163)",\n
"min_version": "2.3.0.0"\n},\n{\n "name":
"knox_versioned_data_dir",\n "description": "Use versioned data dir for
Knox (AMBARI-13164)",\n "min_version": "2.3.2.0"\n},\n{\n
"name": "knox_sso_topology",\n
[jira] [Commented] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
[ https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390417#comment-15390417 ] Sriharsha Chintalapani commented on AMBARI-17861: - Thanks for the help [~sumitmohanty] . +1 on the follow-up patch. > Ambari principal should be part of nimbus.admins for Storm View > --- > > Key: AMBARI-17861 > URL: https://issues.apache.org/jira/browse/AMBARI-17861 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17861-II.patch, AMBARI-17861.patch, > AMBARI-17861.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390308#comment-15390308 ] Sriharsha Chintalapani commented on AMBARI-16027: - [~sumitmohanty] earlier we removed the port during hte upgrade. With this patch we are keeping the config as user might have changed the port but we need to preserve that port and reapply as part of new config. So thats what causing this unit test failure. > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
[ https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17861: Attachment: AMBARI-17861.patch > Ambari principal should be part of nimbus.admins for Storm View > --- > > Key: AMBARI-17861 > URL: https://issues.apache.org/jira/browse/AMBARI-17861 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17861.patch, AMBARI-17861.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
[ https://issues.apache.org/jira/browse/AMBARI-17861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17861: Attachment: AMBARI-17861.patch > Ambari principal should be part of nimbus.admins for Storm View > --- > > Key: AMBARI-17861 > URL: https://issues.apache.org/jira/browse/AMBARI-17861 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17861.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17861) Ambari principal should be part of nimbus.admins for Storm View
Sriharsha Chintalapani created AMBARI-17861: --- Summary: Ambari principal should be part of nimbus.admins for Storm View Key: AMBARI-17861 URL: https://issues.apache.org/jira/browse/AMBARI-17861 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Blocker Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17817) Storm Ambari View should use proxy for secure clusters
[ https://issues.apache.org/jira/browse/AMBARI-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17817: Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for review [~jaimin] > Storm Ambari View should use proxy for secure clusters > -- > > Key: AMBARI-17817 > URL: https://issues.apache.org/jira/browse/AMBARI-17817 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-17817.patch > > > We observed that in secure cluster where ambari has SSL configured. Storm > Ambari view fails to make http calls to Storm REST API as it won't be allowed > to make calls from https origin to http destination. > When we used ambari proxy this issue resolved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17839) Ambari URLStreamProvider doesn't store the cookies
Sriharsha Chintalapani created AMBARI-17839: --- Summary: Ambari URLStreamProvider doesn't store the cookies Key: AMBARI-17839 URL: https://issues.apache.org/jira/browse/AMBARI-17839 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Mahadev konar Priority: Blocker Fix For: 2.4.0 Views generally makes calls via Ambari Proxy Server using URLStreamProvider. This is necessary as making direct calls to the Service REST-APIs is not desirable especially incase if ambari server is running with HTTPS and where as service rest apis are running with HTTP, these calls won't work. URLStreamProvider currently doesn't store any cookies from the responses. This is required, In case of Storm where we use SPNEGO auth it returns a "hadoop-auth" cookie but it doesn't get stored and we get auth exceptions. This works fine if we open the storm-ui directly in the browser which drops hadoop-auth cookie and ambari-server is able to read this cookie and send it to the storm-ui server . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17817) Storm Ambari View should use proxy for secure clusters
[ https://issues.apache.org/jira/browse/AMBARI-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17817: Attachment: AMBARI-17817.patch > Storm Ambari View should use proxy for secure clusters > -- > > Key: AMBARI-17817 > URL: https://issues.apache.org/jira/browse/AMBARI-17817 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-17817.patch > > > We observed that in secure cluster where ambari has SSL configured. Storm > Ambari view fails to make http calls to Storm REST API as it won't be allowed > to make calls from https origin to http destination. > When we used ambari proxy this issue resolved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17817) Storm Ambari View should use proxy for secure clusters
Sriharsha Chintalapani created AMBARI-17817: --- Summary: Storm Ambari View should use proxy for secure clusters Key: AMBARI-17817 URL: https://issues.apache.org/jira/browse/AMBARI-17817 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani We observed that in secure cluster where ambari has SSL configured. Storm Ambari view fails to make http calls to Storm REST API as it won't be allowed to make calls from https origin to http destination. When we used ambari proxy this issue resolved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385875#comment-15385875 ] Sriharsha Chintalapani commented on AMBARI-16027: - [~afernandez] the test failures not related to the patch. Can you take a look resolve this. > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Status: Open (was: Patch Available) > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Attachment: AMBARI-16027-V1.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Status: Patch Available (was: Open) > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027-V1.patch, AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved AMBARI-17641. - Resolution: Fixed > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641-V4.patch, > AMBARI-17641.addendum.patch, AMBARI-17641.patch, > Ambari-17641-patch-appied-installed-Storm-step-1.png, > after-kerborizing-step-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383117#comment-15383117 ] Sriharsha Chintalapani commented on AMBARI-17641: - +1. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641-V4.patch, > AMBARI-17641.addendum.patch, AMBARI-17641.patch, > Ambari-17641-patch-appied-installed-Storm-step-1.png, > after-kerborizing-step-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15383117#comment-15383117 ] Sriharsha Chintalapani edited comment on AMBARI-17641 at 7/18/16 9:32 PM: -- +1 on addendum patch. was (Author: sriharsha): +1. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641-V4.patch, > AMBARI-17641.addendum.patch, AMBARI-17641.patch, > Ambari-17641-patch-appied-installed-Storm-step-1.png, > after-kerborizing-step-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Attachment: AMBARI-17641-V4.patch > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641-V4.patch, > AMBARI-17641.patch, Ambari-17641-patch-appied-installed-Storm-step-1.png, > after-kerborizing-step-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Attachment: after-kerborizing-step-2.png Installed and verified storm and enabled security . Ran storm service check as well. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641-V4.patch, > AMBARI-17641.patch, Ambari-17641-patch-appied-installed-Storm-step-1.png, > after-kerborizing-step-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Attachment: Ambari-17641-patch-appied-installed-Storm-step-1.png Patch applied and installed the storm in non-secure cluster. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641-V4.patch, > AMBARI-17641.patch, Ambari-17641-patch-appied-installed-Storm-step-1.png, > after-kerborizing-step-2.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Assignee: Jaimin D Jetly (was: Sriharsha Chintalapani) > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Jaimin D Jetly >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Attachment: AMBARI-17641-V2.patch > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641-V2.patch, AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380964#comment-15380964 ] Sriharsha Chintalapani edited comment on AMBARI-17641 at 7/16/16 10:15 PM: --- [~jaimin] currently there is no clear way to add couple of configs via stack advisor in storm.py or params_linux.py https://github.com/hortonworks/ambari/blob/apache-ref/trunk/ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/package/scripts/storm.py all the dictionaries coming to params_linux.py or storm.py are immutable so I won't be able to add them to config without hacking around to convert the dictionaries from immutable to mutable and back to immutable. More over we are currently driving any special case handling via StackFeature class. This feels very rigid for stack developers. I as a stack developer shouldn't be writing code or changing adding to constants.py in ambari-common. This should be handled via config file under stacks. I am adding a patch thats not working because of storm-site immutable structure. Assigning this back to you please fix how you see fit. was (Author: sriharsha): [~jaimin] currently there is no clear way to add couple of configs via stack advisor in storm.py or params_linux.py https://github.com/hortonworks/ambari/blob/apache-ref/trunk/ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/package/scripts/storm.py all the dictionaries coming to params_linux.py or storm.py are immutable so I won't be able to add them to config without hacking around to convert the dictionaries from immutable to mutable and back to immutable. I am adding a patch thats not working be cause of immutable structure. Assigning this back to you please fix how you see fit. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380964#comment-15380964 ] Sriharsha Chintalapani edited comment on AMBARI-17641 at 7/16/16 10:09 PM: --- [~jaimin] currently there is no clear way to add couple of configs via stack advisor in storm.py or params_linux.py https://github.com/hortonworks/ambari/blob/apache-ref/trunk/ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/package/scripts/storm.py all the dictionaries coming to params_linux.py or storm.py are immutable so I won't be able to add them to config without hacking around to convert the dictionaries from immutable to mutable and back to immutable. I am adding a patch thats not working be cause of immutable structure. Assigning this back to you please fix how you see fit. was (Author: sriharsha): [~jaimin] currently there is no clear way to add couple of configs via stack advisor in storm.py or params_linux.py https://github.com/hortonworks/ambari/blob/apache-ref/trunk/ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/package/scripts/storm.py all the dictionaries coming to params_linux.py or storm.py are immutable so I won't be able to add them to config without hacking around to convert the dictionaries from immutable to mutable and back to immutable. More over we are driving checking which version certain case should be handle via StackFeatures.py. This is by far the most rigid way to add a feature for stack dev. As a stack dev why I need to go and add code to core ambari libraries. This should be driven by a spec file which should reside inside stacks. Unfortunately now I've to go and add bunch of stuff in core libs and figure out how to test that part. I am adding a patch thats not working be cause of immutable structure. Assigning this back to you please fix how you see fit. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380964#comment-15380964 ] Sriharsha Chintalapani commented on AMBARI-17641: - [~jaimin] currently there is no clear way to add couple of configs via stack advisor in storm.py or params_linux.py https://github.com/hortonworks/ambari/blob/apache-ref/trunk/ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/STORM/package/scripts/storm.py all the dictionaries coming to params_linux.py or storm.py are immutable so I won't be able to add them to config without hacking around to convert the dictionaries from immutable to mutable and back to immutable. More over we are driving checking which version certain case should be handle via StackFeatures.py. This is by far the most rigid way to add a feature for stack dev. As a stack dev why I need to go and add code to core ambari libraries. This should be driven by a spec file which should reside inside stacks. Unfortunately now I've to go and add bunch of stuff in core libs and figure out how to test that part. I am adding a patch thats not working be cause of immutable structure. Assigning this back to you please fix how you see fit. > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15380021#comment-15380021 ] Sriharsha Chintalapani commented on AMBARI-17641: - [~jaimin] I am not sure how the patch I added is any different than what we've here https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/STORM/1.0.1/kerberos.json#L43 IMO, I keep hearing different stories about use kerberos.json depending on who you ask. Its upto ambari to enforce the rule on weather we should add the configs in kerberos.json or in stack advisor. Right now we have 2 ways to do the same thing > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17640) Storm Ambari View should provide a config page & make calls to Storm Rest API
[ https://issues.apache.org/jira/browse/AMBARI-17640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17640: Status: Patch Available (was: Open) > Storm Ambari View should provide a config page & make calls to Storm Rest API > - > > Key: AMBARI-17640 > URL: https://issues.apache.org/jira/browse/AMBARI-17640 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.4.0 > > Attachments: > 0001-Updated-storm-view-with-cors-support-and-search-logs.patch > > > 1. Config page to add storm UI REST API server > 2. Make storm view to call UI Rest API directly instead of going through > ambari server. > 3. Additional small fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17640) Storm Ambari View should provide a config page & make calls to Storm Rest API
[ https://issues.apache.org/jira/browse/AMBARI-17640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17640: Attachment: 0001-Updated-storm-view-with-cors-support-and-search-logs.patch > Storm Ambari View should provide a config page & make calls to Storm Rest API > - > > Key: AMBARI-17640 > URL: https://issues.apache.org/jira/browse/AMBARI-17640 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.4.0 > > Attachments: > 0001-Updated-storm-view-with-cors-support-and-search-logs.patch > > > 1. Config page to add storm UI REST API server > 2. Make storm view to call UI Rest API directly instead of going through > ambari server. > 3. Additional small fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17640) Storm Ambari View should provide a config page & make calls to Storm Rest API
[ https://issues.apache.org/jira/browse/AMBARI-17640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17640: Summary: Storm Ambari View should provide a config page & make calls to Storm Rest API (was: Storm Ambari View should provide a config page) > Storm Ambari View should provide a config page & make calls to Storm Rest API > - > > Key: AMBARI-17640 > URL: https://issues.apache.org/jira/browse/AMBARI-17640 > Project: Ambari > Issue Type: Improvement >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.4.0 > > > 1. Config page to add storm UI REST API server > 2. Make storm view to call UI Rest API directly instead of going through > ambari server. > 3. Additional small fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Attachment: AMBARI-17641.patch > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17641) Add storm impersonation authorized along with default ACL
[ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17641: Status: Patch Available (was: Open) > Add storm impersonation authorized along with default ACL > - > > Key: AMBARI-17641 > URL: https://issues.apache.org/jira/browse/AMBARI-17641 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17641.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17641) Add storm impersonation authorized along with default ACL
Sriharsha Chintalapani created AMBARI-17641: --- Summary: Add storm impersonation authorized along with default ACL Key: AMBARI-17641 URL: https://issues.apache.org/jira/browse/AMBARI-17641 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Blocker Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17640) Storm Ambari View should provide a config page
Sriharsha Chintalapani created AMBARI-17640: --- Summary: Storm Ambari View should provide a config page Key: AMBARI-17640 URL: https://issues.apache.org/jira/browse/AMBARI-17640 Project: Ambari Issue Type: Improvement Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Critical Fix For: 2.4.0 1. Config page to add storm UI REST API server 2. Make storm view to call UI Rest API directly instead of going through ambari server. 3. Additional small fixes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17324) kafka should set zookeeper.set.acl to true when kerberos enabled
[ https://issues.apache.org/jira/browse/AMBARI-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17324: Status: Patch Available (was: Open) > kafka should set zookeeper.set.acl to true when kerberos enabled > > > Key: AMBARI-17324 > URL: https://issues.apache.org/jira/browse/AMBARI-17324 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17324.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17324) kafka should set zookeeper.set.acl to true when kerberos enabled
[ https://issues.apache.org/jira/browse/AMBARI-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17324: Attachment: AMBARI-17324.patch > kafka should set zookeeper.set.acl to true when kerberos enabled > > > Key: AMBARI-17324 > URL: https://issues.apache.org/jira/browse/AMBARI-17324 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-17324.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Status: Patch Available (was: Open) > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16027) Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking
[ https://issues.apache.org/jira/browse/AMBARI-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16027: Attachment: AMBARI-16027.patch > Kafka upgrade from HDP 2.2 to HDP 2.3 is breaking > - > > Key: AMBARI-16027 > URL: https://issues.apache.org/jira/browse/AMBARI-16027 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16027.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15966) ambari-web 2.2.1 build error
[ https://issues.apache.org/jira/browse/AMBARI-15966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15361724#comment-15361724 ] Sriharsha Chintalapani commented on AMBARI-15966: - same issue here node --version v5.9.0 npm --version 3.7.3 brunch version: 2.8.0 > ambari-web 2.2.1 build error > > > Key: AMBARI-15966 > URL: https://issues.apache.org/jira/browse/AMBARI-15966 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: skrho >Assignee: Jaimin D Jetly > Fix For: 2.4.0 > > > Hi Everyone~~ > Now I am building the ambari-web 2.2.1 version > My Environment is > npm : 3.8.7 > node : 4.4.3 > brunch : 2.5.3 > I have a problem when building .. > I just command > # $apache-ambari-2.2.1-src/ambari-web]#brunch build -d > There is error message > brunch:config Trying to load brunch-config +0ms > brunch:config Trying to load config +5ms > 19 Apr 08:26:28 - warn: config.files.stylesheets.defaultPaths was removed > 19 Apr 08:26:28 - warn: config.files.templates.defaultPaths was removed > 19 Apr 08:26:28 - error: Initialization error - You probably need to execute > `npm install` to install brunch plugins. SyntaxError: Setter must have > exactly one formal parameter. > at /usr/lib/node_modules/brunch/lib/plugins.js:101:17 > at Array.map (native) > at deps.filter.dependency.map > (/usr/lib/node_modules/brunch/lib/plugins.js:88:8) > at packages.filter.plugins.map.plugin.filter.deps.filter.allPlugins.filter > (/usr/lib/node_modules/brunch/lib/plugins.js:108:19) > at > Object.packages.filter.plugins.map.plugin.filter.deps.filter.exports.init.plugins.filter.map.preCompilers.push.teardownBrunch > [as init] (/usr/lib/node_modules/brunch/lib/plugins.js:131:20) > at /usr/lib/node_modules/brunch/lib/watch.js:101:19 > Please Help me~ > What can I do that? > In advanced Thank you everyone -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17324) kafka should set zookeeper.set.acl to true when kerberos enabled
[ https://issues.apache.org/jira/browse/AMBARI-17324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17324: Summary: kafka should set zookeeper.set.acl to true when kerberos enabled (was: kafka should set zookeeper.set.acl to true upon kerberorization) > kafka should set zookeeper.set.acl to true when kerberos enabled > > > Key: AMBARI-17324 > URL: https://issues.apache.org/jira/browse/AMBARI-17324 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17324) kafka should set zookeeper.set.acl to true upon kerberorization
Sriharsha Chintalapani created AMBARI-17324: --- Summary: kafka should set zookeeper.set.acl to true upon kerberorization Key: AMBARI-17324 URL: https://issues.apache.org/jira/browse/AMBARI-17324 Project: Ambari Issue Type: Bug Affects Versions: 2.2.0 Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Blocker Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17157) Storm 1.0 log4j config update
[ https://issues.apache.org/jira/browse/AMBARI-17157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17157: Attachment: AMBARI-17157.patch > Storm 1.0 log4j config update > - > > Key: AMBARI-17157 > URL: https://issues.apache.org/jira/browse/AMBARI-17157 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.4.0 > > Attachments: AMBARI-17157.patch, AMBARI-17157.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17157) Storm 1.0 log4j config update
[ https://issues.apache.org/jira/browse/AMBARI-17157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-17157: Attachment: AMBARI-17157.patch > Storm 1.0 log4j config update > - > > Key: AMBARI-17157 > URL: https://issues.apache.org/jira/browse/AMBARI-17157 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Fix For: 2.4.0 > > Attachments: AMBARI-17157.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17157) Storm 1.0 log4j config update
Sriharsha Chintalapani created AMBARI-17157: --- Summary: Storm 1.0 log4j config update Key: AMBARI-17157 URL: https://issues.apache.org/jira/browse/AMBARI-17157 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16946) Storm Metrics Sink has high chance to discard some datapoints
[ https://issues.apache.org/jira/browse/AMBARI-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306267#comment-15306267 ] Sriharsha Chintalapani commented on AMBARI-16946: - [~kabhwan] no lets create the patch against trunk > Storm Metrics Sink has high chance to discard some datapoints > - > > Key: AMBARI-16946 > URL: https://issues.apache.org/jira/browse/AMBARI-16946 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-16946.patch > > > There's a mismatch between TimelineMetricsCache and Storm metrics unit, while > TimelineMetricsCache considers "metric name + timestamp" to be unique but > Storm is not. > For example, assume that bolt B has task T1, T2 and B has registered metrics > M1. It's possible for metrics sink to receive (T1, M1) and (T2, M1) with same > timestamp TS1 (in TaskInfo, not current time), and received later will be > discarded from TimelineMetricsCache. > If we want to have unique metric point of Storm, we should use "topology name > + component name + task id + metric name" to metric name so that "metric name > + timestamp" will be unique. > There're other issues I would like to address, too. > - Currently, hostname is written to hostname of the machine which runs > metrics sink. Since TaskInfo has hostname of the machine which runs task, > we're better to use this. > - Unit of timestamp of TaskInfo is second, while Storm Metrics Sink uses this > as millisecond, resulting in timestamp flaw, and malfunction of cache > eviction. It should be multiplied by 1000. > - 'component name' is not unique across the cluster, so it's not fit for app > id. 'topology name' is unique so proper value of app id is topology name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16946) Storm Metrics Sink has high chance to discard some datapoints
[
https://issues.apache.org/jira/browse/AMBARI-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306253#comment-15306253
]
Sriharsha Chintalapani commented on AMBARI-16946:
-
[~kabhwan] I usually do
{code}
git diff origin/trunk > AMBARI-16946.patch
{code}
to create a patch. Looks like the patch you attached is not cleanly applying
> Storm Metrics Sink has high chance to discard some datapoints
> -
>
> Key: AMBARI-16946
> URL: https://issues.apache.org/jira/browse/AMBARI-16946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.0
>Reporter: Jungtaek Lim
> Attachments: AMBARI-16946.patch
>
>
> There's a mismatch between TimelineMetricsCache and Storm metrics unit, while
> TimelineMetricsCache considers "metric name + timestamp" to be unique but
> Storm is not.
> For example, assume that bolt B has task T1, T2 and B has registered metrics
> M1. It's possible for metrics sink to receive (T1, M1) and (T2, M1) with same
> timestamp TS1 (in TaskInfo, not current time), and received later will be
> discarded from TimelineMetricsCache.
> If we want to have unique metric point of Storm, we should use "topology name
> + component name + task id + metric name" to metric name so that "metric name
> + timestamp" will be unique.
> There're other issues I would like to address, too.
> - Currently, hostname is written to hostname of the machine which runs
> metrics sink. Since TaskInfo has hostname of the machine which runs task,
> we're better to use this.
> - Unit of timestamp of TaskInfo is second, while Storm Metrics Sink uses this
> as millisecond, resulting in timestamp flaw, and malfunction of cache
> eviction. It should be multiplied by 1000.
> - 'component name' is not unique across the cluster, so it's not fit for app
> id. 'topology name' is unique so proper value of app id is topology name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16946) Storm Metrics Sink has high chance to discard some datapoints
[ https://issues.apache.org/jira/browse/AMBARI-16946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306236#comment-15306236 ] Sriharsha Chintalapani commented on AMBARI-16946: - [~kabhwan] you need to attach the patch here https://reviews.apache.org/dashboard/ . Use Ambari as project and add my self and [~swagle] as reviewers . > Storm Metrics Sink has high chance to discard some datapoints > - > > Key: AMBARI-16946 > URL: https://issues.apache.org/jira/browse/AMBARI-16946 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.0 >Reporter: Jungtaek Lim > Attachments: AMBARI-16946.patch > > > There's a mismatch between TimelineMetricsCache and Storm metrics unit, while > TimelineMetricsCache considers "metric name + timestamp" to be unique but > Storm is not. > For example, assume that bolt B has task T1, T2 and B has registered metrics > M1. It's possible for metrics sink to receive (T1, M1) and (T2, M1) with same > timestamp TS1 (in TaskInfo, not current time), and received later will be > discarded from TimelineMetricsCache. > If we want to have unique metric point of Storm, we should use "topology name > + component name + task id + metric name" to metric name so that "metric name > + timestamp" will be unique. > There're other issues I would like to address, too. > - Currently, hostname is written to hostname of the machine which runs > metrics sink. Since TaskInfo has hostname of the machine which runs task, > we're better to use this. > - Unit of timestamp of TaskInfo is second, while Storm Metrics Sink uses this > as millisecond, resulting in timestamp flaw, and malfunction of cache > eviction. It should be multiplied by 1000. > - 'component name' is not unique across the cluster, so it's not fit for app > id. 'topology name' is unique so proper value of app id is topology name. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16648) Upgrade pack changes to work with Storm 1.0
[ https://issues.apache.org/jira/browse/AMBARI-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16648: Status: Open (was: Patch Available) > Upgrade pack changes to work with Storm 1.0 > --- > > Key: AMBARI-16648 > URL: https://issues.apache.org/jira/browse/AMBARI-16648 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-16648.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16648) Upgrade pack changes to work with Storm 1.0
[ https://issues.apache.org/jira/browse/AMBARI-16648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-16648: Attachment: AMBARI-16648.patch > Upgrade pack changes to work with Storm 1.0 > --- > > Key: AMBARI-16648 > URL: https://issues.apache.org/jira/browse/AMBARI-16648 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani > Attachments: AMBARI-16648.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
