[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&focusedCommentId=14726788#comment-14726788 ] ASF GitHub Bot commented on STORM-1005: --- GitHub user Renkai opened a pull request:

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

GitHub user Renkai opened a pull request: https://github.com/apache/storm/pull/713 [STORM-1005]replace default storm.local.dir value to absolute path. One of my supervisors shutdown by it self after running for a few weeks.After I restart the supervisor from another director

[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&focusedCommentId=14726696#comment-14726696 ] Renkai Ge commented on STORM-1005: -- I basically know the reason why supervisor do not rec

[jira] [Commented] (STORM-950) Apache Storm website redesign

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

[GitHub] storm pull request: STORM-950. Apache Storm website redesign.

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/670#issuecomment-136895532 @ptgoetz upmerged. Can you take a look. --- 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 d

[jira] [Commented] (STORM-1025) Invalid links at https://storm.apache.org/about/multi-language.html

[ https://issues.apache.org/jira/browse/STORM-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726418#comment-14726418 ] Aaron Coburn commented on STORM-1025: - See the PR here: https://github.com/apache/stor

[jira] [Created] (STORM-1025) Invalid links at https://storm.apache.org/about/multi-language.html

Aaron Coburn created STORM-1025: --- Summary: Invalid links at https://storm.apache.org/about/multi-language.html Key: STORM-1025 URL: https://issues.apache.org/jira/browse/STORM-1025 Project: Apache Storm

[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&focusedCommentId=14726405#comment-14726405 ] ASF GitHub Bot commented on STORM-969: -- Github user arunmahadevan commented on the pul

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

Github user arunmahadevan commented on the pull request: https://github.com/apache/storm/pull/664#issuecomment-136889084 The value of `topology.message.timeout.secs` can be read from the `conf` that gets passed as the first parameter to `doPrepare` --- If your project is set up for i

[GitHub] storm pull request: fix github links

GitHub user acoburn opened a pull request: https://github.com/apache/storm/pull/712 fix github links Several links on https://storm.apache.org/about/multi-language.html are incorrect, this PR fixes them. You can merge this pull request into a Git repository by running: $ git p

[jira] [Resolved] (STORM-1010) Each KafkaBolt could have a specified properties.

[ https://issues.apache.org/jira/browse/STORM-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1010. - Resolution: Fixed Fix Version/s: 0.11.0 Thanks [Renkai Ge], I merged into master. > Each

[GitHub] storm pull request: [STORM-1010] each KafkaBolt have its own prope...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/699 --- 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 and wishes so, or if the feature is enabl

[jira] [Commented] (STORM-1010) Each KafkaBolt could have a specified properties.

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

[jira] [Commented] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

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

[GitHub] storm pull request: STORM-996: netty-unit-tests/test-batch demonst...

Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/711#issuecomment-136884363 +1 Nice work. --- 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 e

[jira] [Resolved] (STORM-1008) Isolate the code for metric collection and retrieval from the DisruptorQueue

[ https://issues.apache.org/jira/browse/STORM-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1008. - Resolution: Fixed Fix Version/s: 0.11.0 Thanks [~wangli1426] I merged into master. > Isola

[jira] [Commented] (STORM-1008) Isolate the code for metric collection and retrieval from the DisruptorQueue

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

[GitHub] storm pull request: [STORM-1008] Isolate the code for metric colle...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/698 --- 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 and wishes so, or if the feature is enabl

[jira] [Updated] (STORM-1008) Isolate the code for metric collection and retrieval from the DisruptorQueue

[ https://issues.apache.org/jira/browse/STORM-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-1008: Fix Version/s: (was: 0.11.0) > Isolate the code for metric collection and retrieval from the Dis

[jira] [Resolved] (STORM-991) General cleanup of the generics (storm.trident.spout package)

[ https://issues.apache.org/jira/browse/STORM-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-991. Resolution: Fixed Assignee: Dean de Bree Fix Version/s: 0.11.0 Thanks [~ddebree] I me

[jira] [Commented] (STORM-991) General cleanup of the generics (storm.trident.spout package)

[ https://issues.apache.org/jira/browse/STORM-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726311#comment-14726311 ] ASF GitHub Bot commented on STORM-991: -- Github user asfgit closed the pull request at:

[GitHub] storm pull request: [STORM-991] General cleanup of the generics.

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/683 --- 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 and wishes so, or if the feature is enabl

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

[ https://issues.apache.org/jira/browse/STORM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-994. Resolution: Fixed Fix Version/s: 0.10.0 Thanks, [~fmazoyer] for finding missed spot. I merged

[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&focusedCommentId=14726289#comment-14726289 ] ASF GitHub Bot commented on STORM-994: -- Github user asfgit closed the pull request at:

[GitHub] storm pull request: STORM-994 Close download clients and channels ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/697 --- 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 and wishes so, or if the feature is enabl

[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&focusedCommentId=14726276#comment-14726276 ] ASF GitHub Bot commented on STORM-969: -- Github user dossett commented on the pull requ

[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-136876170 @arunmahadevan Our approach is to set the tick tuple frequency to be half of the message timeout setting for the topology. Can the bolt get access to that topology setti

[jira] [Resolved] (STORM-1000) Use static member classes when permitted

[ https://issues.apache.org/jira/browse/STORM-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1000. - Resolution: Fixed Fix Version/s: 0.11.0 Thanks, [~YvonneIronberg] I merged into master. >

[jira] [Commented] (STORM-1000) Use static member classes when permitted

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

[GitHub] storm pull request: STORM-1000: Use static member classes when per...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/691 --- 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 and wishes so, or if the feature is enabl

[jira] [Updated] (STORM-130) [Storm 0.8.2]: java.io.FileNotFoundException: File '../stormconf.ser' does not exist

[ https://issues.apache.org/jira/browse/STORM-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jackson Chung updated STORM-130: Attachment: supervisor.log.2015-08-26 [~sriharsha] here u go. you could see there is a halt/restart o

[jira] [Resolved] (STORM-1001) Undefined STORM_EXT_CLASSPATH adds '::' to classpath of workers

[ https://issues.apache.org/jira/browse/STORM-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1001. - Resolution: Fixed Assignee: Drew Robb Fix Version/s: 0.10.0 Thanks, [~drewrobb] I

[jira] [Commented] (STORM-1001) Undefined STORM_EXT_CLASSPATH adds '::' to classpath of workers

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

[GitHub] storm pull request: Fixes STORM-1001

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/695 --- 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 and wishes so, or if the feature is enabl

[jira] [Commented] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

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

[GitHub] storm pull request: STORM-996: netty-unit-tests/test-batch demonst...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/711#issuecomment-136859814 +1 Great! Missed StormClientHandler so there's only one thread which accesses to Client at any time. --- If your project is set up for it, you can reply to this

[jira] [Resolved] (STORM-1003) In cluster.clj replace task-id with component-id in the declaration

[ https://issues.apache.org/jira/browse/STORM-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1003. - Resolution: Fixed Fix Version/s: 0.11.0 Thanks, [~sanket991] I merged into master. > In cl

[jira] [Commented] (STORM-1003) In cluster.clj replace task-id with component-id in the declaration

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

[GitHub] storm pull request: [STORM-1003] Made changed to method declaratio...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/696 --- 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 and wishes so, or if the feature is enabl

[jira] [Resolved] (STORM-1013) [storm-elasticsearch] Expose TransportClient configuration Map to EsConfig

[ https://issues.apache.org/jira/browse/STORM-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim resolved STORM-1013. - Resolution: Fixed Fix Version/s: 0.11.0 > [storm-elasticsearch] Expose TransportClient conf

[jira] [Commented] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

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

[GitHub] storm pull request: STORM-996: netty-unit-tests/test-batch demonst...

Github user kishorvpatil commented on the pull request: https://github.com/apache/storm/pull/711#issuecomment-136840377 LGTM. +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 e

[jira] [Commented] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

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

[GitHub] storm pull request: STORM-996: netty-unit-tests/test-batch demonst...

Github user d2r commented on the pull request: https://github.com/apache/storm/pull/711#issuecomment-136813085 +1 This seems to fix the issue. I ran test-batch ~50 times without a failure. --- If your project is set up for it, you can reply to this email and have your reply appear on

[jira] [Commented] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

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

[GitHub] storm pull request: STORM-996: netty-unit-tests/test-batch demonst...

GitHub user knusbaum opened a pull request: https://github.com/apache/storm/pull/711 STORM-996: netty-unit-tests/test-batch demonstrates out-of-order delivery Netty calls notifyInterestChanged which causes a race condition in flushMessages. You can merge this pull request into a Gi

[jira] [Updated] (STORM-996) netty-unit-tests/test-batch demonstrates out-of-order delivery

[ https://issues.apache.org/jira/browse/STORM-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Dagit updated STORM-996: -- Assignee: Kyle Nusbaum (was: Derek Dagit) > netty-unit-tests/test-batch demonstrates out-of-order delive

[jira] [Updated] (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:all-tabpanel ] Sriharsha Chintalapani updated STORM-1024: -- Assignee: Arun Mahadevan (was: Priyank Shah) > log4j changes leaving ${sys:stor

[GitHub] storm pull request: [STORM-886] Automatic Back Pressure (ABP)

Github user zhuoliu commented on a diff in the pull request: https://github.com/apache/storm/pull/700#discussion_r38438290 --- Diff: storm-core/src/clj/backtype/storm/daemon/worker.clj --- @@ -114,12 +114,38 @@ (fast-list-iter [[task tuple :as pair] tuple-batch] (.se

[jira] [Commented] (STORM-886) Automatic Back Pressure

[ https://issues.apache.org/jira/browse/STORM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725635#comment-14725635 ] ASF GitHub Bot commented on STORM-886: -- Github user zhuoliu commented on a diff in the

[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&focusedCommentId=14725630#comment-14725630 ] ASF GitHub Bot commented on STORM-969: -- Github user arunmahadevan commented on the pul

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

Github user arunmahadevan commented on the pull request: https://github.com/apache/storm/pull/664#issuecomment-136775368 +1 overall the patch looks good once the [comment] (https://github.com/apache/storm/pull/664#commitcomment-13003095) is addressed --- If your project is set up for

[GitHub] storm pull request: [STORM-886] Automatic Back Pressure (ABP)

Github user redsanket commented on a diff in the pull request: https://github.com/apache/storm/pull/700#discussion_r38437006 --- Diff: storm-core/src/clj/backtype/storm/daemon/worker.clj --- @@ -114,12 +114,38 @@ (fast-list-iter [[task tuple :as pair] tuple-batch] (.

[jira] [Commented] (STORM-886) Automatic Back Pressure

[ https://issues.apache.org/jira/browse/STORM-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725620#comment-14725620 ] ASF GitHub Bot commented on STORM-886: -- Github user redsanket commented on a diff in t

[GitHub] storm pull request: [storm-elasticsearch] Expose TransportClient c...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/707 --- 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 and wishes so, or if the feature is enabl

[GitHub] storm pull request: [storm-elasticsearch] Expose TransportClient c...

Github user alexpanov commented on the pull request: https://github.com/apache/storm/pull/707#issuecomment-136747407 @HeartSaVioR No problem, it's my pleasure. --- 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

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

Sriharsha Chintalapani created STORM-1024: - Summary: log4j changes leaving ${sys:storm.log.dir} under STORM_HOME dir Key: STORM-1024 URL: https://issues.apache.org/jira/browse/STORM-1024 Proje

[jira] [Commented] (STORM-1013) [storm-elasticsearch] Expose TransportClient configuration Map to EsConfig

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

[GitHub] storm pull request: [storm-elasticsearch] Expose TransportClient c...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/707#issuecomment-136731639 Thanks @alexpanov, I merged with master. But github mirror is a bit behind. I'll mark STORM-1013 as resolved when mirror catches up. --- If your project is set u

[jira] [Commented] (STORM-828) HdfsBolt takes a lot of configuration, need good defaults

[ https://issues.apache.org/jira/browse/STORM-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725399#comment-14725399 ] Sanket Reddy commented on STORM-828: I could make it more specific by making the delimi

[jira] [Commented] (STORM-440) NimbusClient throws NPE if Config.STORM_THRIFT_TRANSPORT_PLUGIN is not set

[ https://issues.apache.org/jira/browse/STORM-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725394#comment-14725394 ] Sanket Reddy commented on STORM-440: Im sorry, there seems to be close and resolve. I w

[GitHub] storm pull request: [storm-elasticsearch] Expose TransportClient c...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/707#issuecomment-136722939 Great. +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

[jira] [Updated] (STORM-1023) Nimbus server hogs 100% CPU and clients are stuck

[ https://issues.apache.org/jira/browse/STORM-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frantz Mazoyer updated STORM-1023: -- Labels: (was: newbie) Description: Testing environment is Storm 0.9.5 / thrift java 0

[jira] [Created] (STORM-1023) Nimbus server hogs 100% CPU and clients are stuck

Frantz Mazoyer created STORM-1023: - Summary: Nimbus server hogs 100% CPU and clients are stuck Key: STORM-1023 URL: https://issues.apache.org/jira/browse/STORM-1023 Project: Apache Storm Iss