[jira] [Commented] (STORM-517) Support for "-Dservice=" in bin/storm, via JAVA_SERVICE_NAME environment variable

[ https://issues.apache.org/jira/browse/STORM-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160004#comment-14160004 ] ASF GitHub Bot commented on STORM-517: -- Github user nathanmarz commented on the pull r

[GitHub] storm pull request: STORM-517: Adding JAVA_SERVICE_NAME to bin/sto...

Github user nathanmarz commented on the pull request: https://github.com/apache/storm/pull/281#issuecomment-57974956 I see. I'd be fine with a different patch which does not use any environment vars and instead sets -Dstorm.service= to be one of "nimbus", "supervisor", or "worker", pa

[jira] [Commented] (STORM-307) After host crash, supervisor is unable to restart itself

[ https://issues.apache.org/jira/browse/STORM-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159698#comment-14159698 ] ASF GitHub Bot commented on STORM-307: -- GitHub user wurstmeister opened a pull request

[GitHub] storm pull request: STORM-307: reset LocalState if files are corru...

GitHub user wurstmeister opened a pull request: https://github.com/apache/storm/pull/282 STORM-307: reset LocalState if files are corrupt * allow supervisor to start even if LocalState files are empty You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (STORM-404) Worker on one machine crashes due to a failure of another worker on another machine

[ https://issues.apache.org/jira/browse/STORM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159600#comment-14159600 ] Nathan Marz commented on STORM-404: --- Yes, switching to ZeroMQ transport may fix the probl

[jira] [Commented] (STORM-517) Support for "-Dservice=" in bin/storm, via JAVA_SERVICE_NAME environment variable

[ https://issues.apache.org/jira/browse/STORM-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159598#comment-14159598 ] ASF GitHub Bot commented on STORM-517: -- Github user solarce commented on the pull requ

[GitHub] storm pull request: STORM-517: Adding JAVA_SERVICE_NAME to bin/sto...

Github user solarce commented on the pull request: https://github.com/apache/storm/pull/281#issuecomment-57945091 @nathanmarz It's not any existing environment variable, it's just a name I made up. I do use nimbus.childops, etc for adding JMX related arguments because

[jira] [Commented] (STORM-404) Worker on one machine crashes due to a failure of another worker on another machine

[ https://issues.apache.org/jira/browse/STORM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159597#comment-14159597 ] Ritesh Adval commented on STORM-404: Hi Nathan, We are using the default Netty transpo

[jira] [Commented] (STORM-404) Worker on one machine crashes due to a failure of another worker on another machine

[ https://issues.apache.org/jira/browse/STORM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159592#comment-14159592 ] Nathan Marz commented on STORM-404: --- Do you see this problem with the ZeroMQ transport or

[jira] [Commented] (STORM-404) Worker on one machine crashes due to a failure of another worker on another machine

[ https://issues.apache.org/jira/browse/STORM-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159560#comment-14159560 ] Ritesh Adval commented on STORM-404: Hi guys, We are having this exact same issue on o

[jira] [Commented] (STORM-213) Decouple In-Process ZooKeeper from LocalCluster

[ https://issues.apache.org/jira/browse/STORM-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159548#comment-14159548 ] ASF GitHub Bot commented on STORM-213: -- Github user btiernay commented on the pull req

[GitHub] storm pull request: STORM-213: fixed NullPointerException

Github user btiernay commented on the pull request: https://github.com/apache/storm/pull/207#issuecomment-57938274 @wurstmeister Ok that's good to know, thanks. Perhaps that shouldn't be in a static initializer to avoid confusion? --- If your project is set up for it, you can reply t

[jira] [Commented] (STORM-487) Remove storm.cmd, no need to duplicate work python runs on windows too.

[ https://issues.apache.org/jira/browse/STORM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159499#comment-14159499 ] ASF GitHub Bot commented on STORM-487: -- Github user ChitturiPadma commented on the pul

[GitHub] storm pull request: STORM-487 Let bin/storm compatible with Window...

Github user ChitturiPadma commented on the pull request: https://github.com/apache/storm/pull/280#issuecomment-57932225 When i worked on storm-0.9.0-rc2, the issue existed only with modified python script that works on windows. storm.cmd doesnt show have this issue in file deletion.

[jira] [Commented] (STORM-487) Remove storm.cmd, no need to duplicate work python runs on windows too.

[ https://issues.apache.org/jira/browse/STORM-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159481#comment-14159481 ] ASF GitHub Bot commented on STORM-487: -- Github user HeartSaVioR commented on the pull

[GitHub] storm pull request: STORM-487 Let bin/storm compatible with Window...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/280#issuecomment-57930437 @ChitturiPadma I've just test killing topology using Storm 0.9.2. There're some warning but supervisor seems to not killed. It seems to have an issue you mention