Github user wuchong commented on a diff in the pull request:
https://github.com/apache/storm/pull/1139#discussion_r53916420
--- Diff: storm-core/src/clj/org/apache/storm/ui/helpers.clj ---
@@ -46,197 +46,3 @@
(fn [req]
--- End diff --
I prefer to leave it here, s
[
https://issues.apache.org/jira/browse/STORM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162761#comment-15162761
]
ASF GitHub Bot commented on STORM-1254:
---
Github user wuchong commented on a diff in
Github user wuchong commented on the pull request:
https://github.com/apache/storm/pull/1139#issuecomment-188174878
@revans2 @abhishekagarwal87 @hustfxj Thanks for your review, I have
addressed all the comments.
Can you have a look again?
---
If your project is set up fo
[
https://issues.apache.org/jira/browse/STORM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162766#comment-15162766
]
ASF GitHub Bot commented on STORM-1254:
---
Github user wuchong commented on the pull r
Github user satishd commented on the pull request:
https://github.com/apache/storm/pull/1144#issuecomment-188196306
+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
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162826#comment-15162826
]
ASF GitHub Bot commented on STORM-1569:
---
Github user satishd commented on the pull r
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1144#issuecomment-188215628
LGTM
---
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
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162872#comment-15162872
]
ASF GitHub Bot commented on STORM-1569:
---
Github user abhishekagarwal87 commented on
GitHub user unsleepy22 opened a pull request:
https://github.com/apache/storm/pull/1147
[STORM-1252] port backtype.storm.stats to java
This PR is quite large but because the defrecords are changed to java
POJO's and they're used in many places, I could not break it into small PR's.
[
https://issues.apache.org/jira/browse/STORM-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162959#comment-15162959
]
ASF GitHub Bot commented on STORM-1252:
---
GitHub user unsleepy22 opened a pull reques
[
https://issues.apache.org/jira/browse/STORM-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162976#comment-15162976
]
ASF GitHub Bot commented on STORM-1570:
---
Github user satishd commented on a diff in
Github user satishd commented on a diff in the pull request:
https://github.com/apache/storm/pull/1141#discussion_r53937034
--- Diff:
external/sql/storm-sql-core/src/jvm/org/apache/storm/sql/compiler/ExprCompiler.java
---
@@ -234,14 +253,20 @@ public String translate(ExprCompiler
Github user satishd commented on the pull request:
https://github.com/apache/storm/pull/1141#issuecomment-188257212
Overall LGTM. +1 once the comment is addressed.
---
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 p
[
https://issues.apache.org/jira/browse/STORM-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162987#comment-15162987
]
ASF GitHub Bot commented on STORM-1570:
---
Github user satishd commented on the pull r
Github user abhishekagarwal87 commented on the pull request:
https://github.com/apache/storm/pull/1147#issuecomment-188278662
PR is indeed quite large. StatsUtil file is too large right now. I think
while we are porting from clojure, we should also shift from functional
paradigm to Ob
[
https://issues.apache.org/jira/browse/STORM-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163079#comment-15163079
]
ASF GitHub Bot commented on STORM-1252:
---
Github user abhishekagarwal87 commented on
Github user unsleepy22 commented on the pull request:
https://github.com/apache/storm/pull/1147#issuecomment-188288595
@abhishekagarwal87 thanks, good point! I'll address your comments~
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
[
https://issues.apache.org/jira/browse/STORM-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163131#comment-15163131
]
ASF GitHub Bot commented on STORM-1252:
---
Github user unsleepy22 commented on the pul
Github user redsanket commented on the pull request:
https://github.com/apache/storm/pull/1054#issuecomment-188304984
+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 a
[
https://issues.apache.org/jira/browse/STORM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163208#comment-15163208
]
ASF GitHub Bot commented on STORM-1254:
---
Github user revans2 commented on the pull r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1139#issuecomment-188311189
+1 looks good. I am still seeing some issues with
```
java.lang.ClassCastException: java.lang.Integer cannot be cast to
java.lang.String
at org.apa
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1081#discussion_r53958459
--- Diff: storm-core/src/jvm/org/apache/storm/cluster/ClusterUtils.java ---
@@ -0,0 +1,261 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF)
[
https://issues.apache.org/jira/browse/STORM-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163225#comment-15163225
]
ASF GitHub Bot commented on STORM-1273:
---
Github user revans2 commented on a diff in
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1081#issuecomment-188328586
+1 looks god to me. Did some manual testing and things look good.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
[
https://issues.apache.org/jira/browse/STORM-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163262#comment-15163262
]
ASF GitHub Bot commented on STORM-1273:
---
Github user revans2 commented on the pull r
[
https://issues.apache.org/jira/browse/STORM-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163265#comment-15163265
]
ASF GitHub Bot commented on STORM-1273:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/STORM-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1273.
Thanks [~Johnbaba],
I merged this into master.
> port backtype.storm.cluster to java
>
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1081
---
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 enab
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1142#discussion_r53965439
--- Diff: storm-core/src/jvm/org/apache/storm/command/CLI.java ---
@@ -238,10 +238,13 @@ public CLIBuilder arg(String name, Parse parse, Assoc
assoc) {
[
https://issues.apache.org/jira/browse/STORM-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163289#comment-15163289
]
ASF GitHub Bot commented on STORM-1572:
---
Github user revans2 commented on a diff in
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1142
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1572.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~Johnbaba],
I merged this int
[
https://issues.apache.org/jira/browse/STORM-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163300#comment-15163300
]
ASF GitHub Bot commented on STORM-1572:
---
Github user asfgit closed the pull request
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1137#issuecomment-188358152
+1 There is a merge conflict in the test. It is minor and I can fix it
when doing the merge.
---
If your project is set up for it, you can reply to this email and have
[
https://issues.apache.org/jira/browse/STORM-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163338#comment-15163338
]
ASF GitHub Bot commented on STORM-1267:
---
Github user revans2 commented on the pull r
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1137
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163372#comment-15163372
]
ASF GitHub Bot commented on STORM-1267:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/STORM-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1265.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~abhishek.agarwal],
I merged
[
https://issues.apache.org/jira/browse/STORM-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1267.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~abhishek.agarwal],
I merged
[
https://issues.apache.org/jira/browse/STORM-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1266.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~abhishek.agarwal],
I merged
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163397#comment-15163397
]
ASF GitHub Bot commented on STORM-1488:
---
Github user revans2 commented on the pull r
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/1129#issuecomment-188375495
+1 the travis failure looks unrelated. Do you have a corresponding fix for
master?
---
If your project is set up for it, you can reply to this email and have your
repl
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1128
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163425#comment-15163425
]
ASF GitHub Bot commented on STORM-1564:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/STORM-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-1564.
Resolution: Fixed
Fix Version/s: 2.0.0
Thanks [~vesense],
I merged this into
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1144#issuecomment-188409357
+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 an
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163541#comment-15163541
]
ASF GitHub Bot commented on STORM-1569:
---
Github user knusbaum commented on the pull
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1144
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163551#comment-15163551
]
ASF GitHub Bot commented on STORM-1569:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/STORM-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163607#comment-15163607
]
ASF GitHub Bot commented on STORM-1571:
---
Github user knusbaum commented on the pull
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1143#issuecomment-188428153
+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 an
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1143
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163700#comment-15163700
]
ASF GitHub Bot commented on STORM-1571:
---
Github user asfgit closed the pull request
I was trying to build the current github version and run it to do some
experiments with the new LoadAwareGrouping, but I am having some problems
running topologies with it. Nimbus and supervisor start and from the UI you
see workers and executors are all allocated, but no tuple is processed. I
trie
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/1129#issuecomment-188432892
> +1 the travis failure looks unrelated. Do you have a corresponding fix
for master?
I do not have a branch ready for master, but I can do that. The only
conflictâ
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163713#comment-15163713
]
ASF GitHub Bot commented on STORM-1488:
---
Github user d2r commented on the pull reque
[
https://issues.apache.org/jira/browse/STORM-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Nusbaum resolved STORM-1571.
-
Resolution: Fixed
Fix Version/s: 2.0.0
> Improvment Kafka Spout Time Metric
> -
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kyle Nusbaum resolved STORM-1569.
-
Resolution: Fixed
Fix Version/s: (was: 1.0.0)
2.0.0
> Allowing users
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1144#issuecomment-188446369
@Parth-Brahmbhatt I merged this and resolved the jira, but the the jira's
resolved version was listed as 1.0. I changed it to 2.0, but do we want to
backport this to 1.
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/1144#issuecomment-188447027
@knusbaum I think we should. WE have see RejectedExecutionException on > 5
different customer clusters. I can backport this if others also agree.
---
If your p
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163761#comment-15163761
]
ASF GitHub Bot commented on STORM-1569:
---
Github user Parth-Brahmbhatt commented on t
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163760#comment-15163760
]
ASF GitHub Bot commented on STORM-1569:
---
Github user knusbaum commented on the pull
Github user d2r closed the pull request at:
https://github.com/apache/storm/pull/1129
---
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 enabled
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/1129#issuecomment-188452484
I saw an epoc date reported on the master branch when no errors had yet
been reported. Defaulting the error time to `0` instead of the empty string
may not be handled corre
the master branch has been going through a lot of changes lately. We are in
the process of merging with the JStorm project and as such we expect there to
be some instability. We are trying to keep the build so it continues to pass
all tests and could be released if need be, but as expected wit
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163799#comment-15163799
]
ASF GitHub Bot commented on STORM-1488:
---
Github user d2r commented on the pull reque
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163800#comment-15163800
]
ASF GitHub Bot commented on STORM-1488:
---
Github user d2r closed the pull request at:
Inside the log for your worker it shows that you have the config
"storm.zookeeper.port" 2000,
Not sure where it came from, but it is in your config.
- Bobby
On Wednesday, February 24, 2016 3:04 PM, Bobby Evans
wrote:
the master branch has been going through a lot of changes lately.
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/1144#issuecomment-188461160
@Parth-Brahmbhatt I'll just go ahead and merge it. It is a very small
change and was already marked for 1.0.
---
If your project is set up for it, you can reply to thi
[
https://issues.apache.org/jira/browse/STORM-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163842#comment-15163842
]
ASF GitHub Bot commented on STORM-1569:
---
Github user knusbaum commented on the pull
GitHub user d2r reopened a pull request:
https://github.com/apache/storm/pull/1129
[STORM-1488] fix broken component error times
Note that the errorTime reported for the component/ path was previously in
milliseconds, but the errorTime reported for the topology/ path was in seconds.
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/1129#issuecomment-188477173
The last error time on the topology page for bolts and spouts is once again
blank when no errors have been reported.
---
If your project is set up for it, you can reply to
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163905#comment-15163905
]
ASF GitHub Bot commented on STORM-1488:
---
GitHub user d2r reopened a pull request:
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163904#comment-15163904
]
ASF GitHub Bot commented on STORM-1488:
---
Github user d2r commented on the pull reque
[
https://issues.apache.org/jira/browse/STORM-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15164481#comment-15164481
]
ASF GitHub Bot commented on STORM-1488:
---
GitHub user d2r opened a pull request:
GitHub user d2r opened a pull request:
https://github.com/apache/storm/pull/1148
[STORM-1488] fix broken component error times
See 1.x-branch PR #1129
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/d2r/storm storm-1488-master-err
Zhuo Liu created STORM-1574:
---
Summary: Better exception handling in backpressure thread, and
remove backpressure dir during topology kill.
Key: STORM-1574
URL: https://issues.apache.org/jira/browse/STORM-1574
GitHub user zhuoliu opened a pull request:
https://github.com/apache/storm/pull/1149
[STORM-1574] Better handle backpressure thread exception & clear dir.
1. Better handle exception.
2. Remove topo dir during kill.
3. Add a unit test.
You can merge this pull request into a G
[
https://issues.apache.org/jira/browse/STORM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15165686#comment-15165686
]
ASF GitHub Bot commented on STORM-1574:
---
GitHub user zhuoliu opened a pull request:
Github user hustfxj commented on the pull request:
https://github.com/apache/storm/pull/1149#issuecomment-188537244
+1 It 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 thi
[
https://issues.apache.org/jira/browse/STORM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166442#comment-15166442
]
ASF GitHub Bot commented on STORM-1574:
---
Github user hustfxj commented on the pull r
Github user hustfxj commented on the pull request:
https://github.com/apache/storm/pull/1149#issuecomment-188543268
Some Tests failed. It prompts tests can't find remove-backpressure!. I
guess it generate some questions when it merge with master.
---
If your project is set up for it
[
https://issues.apache.org/jira/browse/STORM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166478#comment-15166478
]
ASF GitHub Bot commented on STORM-1574:
---
Github user hustfxj commented on the pull r
Github user hustfxj commented on the pull request:
https://github.com/apache/storm/pull/1139#issuecomment-188543700
+1. It looks fairly good. Thank you @wuchong
---
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 pro
[
https://issues.apache.org/jira/browse/STORM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166483#comment-15166483
]
ASF GitHub Bot commented on STORM-1254:
---
Github user hustfxj commented on the pull r
Github user wuchong commented on the pull request:
https://github.com/apache/storm/pull/1139#issuecomment-188546255
@revans2 It's a bug which has been fixed in #1119
---
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
[
https://issues.apache.org/jira/browse/STORM-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166495#comment-15166495
]
ASF GitHub Bot commented on STORM-1254:
---
Github user wuchong commented on the pull r
Github user wuchong commented on a diff in the pull request:
https://github.com/apache/storm/pull/1054#discussion_r54042400
--- Diff: documentation/cgroups_in_storm.md ---
@@ -0,0 +1,65 @@
+# CGroups in Storm
+
+CGroups are used by Storm to limit the resource usage of wo
Github user wuchong commented on a diff in the pull request:
https://github.com/apache/storm/pull/1149#discussion_r54043672
--- Diff:
storm-core/test/jvm/org/apache/storm/utils/WorkerBackpressureThreadTest.java ---
@@ -0,0 +1,68 @@
+/**
+ * Licensed to the Apache Software F
[
https://issues.apache.org/jira/browse/STORM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166643#comment-15166643
]
ASF GitHub Bot commented on STORM-1574:
---
Github user wuchong commented on a diff in
Github user wuchong commented on the pull request:
https://github.com/apache/storm/pull/1149#issuecomment-188582664
+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
[
https://issues.apache.org/jira/browse/STORM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166645#comment-15166645
]
ASF GitHub Bot commented on STORM-1574:
---
Github user wuchong commented on the pull r
Robert,
Running a topology in local mode launches in-process zookeeper which by
default binds to 2000.
https://github.com/apache/storm/blob/master/storm-core/src/jvm/org/apache/storm/zookeeper/Zookeeper.java#L284
@Rodrigo
It is possible that you are killing the local cluster just after you spawn
i
Github user abhishekagarwal87 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1149#discussion_r54049182
--- Diff:
storm-core/src/jvm/org/apache/storm/utils/WorkerBackpressureThread.java ---
@@ -43,17 +48,33 @@ static public void notifyBackpressureCheck
[
https://issues.apache.org/jira/browse/STORM-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166730#comment-15166730
]
ASF GitHub Bot commented on STORM-1574:
---
Github user abhishekagarwal87 commented on
Manu Zhang created STORM-1575:
-
Summary: TwitterSampleSpout throws NPE on close
Key: STORM-1575
URL: https://issues.apache.org/jira/browse/STORM-1575
Project: Apache Storm
Issue Type: Bug
Github user hsun-cnnxty commented on the pull request:
https://github.com/apache/storm/pull/705#issuecomment-188634249
Just did another merge to keep it up to date with master branch. Not sure
what the plan is now. I would be happy to make any changes that can help to
make the final
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166804#comment-15166804
]
ASF GitHub Bot commented on STORM-1015:
---
Github user hsun-cnnxty commented on the pu
[
https://issues.apache.org/jira/browse/STORM-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manu Zhang updated STORM-1575:
--
Affects Version/s: 2.0.0
1.0.0
> TwitterSampleSpout throws NPE on close
> ---
Github user hsun-cnnxty commented on the pull request:
https://github.com/apache/storm/pull/728#issuecomment-188640434
@revans2
Just merged code from master and seems there is performance degradation
with recent changes. I noticed that it not only affects this branch, but al
1 - 100 of 106 matches
Mail list logo
