[jira] [Resolved] (STORM-3198) Topology submitters should be able to supply log4j2 configurations
[ https://issues.apache.org/jira/browse/STORM-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3198. Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~jtolar], I merged this into master. > Topology submitters should be able to supply log4j2 configurations > -- > > Key: STORM-3198 > URL: https://issues.apache.org/jira/browse/STORM-3198 > Project: Apache Storm > Issue Type: Improvement >Reporter: Jacob Tolar >Assignee: Jacob Tolar >Priority: Minor > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > As a topology submitter, I would like to submit a log4j2 configuration > alongside my topology to easily control my application's logging parameters. > > For example, I might need to reduce the log level of a particularly noisy > dependency. Or, I might want to add a filter to drop these messages. > > Since log4j supports [composite > configurations|https://logging.apache.org/log4j/2.x/manual/configuration.html#CompositeConfiguration], > Storm could support the user passing in a log4j2.xml file to be combined > with the 'default' log4j2.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-2832) misuse of Utils.readStormConfig() and ConfigUtils.readStormConfig()
[ https://issues.apache.org/jira/browse/STORM-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-2832. Resolution: Fixed Fix Version/s: 2.0.0 Thanks [~jingc], I merged this into master. > misuse of Utils.readStormConfig() and ConfigUtils.readStormConfig() > --- > > Key: STORM-2832 > URL: https://issues.apache.org/jira/browse/STORM-2832 > Project: Apache Storm > Issue Type: Improvement >Reporter: Ethan Li >Assignee: Jing Chen >Priority: Minor > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We want to validate confs before launching daemons. However, code in many > places uses Utils.readStormConfig() instead of ConfigUtils.readStormConfig(). > We should change them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (STORM-2832) misuse of Utils.readStormConfig() and ConfigUtils.readStormConfig()
[ https://issues.apache.org/jira/browse/STORM-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reassigned STORM-2832: -- Assignee: Jing Chen > misuse of Utils.readStormConfig() and ConfigUtils.readStormConfig() > --- > > Key: STORM-2832 > URL: https://issues.apache.org/jira/browse/STORM-2832 > Project: Apache Storm > Issue Type: Improvement >Reporter: Ethan Li >Assignee: Jing Chen >Priority: Minor > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > We want to validate confs before launching daemons. However, code in many > places uses Utils.readStormConfig() instead of ConfigUtils.readStormConfig(). > We should change them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3216) RAS aware blacklisting strategy needed
[ https://issues.apache.org/jira/browse/STORM-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3216. Resolution: Fixed Fix Version/s: 2.0.0 > RAS aware blacklisting strategy needed > -- > > Key: STORM-3216 > URL: https://issues.apache.org/jira/browse/STORM-3216 > Project: Apache Storm > Issue Type: Bug >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The current DefaultBlacklisting strategy only looks at slots, and is not > really compatible with RAS. We should at least make a version that is RAS > compatible. and then look at finding a better way to have a scheduler ask for > resources to be released when needed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3199) Metrics-ganglia depends on an LGPL library, so we shouldn't depend on it
[ https://issues.apache.org/jira/browse/STORM-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3199. Resolution: Fixed Fix Version/s: 1.2.3 2.0.0 > Metrics-ganglia depends on an LGPL library, so we shouldn't depend on it > > > Key: STORM-3199 > URL: https://issues.apache.org/jira/browse/STORM-3199 > Project: Apache Storm > Issue Type: Task >Affects Versions: 2.0.0, 1.2.0, 1.2.1, 1.2.2 >Reporter: Stig Rohde Døssing >Assignee: Stig Rohde Døssing >Priority: Blocker > Labels: pull-request-available > Fix For: 2.0.0, 1.2.3 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > https://issues.apache.org/jira/browse/STORM-2153 introduced a dependency on > metrics-ganglia, which depends on remotetea-oncrpc. This library appears to > be licensed under LGPL. > The Dropwizard metrics project removed it for the same reason > https://github.com/dropwizard/metrics/issues/1319. I think we also need to > get rid of it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (STORM-3217) Component errors missing in /api/v1/component API call
[ https://issues.apache.org/jira/browse/STORM-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans reassigned STORM-3217: -- Assignee: Govind Menon > Component errors missing in /api/v1/component API call > -- > > Key: STORM-3217 > URL: https://issues.apache.org/jira/browse/STORM-3217 > Project: Apache Storm > Issue Type: Bug > Components: storm-webapp >Reporter: Govind Menon >Assignee: Govind Menon >Priority: Major > > componentErrors and other component stats were missed by me in the migration. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (STORM-3217) Component errors missing in /api/v1/component API call
Govind Menon created STORM-3217: --- Summary: Component errors missing in /api/v1/component API call Key: STORM-3217 URL: https://issues.apache.org/jira/browse/STORM-3217 Project: Apache Storm Issue Type: Bug Components: storm-webapp Reporter: Govind Menon componentErrors and other component stats were missed by me in the migration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
