Hi Danijel,
I think your description of the expected behavior of Trident primitives is
correct. I'm interested in understanding the issue you describe, could you
share some code so we can have a look?
Svend
On Thu, Feb 13, 2014 at 9:20 PM, Danijel Schiavuzzi wrote:
> Hi,
>
> I'm experimenting
Hello there -
On my current project we would like to accumulate usage stats for our
spouts. We want total number of tuples transfered and TOTAL NUMBER OF
BYTES TRANSFERED for all the spouts we are running.
It seems like Storm's built in metric's will give
us information on tuples emitted for spo
Yeah, we had to disable issues on nathanmarz/storm in order to get everyone to
start using the Apache infrastructure. An unfortunate side effect of that was
that now links to old github issues return a 404.
All the github issues before the move have been migrated to JIRA now
(https://issues.apa
I have storm0.9 cluster with a nimbus 1 zk and 2 supervisors. I am facing
an issue where nimbus shutsdown with no logging.
below is log from nimbus
2014-02-13 17:27:39 b.s.d.nimbus [INFO] Shutting down master
2014-02-13 17:27:39 o.a.z.ZooKeeper [INFO] Session: 0x144241ecfe50067 closed
2014-02-1
You need to configure the file contents to using netty??storm.yaml
storm.messaging.transport: "backtype.storm.messaging.netty.Context"
storm.messaging.netty.server_worker_threads: 1
storm.messaging.netty.client_worker_threads: 1
storm.messaging.netty.buffer_size: 5242880
storm.
The workers seem to want it.
John L. Magee
US Office: +1(303)974-2860
US Mobile: +1(917)855-7109
http://www.recondotech.com
This message is confidential. It may also be privileged or otherwise protected
by work product immunity or other legal rules. If you have received it by
mist
Thank you for your replies, we removed the garbage collection statements
from the nimbus, supervisor, and worker childoptions and re-ran our
loadtests. The worker death issue appears resolved - thank you again!
Hi,
I'm experimenting a little with a TridentState implementation which
persists state in a RDBMS (SQL) database, and it's working fine using
paralellismHint(1).
However, increasing the TridentState paralellism leads to database
deadlocks, which is unusual since I thought that, by using groupBy()
Including closed issues? E.g. I'm specifically looking for the
following issue, which is gone:
https://github.com/nathanmarz/storm/issues/31#issuecomment-17607249
Thanks,
Marc
I was asked to write a blog on Storm + Cassandra.
Given the number of emails going over the list regarding that pairing, I
figured it wouldn't hurt to share:
http://brianoneill.blogspot.com/2014/02/storm-and-cassandra-three-year.html
(feedback/corrections always welcome)
-brian
--
Brian ONeill
I was going to mention something similar. The stdout/stderr issue is
insidious. Only happens in cluster mode and while it was fixed for some
stdout/stderr pathways, others have not been fixed AFAIK. Taylor has
mentioned one, another is stdout/stderr coming from native code via JNI
(i.e. printf,
Hi,
Your blog post series on Storm Trident is great! There's some really great
info there which is really missing and should IMHO be included in the
official Storm wiki.
Danijel
On Mon, Feb 10, 2014 at 11:07 PM, Svend Vanderveken <
svend.vanderve...@gmail.com> wrote:
>
>
> Hi all,
>
>
> I wrot
12 matches
Mail list logo