GitHub user itaifrenkel opened a pull request:
https://github.com/apache/storm/pull/685
ShellBolt should treat ack and fail as heartbeat
Python queues up requests, and it can handle many requests before reaching
the __heartbeat signal, so the shellbolt must treat ack/fail as
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/685#issuecomment-131084050
@itaifrenkel
Thanks for the work, but it was already addressed.
https://issues.apache.org/jira/browse/STORM-742
Could you review
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696914#comment-14696914
]
ASF GitHub Bot commented on STORM-742:
--
Github user HeartSaVioR commented on the pull
Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/644#issuecomment-130991133
@d2r Thanks for the review, incorporated your feedback.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696560#comment-14696560
]
ASF GitHub Bot commented on STORM-837:
--
Github user arunmahadevan commented on the
Sorry for this abrupt question. I should have learnt about Trident before
asking.
On Aug 14, 2015, at 14:59, 王立 wangli1...@gmail.com wrote:
Hi all,
I have a question regarding to the fault tolerance mechanism in storm.
I believe the key idea behind fault tolerance mechanism is the
[
https://issues.apache.org/jira/browse/STORM-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696542#comment-14696542
]
Samuel Hsieh commented on STORM-167:
Hi Parth Brahmbhatt,
Any validation support
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696986#comment-14696986
]
ASF GitHub Bot commented on STORM-742:
--
Github user revans2 commented on the pull
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-742.
---
Resolution: Fixed
Fix Version/s: 0.10.0
Thanks [~kabhwan],
I merged this into
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-131105849
@HeartSaVioR Sorry I have been way behind on looking at pull requests,
among other things. It looks good to me +1. Do you want to pull this back
into 0.10 too?
---
Hi.
First of all, you may want to read Guaranteeing Message Processing
http://storm.apache.org/documentation/Guaranteeing-message-processing.html to
see how it works.
In short, Spout and Bolt should also be stateless since worker could be
killed and restarted. (at any time)
Also data source for
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-131107320
OK I'll check it into both branches.
---
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
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696994#comment-14696994
]
ASF GitHub Bot commented on STORM-742:
--
Github user HeartSaVioR commented on the pull
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696997#comment-14696997
]
ASF GitHub Bot commented on STORM-742:
--
Github user revans2 commented on the pull
To truly guarantee exact recovery your code needs to be stateless, but in most
cases with a lambda architecture, which is really what storm was initially
designed for, you can deal with keeping some or all of the data only in memory.
For example if I am doing a rolling window aggregation and I
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/497
---
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
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697015#comment-14697015
]
ASF GitHub Bot commented on STORM-742:
--
Github user asfgit closed the pull request at:
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-131107204
@revans2
Thanks for the review. :)
Yes, it would be better to include it to next release, since several users
already reported such situation.
---
If your
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-131131538
@revans2 Thanks for merging!
---
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
[
https://issues.apache.org/jira/browse/STORM-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697149#comment-14697149
]
ASF GitHub Bot commented on STORM-988:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/681#issuecomment-131133006
+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
[
https://issues.apache.org/jira/browse/STORM-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-988.
Resolution: Fixed
Fix Version/s: 0.11.0
supervisor.slots.ports should not allow duplicate
[
https://issues.apache.org/jira/browse/STORM-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697164#comment-14697164
]
Jungtaek Lim commented on STORM-988:
Thanks [~caofangkun], I merged into master.
[
https://issues.apache.org/jira/browse/STORM-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697163#comment-14697163
]
ASF GitHub Bot commented on STORM-988:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697147#comment-14697147
]
ASF GitHub Bot commented on STORM-742:
--
Github user HeartSaVioR commented on the pull
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/675#issuecomment-131150732
@HeartSaVioR can you take a look at my pull request again
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697244#comment-14697244
]
P. Taylor Goetz commented on STORM-742:
---
[~revans2] [~kabhwan] Thanks for taking care
[
https://issues.apache.org/jira/browse/STORM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697233#comment-14697233
]
ASF GitHub Bot commented on STORM-949:
--
Github user jerrypeng commented on the pull
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/656
---
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
[
https://issues.apache.org/jira/browse/STORM-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-938:
-
Assignee: Aaron Dossett (was: Priyank Shah)
storm-hive add a time interval to
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/687#issuecomment-131230746
Closing in preference to https://github.com/apache/storm/pull/688 (fixed
branch name)
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user d2r opened a pull request:
https://github.com/apache/storm/pull/688
[YSTORM-993] include uptimeSeconds as JSON integer field
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/d2r/storm storm-993-ui-uptime-seconds
Github user d2r closed the pull request at:
https://github.com/apache/storm/pull/687
---
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 opened a pull request:
https://github.com/apache/storm/pull/687
[YSTORM-933] include uptimeSeconds as JSON integer field
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/d2r/storm storm-933-ui-uptime-seconds
GitHub user priyank5485 opened a pull request:
https://github.com/apache/storm/pull/686
STORM-965: Fix excessive logging
The reason for this pull request is that when a non-secure client tries to
connect to nimbus host in a secure cluster, an exception was being thrown and a
null
Derek Dagit created STORM-993:
-
Summary: Add uptime in seconds to UI REST API
Key: STORM-993
URL: https://issues.apache.org/jira/browse/STORM-993
Project: Apache Storm
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697423#comment-14697423
]
ASF GitHub Bot commented on STORM-837:
--
Github user revans2 commented on the pull
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697448#comment-14697448
]
ASF GitHub Bot commented on STORM-837:
--
Github user ptgoetz commented on the pull
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697331#comment-14697331
]
ASF GitHub Bot commented on STORM-837:
--
Github user d2r commented on a diff in the
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/644#discussion_r37093803
--- Diff:
external/storm-hdfs/src/main/java/org/apache/storm/hdfs/trident/HdfsState.java
---
@@ -136,44 +174,98 @@ public void run() {
private
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/644#issuecomment-131192881
+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-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697465#comment-14697465
]
ASF GitHub Bot commented on STORM-837:
--
Github user asfgit closed the pull request at:
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/684#discussion_r37092739
--- Diff: storm-core/src/jvm/backtype/storm/Config.java ---
@@ -145,6 +145,12 @@
public static final String STORM_LOCAL_DIR = storm.local.dir;
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697346#comment-14697346
]
ASF GitHub Bot commented on STORM-837:
--
Github user d2r commented on the pull request:
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/644#issuecomment-131175103
Thanks @arunmahadevan
+1 It seems fine to me, and the new tests pass for me. The remaining
comment on refactoring is minor, so I am ok merging it.
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/644#issuecomment-131188419
Still +1 looks good.
---
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
[
https://issues.apache.org/jira/browse/STORM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697483#comment-14697483
]
ASF GitHub Bot commented on STORM-976:
--
Github user YvonneIronberg commented on a diff
Github user YvonneIronberg commented on a diff in the pull request:
https://github.com/apache/storm/pull/684#discussion_r37103291
--- Diff: storm-core/src/jvm/backtype/storm/Config.java ---
@@ -145,6 +145,12 @@
public static final String STORM_LOCAL_DIR = storm.local.dir;
[
https://issues.apache.org/jira/browse/STORM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697938#comment-14697938
]
ASF GitHub Bot commented on STORM-976:
--
Github user YvonneIronberg commented on the
Github user YvonneIronberg commented on the pull request:
https://github.com/apache/storm/pull/684#issuecomment-131265858
Thanks for the suggestions. Addressed them in the latest commit.
logback.xml is converted to an equivalent log4j2.xml according to their docs.
*
[
https://issues.apache.org/jira/browse/STORM-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697988#comment-14697988
]
ASF GitHub Bot commented on STORM-975:
--
Github user HeartSaVioR commented on a diff in
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/684#discussion_r37120357
--- Diff: bin/storm-config.cmd ---
@@ -83,10 +83,10 @@ if not defined STORM_LOG_DIR (
)
@rem
-@rem retrieve storm.logback.conf.dir from conf
Github user ddebree commented on the pull request:
https://github.com/apache/storm/pull/682#issuecomment-131239318
I have updated the class to rather use the RotatingMap as a member
variable. It comes out a lot more similar to the original.
---
If your project is set up for it, you
[
https://issues.apache.org/jira/browse/STORM-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697752#comment-14697752
]
ASF GitHub Bot commented on STORM-990:
--
Github user ddebree commented on the pull
[
https://issues.apache.org/jira/browse/STORM-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697754#comment-14697754
]
Frantz Mazoyer commented on STORM-994:
--
In Utils.java method downloadFromMaster leaks
[
https://issues.apache.org/jira/browse/STORM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697765#comment-14697765
]
ASF GitHub Bot commented on STORM-976:
--
Github user d2r commented on a diff in the
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/684#issuecomment-131242201
I looked through the branch and found some I hadn't noticed before:
*
[
https://issues.apache.org/jira/browse/STORM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697780#comment-14697780
]
ASF GitHub Bot commented on STORM-976:
--
Github user d2r commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697965#comment-14697965
]
ASF GitHub Bot commented on STORM-976:
--
Github user ptgoetz commented on a diff in the
Github user ptgoetz commented on a diff in the pull request:
https://github.com/apache/storm/pull/684#discussion_r37129089
--- Diff: bin/storm-config.cmd ---
@@ -83,10 +83,10 @@ if not defined STORM_LOG_DIR (
)
@rem
-@rem retrieve storm.logback.conf.dir from
Frantz Mazoyer created STORM-994:
Summary: Connection leak between nimbus and supervisors
Key: STORM-994
URL: https://issues.apache.org/jira/browse/STORM-994
Project: Apache Storm
Issue
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/666#discussion_r37130096
--- Diff:
examples/storm-starter/src/jvm/storm/starter/trident/TridentKafkaWordCount.java
---
@@ -0,0 +1,208 @@
+package storm.starter.trident;
[
https://issues.apache.org/jira/browse/STORM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14697987#comment-14697987
]
ASF GitHub Bot commented on STORM-949:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/675#issuecomment-131272147
@jerrypeng
I'm with @knusbaum. PR is a bit different from JIRA title, and I'm also
more in favor of putting time/date.
How about gathering consensus about
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/666#issuecomment-131276460
Other things look fine.
---
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
[
https://issues.apache.org/jira/browse/STORM-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698030#comment-14698030
]
ASF GitHub Bot commented on STORM-975:
--
Github user HeartSaVioR commented on the pull
Github user arunmahadevan commented on a diff in the pull request:
https://github.com/apache/storm/pull/666#discussion_r37133083
--- Diff:
examples/storm-starter/src/jvm/storm/starter/trident/TridentKafkaWordCount.java
---
@@ -0,0 +1,208 @@
+package storm.starter.trident;
[
https://issues.apache.org/jira/browse/STORM-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698100#comment-14698100
]
ASF GitHub Bot commented on STORM-975:
--
Github user arunmahadevan commented on a diff
[
https://issues.apache.org/jira/browse/STORM-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14696961#comment-14696961
]
ASF GitHub Bot commented on STORM-742:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/497#issuecomment-131097025
@ptgoetz @revans2 @harshach
Multi-lang users need this PR to overcome heartbeat design constraint.
Could you take a look? Thanks in advance!
---
If your
[
https://issues.apache.org/jira/browse/STORM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim reopened STORM-992:
It will be closed when PR is merged to Apache repo. Reopening.
A bug in the timer.clj might cause
71 matches
Mail list logo
