[jira] [Commented] (STORM-706) Clarify IntelliJ instructions for example running.

[ https://issues.apache.org/jira/browse/STORM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366651#comment-14366651 ] P. Taylor Goetz commented on STORM-706: --- I think we can handle this better through bo

Re: IntelliJ setup of source.

This is a big annoyance of mine with IntelliJ… One way to address it is to define a Maven property for the `provided` scope, default it to `provided`, then override it in a profile that you enable in IntelliJ. It’s not pretty, but it saves you from constantly commenting/uncommenting the `scope

[jira] [Updated] (STORM-701) provide eclipse plugin for creating/monitoring/debugging user topology

[ https://issues.apache.org/jira/browse/STORM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caofangkun updated STORM-701: - Summary: provide eclipse plugin for creating/monitoring/debugging user topology (was: provide eclipse plu

[jira] [Updated] (STORM-701) provide eclipse plugin for monitoring/debugging user topology

[ https://issues.apache.org/jira/browse/STORM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caofangkun updated STORM-701: - Attachment: New Storm Topology Project-03.jpg New Storm Topology Project-02.jpg

[jira] [Updated] (STORM-701) provide eclipse plugin for monitoring/debugging user topology

[ https://issues.apache.org/jira/browse/STORM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caofangkun updated STORM-701: - Description: provide eclipse plugin for debugging user topology, submit topologies and monitor their exe

[jira] [Updated] (STORM-701) provide eclipse plugin for monitoring/debugging user topology

[ https://issues.apache.org/jira/browse/STORM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] caofangkun updated STORM-701: - Description: provide eclipse plugin for debugging user topology, submit topologies and monitor their exe

[jira] [Commented] (STORM-503) Short disruptor queue wait time leads to high CPU usage when idle

[ https://issues.apache.org/jira/browse/STORM-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366259#comment-14366259 ] Eric commented on STORM-503: will be fix in next versions https://issues.apache.org/jira/browse

[jira] [Commented] (STORM-503) Short disruptor queue wait time leads to high CPU usage when idle

[ https://issues.apache.org/jira/browse/STORM-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366206#comment-14366206 ] Stan Miroshnikov commented on STORM-503: Seeing the same with Storm 0.9.3: 88% sun

[jira] [Created] (STORM-709) Received unexpected tuple

Matthew Gaulin created STORM-709: Summary: Received unexpected tuple Key: STORM-709 URL: https://issues.apache.org/jira/browse/STORM-709 Project: Apache Storm Issue Type: Bug Affects Vers

[jira] [Commented] (STORM-561) Add ability to create topologies dynamically

[ https://issues.apache.org/jira/browse/STORM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366125#comment-14366125 ] P. Taylor Goetz commented on STORM-561: --- FWIW, based on feedback from a number of sou

[jira] [Commented] (STORM-702) Apache Exhibitor support

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

[GitHub] storm pull request: STORM-702: Exhibitor support

Github user atdixon commented on the pull request: https://github.com/apache/storm/pull/432#issuecomment-82580384 @harshach implemented your suggestions, thank you. The *storm* configuration I used to test (w/ single zk node, too) is in the first comment of this thread.

[jira] [Commented] (STORM-681) Auto insert license header with genthrift.sh

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

[GitHub] storm pull request: [STORM-681] Auto insert license header with ge...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/436 --- 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-681] Auto insert license header with ge...

Github user knusbaum commented on the pull request: https://github.com/apache/storm/pull/436#issuecomment-82484008 +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 and

[jira] [Commented] (STORM-681) Auto insert license header with genthrift.sh

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

[jira] [Commented] (STORM-702) Apache Exhibitor support

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

[GitHub] storm pull request: STORM-702: Exhibitor support

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/432#discussion_r26591966 --- Diff: storm-core/src/jvm/backtype/storm/utils/Utils.java --- @@ -363,9 +384,30 @@ public static CuratorFramework newCurator(Map conf, List servers, Object

[jira] [Commented] (STORM-702) Apache Exhibitor support

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

[GitHub] storm pull request: STORM-702: Exhibitor support

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/432#issuecomment-82468584 @atdixon minor nit pick above. I am trying to test this by running exhibitor, can you provide a sample config for running exhibitor with single host zookeeper. I a

[GitHub] storm pull request: STORM-702: Exhibitor support

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/432#discussion_r26588593 --- Diff: storm-core/src/jvm/backtype/storm/utils/Utils.java --- @@ -363,9 +384,30 @@ public static CuratorFramework newCurator(Map conf, List servers, Object

[jira] [Commented] (STORM-702) Apache Exhibitor support

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

[jira] [Commented] (STORM-541) Build produces maven warnings

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

[jira] [Resolved] (STORM-541) Build produces maven warnings

[ https://issues.apache.org/jira/browse/STORM-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-541. --- Resolution: Fixed Fix Version/s: 0.10.0 Thanks [~caofangkun], I merged this int

[jira] [Commented] (STORM-541) Build produces maven warnings

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

[GitHub] storm pull request: STORM-541:Clean duplicate dependences in poms

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/422 --- 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-541:Clean duplicate dependences in poms

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/422#issuecomment-82420774 +1 it cleans up the warnings, the pull request title is a bit confusing, but it works. --- If your project is set up for it, you can reply to this email and have your re

[jira] [Commented] (STORM-702) Apache Exhibitor support

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

[GitHub] storm pull request: STORM-702: Exhibitor support

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/432#issuecomment-82411216 The code looks good to me and there is a JIRA for it. I am +1, but @harshach I'll wait to hear from you before I check anything in. --- If your project is set up for it,

[GitHub] storm pull request: STORM-532:Supervisor should restart worker imm...

Github user revans2 commented on a diff in the pull request: https://github.com/apache/storm/pull/296#discussion_r26581260 --- Diff: storm-core/src/clj/backtype/storm/util.clj --- @@ -392,6 +392,15 @@ (.addArgument command a)) (.execute (DefaultExecutor.) command

[jira] [Commented] (STORM-532) Supervisor should restart worker immediately, if the worker process does not exist any more

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

[jira] [Commented] (STORM-638) UI should show up process-id of the Worker to which an Executor is assigned

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

[GitHub] storm pull request: STORM-638:UI should show up process-id of the ...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/396#issuecomment-82399938 Sorry it is not the code generation after all. Although the comment in the generated code with a 0.7.0 is off putting, and I would prefer it to be generated with 0.9.2.

[GitHub] storm pull request: STORM-638:UI should show up process-id of the ...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/396#issuecomment-82397663 @harshach, If you are running the UI without a filter I would not consider that secure. There is other more damaging information exposed on the UI already. Also what is

[jira] [Commented] (STORM-638) UI should show up process-id of the Worker to which an Executor is assigned

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

[jira] [Resolved] (STORM-689) SimpleACLAuthorizer should provide a way to restrict who can submit topologies

[ https://issues.apache.org/jira/browse/STORM-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-689. --- Resolution: Fixed Fix Version/s: 0.10.0 Thanks [~sriharsha], I merged this into

[GitHub] storm pull request: STORM-689. SimpleACLAuthorizer should provide ...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/445#issuecomment-82392832 +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 and w

[jira] [Commented] (STORM-689) SimpleACLAuthorizer should provide a way to restrict who can submit topologies

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

[GitHub] storm pull request: STORM-689. SimpleACLAuthorizer should provide ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/445 --- 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-689) SimpleACLAuthorizer should provide a way to restrict who can submit topologies

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

[jira] [Commented] (STORM-681) Auto insert license header with genthrift.sh

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

[GitHub] storm pull request: [STORM-681] Auto insert license header with ge...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/436#issuecomment-82376057 +1 looks good to me. --- 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 fea

[jira] [Commented] (STORM-329) Fix cascading Storm failure by improving reconnection strategy and buffering messages

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

[GitHub] storm pull request: STORM-329 : buffer message in client and recon...

Github user tedxia closed the pull request at: https://github.com/apache/storm/pull/268 --- 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-329) Fix cascading Storm failure by improving reconnection strategy and buffering messages

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

[GitHub] storm pull request: STORM-329 : buffer message in client and recon...

Github user miguno commented on the pull request: https://github.com/apache/storm/pull/268#issuecomment-82217610 @clockfly We may also want to check why we don't have the permissions to close this PR ourselves. --- If your project is set up for it, you can reply to this email and hav

[jira] [Commented] (STORM-329) Fix cascading Storm failure by improving reconnection strategy and buffering messages

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

[GitHub] storm pull request: STORM-329 : buffer message in client and recon...

Github user clockfly commented on the pull request: https://github.com/apache/storm/pull/268#issuecomment-82196521 I will ask Ted to close this. --- 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 hav

[jira] [Updated] (STORM-707) Client (Netty): improve logging to help troubleshooting connection woes

[ https://issues.apache.org/jira/browse/STORM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Noll updated STORM-707: --- Fix Version/s: 0.10.0 > Client (Netty): improve logging to help troubleshooting connection woes > -

[jira] [Closed] (STORM-707) Client (Netty): improve logging to help troubleshooting connection woes

[ https://issues.apache.org/jira/browse/STORM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Noll closed STORM-707. -- Resolution: Fixed > Client (Netty): improve logging to help troubleshooting connection woes > ---

[jira] [Commented] (STORM-707) Client (Netty): improve logging to help troubleshooting connection woes

[ https://issues.apache.org/jira/browse/STORM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364746#comment-14364746 ] Michael Noll commented on STORM-707: I needed to reopen the ticket so that JIRA would a

[jira] [Commented] (STORM-707) Client (Netty): improve logging to help troubleshooting connection woes

[ https://issues.apache.org/jira/browse/STORM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364744#comment-14364744 ] Michael Noll commented on STORM-707: Thanks a lot, Kyle! > Client (Netty): improve log

[jira] [Reopened] (STORM-707) Client (Netty): improve logging to help troubleshooting connection woes

[ https://issues.apache.org/jira/browse/STORM-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Noll reopened STORM-707: > Client (Netty): improve logging to help troubleshooting connection woes > -