Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/630#issuecomment-121150967
@errordaiwa @amontalenti
1000ms timeout makes sense to me.
Actually 100ms timeout also makes sense to me, but I'd like to know our
opinions about load aware.
[
https://issues.apache.org/jira/browse/STORM-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625967#comment-14625967
]
ASF GitHub Bot commented on STORM-935:
--
Github user HeartSaVioR commented on the pull
Github user ellull commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-121180650
We are also facing this issue, so +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 n
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626112#comment-14626112
]
ASF GitHub Bot commented on STORM-643:
--
Github user ellull commented on the pull reque
Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-121188995
In branch 0.10.0, the failed tuple has been managered by
ExponentialBackoffMsgRetryManager, should we also make this change to 0.10.0
---
If your project is set up for i
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626140#comment-14626140
]
ASF GitHub Bot commented on STORM-643:
--
Github user tedxia commented on the pull reque
Github user mvalleavila commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-121189676
We are reproducing the issue too, +1
Thx!
---
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-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626147#comment-14626147
]
ASF GitHub Bot commented on STORM-643:
--
Github user mvalleavila commented on the pull
Github user 2new commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-121215831
Faced this issue with 0.9.5. Is this patch going to be merged in the short
term?
---
If your project is set up for it, you can reply to this email and have your
reply appea
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626260#comment-14626260
]
ASF GitHub Bot commented on STORM-643:
--
Github user 2new commented on the pull request
[
https://issues.apache.org/jira/browse/STORM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shyam Rajendran updated STORM-932:
--
Assignee: (was: Shyam Rajendran)
> Trident RichSpoutBatchExecutor emit batch
> -
[
https://issues.apache.org/jira/browse/STORM-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626377#comment-14626377
]
Shyam Rajendran commented on STORM-899:
---
STORM-919 is being worked on as a related JI
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/593#issuecomment-121281726
Thanks @HeartSaVioR .We can have this merged to master whenever we feel
appropriate.
---
If your project is set up for it, you can reply to this email and have your
[
https://issues.apache.org/jira/browse/STORM-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626476#comment-14626476
]
ASF GitHub Bot commented on STORM-67:
-
Github user bourneagain commented on the pull req
Hi,
I want to know why setup-default-uncaught-exception-handler just deal
with the OOM error, since the fast fail is the philosophy of Storm design.
When a thread crashes in one Storm process, the process will lost its
functionality mostly.
Why not exit the whole process when an uncaught excepti
[
https://issues.apache.org/jira/browse/STORM-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626548#comment-14626548
]
Sriharsha Chintalapani commented on STORM-615:
--
[~revans2] do you have any sug
[
https://issues.apache.org/jira/browse/STORM-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626595#comment-14626595
]
Robert Joseph Evans commented on STORM-615:
---
Using policy files would work to pre
Reza Farivar created STORM-937:
--
Summary: StormBoundedExponentialBackoffRetry too noisy, lower log
level
Key: STORM-937
URL: https://issues.apache.org/jira/browse/STORM-937
Project: Apache Storm
GitHub user rfarivar opened a pull request:
https://github.com/apache/storm/pull/631
[STORM-937] Changing the log level from info to debug
This is to reduce the noisiness of supervisor logs.
You can merge this pull request into a Git repository by running:
$ git pull https://g
[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reza Farivar updated STORM-937:
---
Comment: was deleted
(was: Pull Request https://github.com/apache/storm/pull/631)
> StormBoundedExpone
[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626644#comment-14626644
]
Reza Farivar commented on STORM-937:
Pull Request https://github.com/apache/storm/pull/
[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626643#comment-14626643
]
ASF GitHub Bot commented on STORM-937:
--
GitHub user rfarivar opened a pull request:
Hi Chuanlei,
The setup-default-uncaught-exception-handler fails fast in both OOM and other
uncaught Exceptions. The difference in treatment is Runtime.halt vs
Runtime.exist (Other uncaught exceptions handled here).
If the OOM Error, we shutdown JVM using Runtime.halt. In other cases, we call
R
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/631#discussion_r34597439
--- Diff:
storm-core/src/jvm/backtype/storm/utils/StormBoundedExponentialBackoffRetry.java
---
@@ -44,7 +44,7 @@ public StormBoundedExponentialBackoffRetry(int
b
[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626756#comment-14626756
]
ASF GitHub Bot commented on STORM-937:
--
Github user d2r commented on a diff in the pul
Github user knusbaum commented on a diff in the pull request:
https://github.com/apache/storm/pull/617#discussion_r34599960
--- Diff: storm-core/src/jvm/backtype/storm/messaging/netty/Client.java ---
@@ -59,20 +59,16 @@
* - Connecting and reconnecting are performed asynchronou
Github user eshioji commented on a diff in the pull request:
https://github.com/apache/storm/pull/617#discussion_r34602607
--- Diff: storm-core/src/jvm/backtype/storm/messaging/netty/Client.java ---
@@ -59,20 +59,16 @@
* - Connecting and reconnecting are performed asynchronous
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/617#discussion_r34603263
--- Diff: storm-core/src/jvm/backtype/storm/messaging/netty/Client.java ---
@@ -59,20 +59,16 @@
* - Connecting and reconnecting are performed asynchronous
Github user knusbaum commented on a diff in the pull request:
https://github.com/apache/storm/pull/617#discussion_r34603678
--- Diff: storm-core/src/jvm/backtype/storm/messaging/netty/Client.java ---
@@ -59,20 +59,16 @@
* - Connecting and reconnecting are performed asynchronou
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/617#issuecomment-121338762
+1 the code compiles and the tests all pass
---
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 projec
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/616#issuecomment-121338740
+1 the code compiles and the tests all pass
---
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 projec
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/568#issuecomment-121338790
+1 the code compiles and the tests all pass
---
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 projec
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626850#comment-14626850
]
ASF GitHub Bot commented on STORM-763:
--
Github user revans2 commented on the pull requ
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/616#issuecomment-121343845
+1 tests pass, examples run.
---
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
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/568#issuecomment-121344016
+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
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/616
---
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 user asfgit closed the pull request at:
https://github.com/apache/storm/pull/566
---
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
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626879#comment-14626879
]
ASF GitHub Bot commented on STORM-763:
--
Github user knusbaum commented on the pull req
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/617
---
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
[
https://issues.apache.org/jira/browse/STORM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626880#comment-14626880
]
ASF GitHub Bot commented on STORM-839:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626883#comment-14626883
]
ASF GitHub Bot commented on STORM-839:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/568
---
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
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626884#comment-14626884
]
ASF GitHub Bot commented on STORM-763:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626881#comment-14626881
]
ASF GitHub Bot commented on STORM-839:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated STORM-763:
--
Assignee: Enno Shioji
> nimbus reassigned worker A to another machine, but other worker's
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-763.
---
Resolution: Fixed
Fix Version/s: 0.9.6
Thanks [~eshioji],
I merged this into ma
[
https://issues.apache.org/jira/browse/STORM-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-839.
---
Resolution: Fixed
Assignee: Enno Shioji
Fix Version/s: 0.9.6
Thanks [~e
[
https://issues.apache.org/jira/browse/STORM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626944#comment-14626944
]
Enno Shioji commented on STORM-763:
---
[~revans2] Yay, thank you! I'll ping [~ptgoetz] on t
Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/631#issuecomment-121365995
+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
Hi Taylor,
@Bobby recommended I talk to you about a potential 0.9.6 release to fix
STORM-763/839. The fixes are already merged to master, 0.10.x and 0.9.x.
In a nutshell, they fix the following symptoms -- but the catch is that
these symptoms only surface when connections between bolts are lost
[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626970#comment-14626970
]
ASF GitHub Bot commented on STORM-937:
--
Github user knusbaum commented on the pull req
In addition to Enno's mail, I'd like to know we'd like to maintain three
version lines (currently 0.9.x, 0.10.x, 0.11.x) continuously, or it is just
a period of transition.
I'm maintaining three version lines (bugfix, next minor, next major - with
respecting semver) from other project, and sometim
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/631#issuecomment-121400695
+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
[
https://issues.apache.org/jira/browse/STORM-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627098#comment-14627098
]
ASF GitHub Bot commented on STORM-937:
--
Github user HeartSaVioR commented on the pull
Github user nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/631#issuecomment-121403303
+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-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627113#comment-14627113
]
ASF GitHub Bot commented on STORM-937:
--
Github user nathanmarz commented on the pull r
Ok, understand. Thank you very much.
And sorry for the halfheartedness while reading the code!
Thank you again!
2015-07-15 1:17 GMT+08:00 Kishorkumar Patil :
> Hi Chuanlei,
> The setup-default-uncaught-exception-handler fails fast in both OOM and
> other uncaught Exceptions. The difference in t
My opinion:
In terms of supporting the 0.9.x release line, I think that’s critical, at the
very least until 0.10.0 stable is released. More likely for some time
thereafter for those who don’t want to (or can’t) upgrade.
Updates to the the 0.9.x line should be limited to bug fixes.
I’d like to
[
https://issues.apache.org/jira/browse/STORM-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-615:
---
Fix Version/s: (was: 0.10.0)
> Add REST API to upload topology
> ---
>
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-121473131
@miguno Sorry I took so long to respond. Like @tpiscitell already
explained, this problem are not solved by STORM-586 and STORM-511.
---
If your project is set up for i
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627456#comment-14627456
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense commented on the pull requ
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-121473865
@HeartSaVioR @tedxia This PR is for branch 0.9.x. 0.9.x is very different
from 0.10.x and master, so when we go the cherry-pick there are a lot of
conflicts. In branch 0.
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627459#comment-14627459
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense commented on the pull requ
To be more clear, I'm fine with maintaining three minor version lines
while it is period of transition.
Just a thing I'm curious is we'd like to maintain two stable version lines
continuously (with one unstable).
For now, I'm fine with releasing 0.9.6 with backporting bugfixes which are
already c
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-121484496
@dashengju Could you share your patch (limiting queue size) if you don't
mind?
---
If your project is set up for it, you can reply to this email and have your
reply
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627496#comment-14627496
]
ASF GitHub Bot commented on STORM-742:
--
Github user HeartSaVioR commented on the pull
[
https://issues.apache.org/jira/browse/STORM-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shyam Rajendran reassigned STORM-918:
-
Assignee: Shyam Rajendran
> Storm CLI could validate arguments/print usage
> -
[
https://issues.apache.org/jira/browse/STORM-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shyam Rajendran reassigned STORM-918:
-
Assignee: Shyam Rajendran
> Storm CLI could validate arguments/print usage
> -
[
https://issues.apache.org/jira/browse/STORM-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shyam Rajendran updated STORM-918:
--
Assignee: (was: Shyam Rajendran)
> Storm CLI could validate arguments/print usage
> -
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan reassigned STORM-837:
Assignee: Arun Mahadevan
> HdfsState ignores commits
> -
>
>
[
https://issues.apache.org/jira/browse/STORM-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani closed STORM-869.
Resolution: Invalid
> kafka spout cannot fetch message if log size is above fetchSize
[
https://issues.apache.org/jira/browse/STORM-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627501#comment-14627501
]
Sriharsha Chintalapani commented on STORM-869:
--
[~sweetest_sj] this is not a i
GitHub user bourneagain opened a pull request:
https://github.com/apache/storm/pull/632
STORM-918 Storm CLI could validate arguments/print usage
Storm commands that mandate proper args to be passed would now throw
the function's doc string as help rather than exiting out with err
[
https://issues.apache.org/jira/browse/STORM-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627573#comment-14627573
]
ASF GitHub Bot commented on STORM-918:
--
GitHub user bourneagain opened a pull request:
GitHub user lethalbrains opened a pull request:
https://github.com/apache/storm/pull/633
Added closing quotes(") in the documentation
Closing quotes was missing in a code sample. Fixed that.
You can merge this pull request into a Git repository by running:
$ git pull https://g
75 matches
Mail list logo
