[jira] [Created] (STORM-3273) Don't pass storm.local.hostname to topology conf
Robert Joseph Evans created STORM-3273: -- Summary: Don't pass storm.local.hostname to topology conf Key: STORM-3273 URL: https://issues.apache.org/jira/browse/STORM-3273 Project: Apache Storm Issue Type: Bug Components: storm-server Affects Versions: 2.0.0 Reporter: Robert Joseph Evans Assignee: Robert Joseph Evans We have found that if we set storm.local.hostname on nimbus it gets put into the topology conf which in turn causes the topology to report all metrics as coming from nimbus, which is not what we want. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3272) supervisor can fail to delete topology stormdist folder
[ https://issues.apache.org/jira/browse/STORM-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3272: -- Labels: pull-request-available (was: ) > supervisor can fail to delete topology stormdist folder > --- > > Key: STORM-3272 > URL: https://issues.apache.org/jira/browse/STORM-3272 > Project: Apache Storm > Issue Type: Bug >Reporter: Aaron Gresch >Assignee: Aaron Gresch >Priority: Major > Labels: pull-request-available > > Upon investigating supervisor restarts, I saw messages such as: > > 2018-10-19 23:01:38.816 o.a.s.u.Utils Thread-20731 [INFO] UNNAMED:rmdir of > /home/y/var/storm/supervisor/stormdist/XXX-124-1539730805 failed - Directory > not empty > > Looking further, the directory contained a symlink that pointed at a missing > file. Investigating worker-launcher code, this looks like it sees that this > is a file that does not exist, so it does not process the symlink, preventing > deletion of the directory. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (STORM-3273) Don't pass storm.local.hostname to topology conf
[ https://issues.apache.org/jira/browse/STORM-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660710#comment-16660710 ] Robert Joseph Evans commented on STORM-3273: In the latest versions of ZK this is mostly fixed. There are some cases where it will shut down the entire server if there are errors. But I don't think that they are good enough and we need to extend it further. > Don't pass storm.local.hostname to topology conf > > > Key: STORM-3273 > URL: https://issues.apache.org/jira/browse/STORM-3273 > Project: Apache Storm > Issue Type: Bug > Components: storm-server >Affects Versions: 2.0.0 >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > > We have found that if we set storm.local.hostname on nimbus it gets put into > the topology conf which in turn causes the topology to report all metrics as > coming from nimbus, which is not what we want. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (STORM-3273) Don't pass storm.local.hostname to topology conf
[ https://issues.apache.org/jira/browse/STORM-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans updated STORM-3273: --- Comment: was deleted (was: In the latest versions of ZK this is mostly fixed. There are some cases where it will shut down the entire server if there are errors. But I don't think that they are good enough and we need to extend it further.) > Don't pass storm.local.hostname to topology conf > > > Key: STORM-3273 > URL: https://issues.apache.org/jira/browse/STORM-3273 > Project: Apache Storm > Issue Type: Bug > Components: storm-server >Affects Versions: 2.0.0 >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > > We have found that if we set storm.local.hostname on nimbus it gets put into > the topology conf which in turn causes the topology to report all metrics as > coming from nimbus, which is not what we want. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (STORM-3273) Don't pass storm.local.hostname to topology conf
[ https://issues.apache.org/jira/browse/STORM-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated STORM-3273: -- Labels: pull-request-available (was: ) > Don't pass storm.local.hostname to topology conf > > > Key: STORM-3273 > URL: https://issues.apache.org/jira/browse/STORM-3273 > Project: Apache Storm > Issue Type: Bug > Components: storm-server >Affects Versions: 2.0.0 >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Critical > Labels: pull-request-available > > We have found that if we set storm.local.hostname on nimbus it gets put into > the topology conf which in turn causes the topology to report all metrics as > coming from nimbus, which is not what we want. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3260) Add in more admin commands to debug cluster state
[ https://issues.apache.org/jira/browse/STORM-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3260. Resolution: Fixed Fix Version/s: 2.0.0 > Add in more admin commands to debug cluster state > - > > Key: STORM-3260 > URL: https://issues.apache.org/jira/browse/STORM-3260 > Project: Apache Storm > Issue Type: Improvement > Components: storm-server >Reporter: Robert Joseph Evans >Assignee: Robert Joseph Evans >Priority: Major > Labels: pull-request-available > Fix For: 2.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > It would be really nice to have more visibility into exactly what is stored > in ZK. Specifically the topology that the user submitted to us. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (STORM-3269) storm-client and storm-server indirectly depend on storm-core
[ https://issues.apache.org/jira/browse/STORM-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-3269. Resolution: Fixed Fix Version/s: 2.0.0 > storm-client and storm-server indirectly depend on storm-core > - > > Key: STORM-3269 > URL: https://issues.apache.org/jira/browse/STORM-3269 > Project: Apache Storm > Issue Type: Bug > Components: storm-client, storm-core, storm-server >Affects Versions: 2.0.0 >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 > > When trying to get the version information for nimbus it looks for > storm-core, which requires the storm-core class to be on the classpath. We > need to fix this, because VersionInfo is in storm-client so it is possible > for someone who uses it from storm-client to load the wrong thing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
