On 27/03/2016 05:03, Xin Wang wrote:
RAS:
http://storm.apache.org/releases/2.0.0-SNAPSHOT/Resource_Aware_Scheduler_overview.html
CGroup:
http://storm.apache.org/releases/2.0.0-SNAPSHOT/cgroups_in_storm.html
Thanks for that. I hadn't twigged that these features were in
new/unreleased code.
B
On 24/03/2016 17:04, Brian Candler wrote:
On 24/03/2016 17:02, Brian Candler wrote:
At the bottom of the storm.apache.org home page there is a black
section labelled "First Look", and under that is a link to
"Tutorial", which links to
http://storm.apache.org/releases/c
On 24/03/2016 17:02, Brian Candler wrote:
At the bottom of the storm.apache.org home page there is a black
section labelled "First Look", and under that is a link to "Tutorial",
which links to
http://storm.apache.org/releases/current/tutorial.html
- but that gives a 404
I can see the docs have been reorganised.
At the bottom of the storm.apache.org home page there is a black section
labelled "First Look", and under that is a link to "Tutorial", which
links to
http://storm.apache.org/releases/current/tutorial.html
- but that gives a 404 error.
It's not availa
On 23/03/2016 03:37, Xin Wang wrote:
I have provided an implementation `MessagePackSerializer` for
improving muti-lang performance. (PR:
https://github.com/apache/storm/pull/1136). You can take a look at
this. It's not merged yet.
Thanks.
Another question: the default config file talks abou
On 23/03/2016 08:45, Matthew Lowe wrote:
The cpu is not under a lot of strain for the spout
On each VM, have you tried running "top" and then hitting "1"? This will
show you the CPU utilisation per core. If on any VM you see one core at
100% then you need to increase parallelism by more threads
Just a minor note: at
http://storm.apache.org/documentation/Multilang-protocol.html
there is a broken link:
" documented
[here](Storm-multi-language-protocol-(versions-0.7.0-and-below).html)"
It looks like the embedded parentheses are confusing markdown.
The page itself at
http://storm.apache
On 22/03/2016 20:13, Matthew Lowe wrote:
The maxTuplePending is set to 35 (During testing we found 3 ackers and 35 max
pending was “good")
Have you tried increasing this now you have built your spout-bolt-bolt
topology?
When testing with only the Spout (no bolts) I was emitting about 70,000 pe
I have two servers, and I
run a topology with 2 workers, 4 tasks of A and 4 tasks of B. Will I get
4A on one server and 4B on the other, or 2A+2B on both, or something else?
Many thanks,
Brian Candler.
