GitHub user hsun-cnnxty opened a pull request:
https://github.com/apache/storm/pull/728
[STORM-1038] Upgraded netty to 4.x
Upgraded the netty transportation layer to 4.x to take advantage of its
memory management efficiency.
You can merge this pull request into a Git repository by
[
https://issues.apache.org/jira/browse/STORM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736242#comment-14736242
]
ASF GitHub Bot commented on STORM-1038:
---
GitHub user hsun-cnnxty opened a pull reque
Hang Sun created STORM-1038:
---
Summary: Upgrade netty transport from 3.x to 4.x
Key: STORM-1038
URL: https://issues.apache.org/jira/browse/STORM-1038
Project: Apache Storm
Issue Type: Dependency upg
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736226#comment-14736226
]
ASF GitHub Bot commented on STORM-1015:
---
Github user hsun-cnnxty commented on the pu
Github user hsun-cnnxty commented on the pull request:
https://github.com/apache/storm/pull/705#issuecomment-138791147
I assume you are referring to the json format of the spout "state" stored
in ZK? The "state" will be saved using the exact same json format in Kafka's
internal topic
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736155#comment-14736155
]
ASF GitHub Bot commented on STORM-1015:
---
Github user sweetest commented on the pull
Github user sweetest commented on the pull request:
https://github.com/apache/storm/pull/705#issuecomment-13874
how will this change affect the format of spout's offset message in
zookeeper?
---
If your project is set up for it, you can reply to this email and have your
reply app
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736150#comment-14736150
]
ASF GitHub Bot commented on STORM-1015:
---
Github user hsun-cnnxty commented on the pu
Github user hsun-cnnxty commented on the pull request:
https://github.com/apache/storm/pull/705#issuecomment-138777397
Thanks for the advices. Will get them fixed as soon as I get some time.
---
If your project is set up for it, you can reply to this email and have your
reply appear o
[
https://issues.apache.org/jira/browse/STORM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736001#comment-14736001
]
ASF GitHub Bot commented on STORM-1037:
---
Github user harshach commented on the pull
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/726#issuecomment-138754304
+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 harshach commented on the pull request:
https://github.com/apache/storm/pull/727#issuecomment-138754092
+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 harshach commented on the pull request:
https://github.com/apache/storm/pull/561#issuecomment-138753701
@sumitchawla sorry about the long delay in reviewing this. overall this
looks good to me I am going to run some tests on this patch.
@ptgoetz @revans2 @HeartSaVioR @P
[
https://issues.apache.org/jira/browse/STORM-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735999#comment-14735999
]
ASF GitHub Bot commented on STORM-817:
--
Github user harshach commented on the pull req
Github user wangli1426 commented on the pull request:
https://github.com/apache/storm/pull/716#issuecomment-138752669
@HeartSaVioR
Thanks for voting +1.
By the way, in my original design, I didn't use timer to update the
histograms. Instant, the histograms were updated in
[
https://issues.apache.org/jira/browse/STORM-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735996#comment-14735996
]
ASF GitHub Bot commented on STORM-1007:
---
Github user wangli1426 commented on the pul
[
https://issues.apache.org/jira/browse/STORM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735978#comment-14735978
]
ASF GitHub Bot commented on STORM-1005:
---
Github user Renkai closed the pull request
Github user Renkai closed the pull request at:
https://github.com/apache/storm/pull/713
---
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-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735691#comment-14735691
]
ASF GitHub Bot commented on STORM-1007:
---
Github user HeartSaVioR commented on the pu
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/716#issuecomment-138714873
+1
Thanks for providing great feature and benchmark result.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/716#discussion_r38985117
--- Diff: storm-core/src/jvm/backtype/storm/utils/RateTracker.java ---
@@ -0,0 +1,119 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) u
[
https://issues.apache.org/jira/browse/STORM-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735689#comment-14735689
]
ASF GitHub Bot commented on STORM-1007:
---
Github user HeartSaVioR commented on a diff
[
https://issues.apache.org/jira/browse/STORM-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735667#comment-14735667
]
ASF GitHub Bot commented on STORM-1007:
---
Github user HeartSaVioR commented on a diff
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/716#discussion_r38983639
--- Diff: storm-core/src/jvm/backtype/storm/utils/RateTracker.java ---
@@ -0,0 +1,119 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) u
[
https://issues.apache.org/jira/browse/STORM-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735643#comment-14735643
]
ASF GitHub Bot commented on STORM-1011:
---
Github user HeartSaVioR commented on the pu
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/701#issuecomment-138706758
+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
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/723#issuecomment-138704321
+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-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735635#comment-14735635
]
ASF GitHub Bot commented on STORM-1032:
---
Github user HeartSaVioR commented on the pu
[
https://issues.apache.org/jira/browse/STORM-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735600#comment-14735600
]
ASF GitHub Bot commented on STORM-1005:
---
Github user HeartSaVioR commented on the pu
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/722#issuecomment-138698074
+1
@Renkai I think current unit test is enough.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
[
https://issues.apache.org/jira/browse/STORM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735590#comment-14735590
]
Jungtaek Lim commented on STORM-1033:
-
Seems like closer.cgi serves download link agai
[
https://issues.apache.org/jira/browse/STORM-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1033:
Priority: Minor (was: Critical)
> TLP site's download link should be updated to refer closer.lua in
[
https://issues.apache.org/jira/browse/STORM-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735583#comment-14735583
]
Jungtaek Lim commented on STORM-1027:
-
No, Bolt also has overflow buffer. We just need
[
https://issues.apache.org/jira/browse/STORM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-292.
Resolution: Fixed
Assignee: Robert Joseph Evans (was: Abhishek Agarwal)
Fix Version/s
[
https://issues.apache.org/jira/browse/STORM-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735516#comment-14735516
]
Steven Owens edited comment on STORM-614 at 9/8/15 8:12 PM:
gra
[
https://issues.apache.org/jira/browse/STORM-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Owens reopened STORM-614:
gradle in NetBeans could not download clj-time without clojars in repositories
in project build.gradle
My requirement is different from turning on debugging in runtime. I want to
pass the worker.xml in my topology jar. Worker of my topology should pick
up the file in user jar instead of $STORM_HOME/log4j/worker.xml
On Wed, Sep 9, 2015 at 12:06 AM, Bobby Evans
wrote:
> What exactly do you want t
[
https://issues.apache.org/jira/browse/STORM-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735372#comment-14735372
]
ASF GitHub Bot commented on STORM-1015:
---
Github user rmkellogg commented on the pull
Github user rmkellogg commented on the pull request:
https://github.com/apache/storm/pull/705#issuecomment-138665642
A few minor nits:
When providing javadoc on variables/methods, be sure to use the following
syntax:
/**
* Comment text
**/
private String v
What exactly do you want to change?
We have a JIRA https://issues.apache.org/jira/browse/STORM-412 that we have
working code internally for, and should be pushing back to open source soon.
Is that enough of what you want to do, or do you want to configure where the
logs go?
- Bobby
On
[
https://issues.apache.org/jira/browse/STORM-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Kellogg resolved STORM-692.
Resolution: Invalid
Determined that loss of offset storage in Zookeeper was related to not calling
a
[
https://issues.apache.org/jira/browse/STORM-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735209#comment-14735209
]
ASF GitHub Bot commented on STORM-969:
--
Github user arunmahadevan commented on the pul
Github user arunmahadevan commented on the pull request:
https://github.com/apache/storm/pull/664#issuecomment-138639789
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
[
https://issues.apache.org/jira/browse/STORM-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735033#comment-14735033
]
ASF GitHub Bot commented on STORM-943:
--
Github user dossett commented on the pull requ
[
https://issues.apache.org/jira/browse/STORM-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735032#comment-14735032
]
ASF GitHub Bot commented on STORM-969:
--
Github user dossett commented on the pull requ
Github user dossett commented on the pull request:
https://github.com/apache/storm/pull/583#issuecomment-138607384
@revans2 Per your suggestion I did create a JIRA and associate it. Feel
free to merge this at your convenience. Thanks!
---
If your project is set up for it, you can r
Github user dossett commented on the pull request:
https://github.com/apache/storm/pull/664#issuecomment-138607186
@arunmahadevan @harshach Do you have any further comments about my updated
PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
re
Github user shellbj commented on a diff in the pull request:
https://github.com/apache/storm/pull/715#discussion_r38932103
--- Diff: bin/storm.py ---
@@ -103,6 +103,12 @@ def get_config_opts():
sys.exit(1)
def get_jars_full(adir):
+files = []
+if
[
https://issues.apache.org/jira/browse/STORM-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734884#comment-14734884
]
ASF GitHub Bot commented on STORM-1026:
---
Github user shellbj commented on a diff in
In storm a slot is just a port, but in order to be able to use it effectively
you need to treat it like a slot in the old hadoop. At least until
https://issues.apache.org/jira/browse/STORM-893 is released. On our clusters
we typically set it up so there is one slot per core and about 3.5 GB of
[
https://issues.apache.org/jira/browse/STORM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-1017:
--
Assignee: Priyank Shah (was: Sriharsha Chintalapani)
> If ignoreZkOffsets set t
[
https://issues.apache.org/jira/browse/STORM-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734794#comment-14734794
]
Sriharsha Chintalapani commented on STORM-1017:
---
[~RenkaiGe] KafkaSpout uses
Github user Renkai commented on the pull request:
https://github.com/apache/storm/pull/724#issuecomment-138547486
You'd better use English and contribute by this guide
http://storm.apache.org/documentation/Contributing-to-Storm.html
---
If your project is set up for it, you can re
+1 want to know more about this,too
在 15/9/8 15:25，“#ZHANG SHUHAO#” 写入:
>Hi,
>
>When we launch a supervisor node with storm.yaml, we can configure slots port
>(default is 4). Based on my understanding, this is nothing but a threshold to
>prevent too-many concurrent running workers (maximum i
Right now, AFAIK there is a fixed log4j configuration which is shared
across all topologies in a cluster. This is currently encoded in
worker.xml. I was wondering if we can have a way to override this
configuration per topology
Pros
> I could have a custom retention policy for each of my topology.
GitHub user XinzeChi opened a pull request:
https://github.com/apache/storm/pull/727
[STORM-1037] do not remove storm-code in supervisor until kill job
nimbus maybe reschedule topology later
Signed-off-by: Xinze Chi
You can merge this pull request into a Git repository by
[
https://issues.apache.org/jira/browse/STORM-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734552#comment-14734552
]
ASF GitHub Bot commented on STORM-1037:
---
GitHub user XinzeChi opened a pull request:
XinzeChi created STORM-1037:
---
Summary: do not remove storm-code in supervisor until kill job
Key: STORM-1037
URL: https://issues.apache.org/jira/browse/STORM-1037
Project: Apache Storm
Issue Type:
XinzeChi created STORM-1036:
---
Summary: do not remove storm-code in supervisor until kill job
Key: STORM-1036
URL: https://issues.apache.org/jira/browse/STORM-1036
Project: Apache Storm
Issue Type:
XinzeChi created STORM-1035:
---
Summary: do not remove storm-code in supervisor until kill job
Key: STORM-1035
URL: https://issues.apache.org/jira/browse/STORM-1035
Project: Apache Storm
Issue Type:
[
https://issues.apache.org/jira/browse/STORM-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734393#comment-14734393
]
Abhishek Agarwal commented on STORM-1027:
-
I assume that you are referring to STOR
[
https://issues.apache.org/jira/browse/STORM-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Agarwal reassigned STORM-1027:
---
Assignee: Abhishek Agarwal
> Topology may hang because metric-tick function is a bloc
[
https://issues.apache.org/jira/browse/STORM-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Agarwal reassigned STORM-292:
--
Assignee: Abhishek Agarwal
> emit blocks the publishing bolt if disrupter queue is full
Hi,
When we launch a supervisor node with storm.yaml, we can configure slots port
(default is 4). Based on my understanding, this is nothing but a threshold to
prevent too-many concurrent running workers (maximum is 4 by default then).
However, my experiment results shows that number of slots d
64 matches
Mail list logo
