Re: Details about the Storm Scheduler

Also your bolt may be pending on a call to an external resource (e.g. DB) and thus not consuming much CPU despite a relatively high usage. On Wed, Aug 24, 2016 at 10:09 AM, Bobby Evans wrote: > But CGroups is restricting the actual CPU usage and scheduling is taking

Re: Multiple query processing in apache storm

Obviously you cannot change what is in your jar file but if the bolt is already compiled you can try flux to change how your topology is linked. http://storm.apache.org/documentation/flux.html On Wed, Nov 25, 2015 at 5:03 AM, Renya nath N wrote: > Hi Ankur, > > Thank you

Re: How to limit the spout not to generate the tuple in case of failure of downstream tuple?

Don't fail the tuple, just drop it (don't emit). Btw the user list is better for this type of question. On Sep 12, 2015 7:43 AM, "Sachin Pasalkar" wrote: > Hi, > > As per my knowledge storm is follow "at least one” way , which means it > will make sure at least

Re: Storm for LHCb at CERN

Forgive me if my math is off, but are you pushing 4TB of raw data every second? I can't say whether storm would work or not, but I'm pretty sure that if it does the configuration will look very different from what most people are using. What are your tolerances for data loss? On Jun 23, 2015

Re: Aeolus 0.1 available

You can see more here: https://github.com/apache/storm/tree/master/external On Wed, Jun 3, 2015 at 4:43 PM, Matthias J. Sax mj...@informatik.hu-berlin.de wrote: Thanks for the input. Currently, everything is written in Java (I am not familiar with Clojure -- maybe a good way to get started

Re: Storm message passing

To expound, most fields send locally when their semantics allow it; fields grouping and shuffle grouping will send locally iff the target bolt task is local. Local or shuffle grouping will send locally if possible; otherwise it will use shuffle grouping. On May 8, 2015 11:55 AM, Bobby Evans

Re: Hooking into the internal messaging system

It is preferable to emit on a separate stream that the prior bolt subscribes to. That way you can conditionally emit on the second stream and avoid infinite loops. On May 7, 2015 5:55 AM, Matthias J. Sax mj...@informatik.hu-berlin.de wrote: Hi, you can user collector.emitDirect(...) to send a

Re: Why is Storm Config not modifiable?

()/prepare() of the abstract class is called, too, and set the default value if the value was neither provided by the user, not by the derived class. Does it make sense how I explained it? -Matthias On 04/23/2015 01:08 PM, Nathan Leung wrote: Config should be set when the topology

Re: Why is Storm Config not modifiable?

Config should be set when the topology is created before it's sent to the nimbus. If you write an option to the map there is no mechanism to propagate the change to the rest of the instances of storm components. On Apr 23, 2015 6:02 AM, Matthias J. Sax mj...@informatik.hu-berlin.de wrote: Hi,

Re: Storm supervisor dying continously

Try cd to your storm local working directory before running supervisor. I'm not sure if they fixed this in later versions but storm supervisor is not very good about setting it's cwd so if you start it from a folder that it cannot write to then it can have problems. If you run with supervision

Re: Fwd: Auto-Scaling

You can't change the number of tasks. Changing the number of tasks will, for example, break any fields grouping you have. On Dec 26, 2014 7:03 PM, Harsha Balasubramanian harsha...@gmail.com wrote: Works Fine Now!! Thanks a ton to everyone who helped me get this going. You folks are incredibly

[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-tabpanelfocusedCommentId=14242040#comment-14242040 ] Nathan Leung commented on STORM-561: Yes, the intent is for Java based topologies

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

[ https://issues.apache.org/jira/browse/STORM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14233550#comment-14233550 ] Nathan Leung edited comment on STORM-561 at 12/3/14 9:29 PM

[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-tabpanelfocusedCommentId=14232597#comment-14232597 ] Nathan Leung commented on STORM-561: Do you mean a serialized representation

[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-tabpanelfocusedCommentId=14230957#comment-14230957 ] Nathan Leung commented on STORM-561: Thanks for the offer. The initial implementation

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

Nathan Leung created STORM-561: -- Summary: Add ability to create topologies dynamically Key: STORM-561 URL: https://issues.apache.org/jira/browse/STORM-561 Project: Apache Storm Issue Type

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

[ https://issues.apache.org/jira/browse/STORM-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Leung updated STORM-561: --- Description: It would be nice if a storm topology could be built dynamically, instead of requiring