[jira] [Commented] (STORM-994) Connection leak between nimbus and supervisors

[ https://issues.apache.org/jira/browse/STORM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727018#comment-14727018 ] Frantz Mazoyer commented on STORM-994: -- My pleasure :-) Thanks for merging. > Connection leak between

[jira] [Commented] (STORM-1024) log4j changes leaving ${sys:storm.log.dir} under STORM_HOME dir

[ https://issues.apache.org/jira/browse/STORM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727714#comment-14727714 ] ASF GitHub Bot commented on STORM-1024: --- Github user harshach commented on the pull request:

[jira] [Commented] (STORM-1024) log4j changes leaving ${sys:storm.log.dir} under STORM_HOME dir

[ https://issues.apache.org/jira/browse/STORM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727700#comment-14727700 ] Arun Mahadevan commented on STORM-1024: --- [~sriharsha] Please review > log4j changes leaving

[GitHub] storm pull request: [STORM-1024] Pass -Dstorm.log.dir arg to LogWr...

GitHub user arunmahadevan opened a pull request: https://github.com/apache/storm/pull/714 [STORM-1024] Pass -Dstorm.log.dir arg to LogWriter The log4j variable `${sys:storm.log.dir}` is used in `worker.xml` to set the fileName however the system property was not being set while

[jira] [Commented] (STORM-1024) log4j changes leaving ${sys:storm.log.dir} under STORM_HOME dir

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

[GitHub] storm pull request: [STORM-1024] Pass -Dstorm.log.dir arg to LogWr...

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/714#issuecomment-137184747 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled

[jira] [Commented] (STORM-1024) log4j changes leaving ${sys:storm.log.dir} under STORM_HOME dir

[ https://issues.apache.org/jira/browse/STORM-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727680#comment-14727680 ] Arun Mahadevan commented on STORM-1024: --- It appears that the "-Dstorm.log.dir" arg is not passed to

[GitHub] storm pull request: [STORM-1005]replace default storm.local.dir va...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/713#issuecomment-137288071 One thing we should keep in mind is, some users are using Storm in Windows environment. Using absolute path, especially known *nix path to default value will make

[jira] [Commented] (STORM-1005) Supervisor do not get running workers after restart.

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

[GitHub] storm pull request: STORM-1026: Expand external classpaths to incl...

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/715#discussion_r38604124 --- Diff: bin/storm.py --- @@ -103,6 +103,12 @@ def get_config_opts(): sys.exit(1) def get_jars_full(adir): +files = [] +

[jira] [Commented] (STORM-1026) Adding external classpath elements does not work

[ https://issues.apache.org/jira/browse/STORM-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728337#comment-14728337 ] ASF GitHub Bot commented on STORM-1026: --- Github user HeartSaVioR commented on a diff in the pull

[GitHub] storm pull request: [STORM-1019][STORM-1020] Added missing version...

Github user rmkellogg commented on the pull request: https://github.com/apache/storm/pull/710#issuecomment-137296720 Can we merge this? No idea why Travis-CI is failing. It worked earlier. --- If your project is set up for it, you can reply to this email and have your reply appear

[jira] [Commented] (STORM-1019) Added missing dependency version to use of org.codehaus.mojo:make-maven-plugin

[ https://issues.apache.org/jira/browse/STORM-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728368#comment-14728368 ] ASF GitHub Bot commented on STORM-1019: --- Github user rmkellogg commented on the pull request:

[jira] [Created] (STORM-1026) Adding external classpath elements does not work

Bryan Shell created STORM-1026: -- Summary: Adding external classpath elements does not work Key: STORM-1026 URL: https://issues.apache.org/jira/browse/STORM-1026 Project: Apache Storm Issue

[jira] [Updated] (STORM-1026) Adding external classpath elements does not work

[ https://issues.apache.org/jira/browse/STORM-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Shell updated STORM-1026: --- Description: Adding an external path and/or jar to the classpath fails to work as expected. I would

[jira] [Commented] (STORM-1026) Adding external classpath elements does not work

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

[GitHub] storm pull request: STORM-1026: Expand external classpaths to incl...

GitHub user shellbj opened a pull request: https://github.com/apache/storm/pull/715 STORM-1026: Expand external classpaths to include any jars You can merge this pull request into a Git repository by running: $ git pull https://github.com/shellbj/storm STORM-1026

Storm UI does not load

Hi, I am running Debian Jessy in my laptop. Up to now I never had problems to access Storm UI via Iceweasel (ie, Debian's Firefox). But now, the UI does not load completely. It displays "Loading summary..." and the background is shaded. The cluster summary on top of the page is not rendered

Overflow buffer and metrics

I have been facing a scenario recently wherein the topology is just hung. In stack trace, I can see that KafkaSpout is stuck on metrics_tick.invoke. Since it is not able to find free slot in the disruptor queue. Acker taks is blocked on disruptor queue as well. I noticed that Nathan had a fixed a

[GitHub] storm pull request: STORM-969: HDFS Bolt can end up in an unrecove...

Github user dossett commented on the pull request: https://github.com/apache/storm/pull/664#issuecomment-137064748 @arunmahadevan So it can! PR updated. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[jira] [Commented] (STORM-969) HDFS Bolt can end up in an unrecoverable state

[ https://issues.apache.org/jira/browse/STORM-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727293#comment-14727293 ] ASF GitHub Bot commented on STORM-969: -- Github user dossett commented on the pull request: