Answered my own question, after a deeper search in google, the point is
Storm-on-YARN, is designed for use in the batch layer (over a HDFS
cluster), so the Storm-to-HDFS connector has sense in this batch layer. On
the other hand, the Storm in the speed layer has no sense the use of HDFS
connector.
We also had the same issue. We also need to delete supervisor and worker
directories in order to restart the supervisor processes after these processes
die.
Is this known bug? Is there any cleaner way to restart?
Thanks ,
Saurabh.
- Original Message -
From: Ryan Chan
At: Friday,
This has already been reported: https://issues.apache.org/jira/browse/STORM-307.
The workaround we’ve implemented is, in our storm init scripts, we always
delete the {storm.home}/supervisor and {storm.home}/workers directories before
starting the supervisor.
From: Saurabh Agarwal (BLOOMBERG/
#6 - 5 pts
On Thu, May 15, 2014 at 6:28 PM, P. Taylor Goetz ptgo...@gmail.com wrote:
This is a call to vote on selecting the top 3 Storm logos from the 11
entries received. This is the first of two rounds of voting. In the first
round the top 3 entries will be selected to move onto the
#10: 3pts
#6: 2pts
From: jose farfan [mailto:josef...@gmail.com]
Sent: 21 May 2014 11:38
To: user@storm.incubator.apache.org
Subject: Re: [VOTE] Storm Logo Contest - Round 1
#6 - 5 pts
On Thu, May 15, 2014 at 6:28 PM, P. Taylor Goetz
ptgo...@gmail.commailto:ptgo...@gmail.com wrote:
This is a
Are you sure that you're not passing a null value in your tuple?
On May 21, 2014 7:25 AM, Irek Khasyanov qua...@gmail.com wrote:
Hello.
I have strange problem with by topology, sometimes everything crashed with
exception:
java.lang.RuntimeException: java.lang.NullPointerException
at
Are you using the OutputCollector to emit in a separate thread (i.e. Outside of
the execute() method.)?
As the wiki states, this will cause the problem you are seeing?
-Taylor
On May 21, 2014, at 7:24 AM, Irek Khasyanov qua...@gmail.com wrote:
Hello.
I have strange problem with by
I want to set a *tick tuple* and I always do that in
getComponentConfiguration() without problems.
But in this case for a variety of reasons I need do it during *prepare
method* and I don't know how to set tick tuple at this point
(getComponentConfiguration has already called).
Is it possible
You can also synchronize access to the OutputCollector so that only 1
thread is using it at a time.
On Wed, May 21, 2014 at 12:39 PM, Irek Khasyanov qua...@gmail.com wrote:
Hm, yes, firs bolt emitting from different thread, I did't realize that
this will be problem. Thanks! I'll try to change
storm-kafka is now part of the Storm project. When 0.9.2 is released (shortly)
it will include the Kafka spout (for Kafka 0.8.x).
- Taylor
On May 21, 2014, at 4:32 PM, Marco zentrop...@yahoo.co.uk wrote:
Hi,
I'm having some troubles understanding how to boostrap a Kafka + Storm
project.
https://github.com/apache/incubator-storm/blob/master/external/storm-kafka/pom.xml#L34
And 2.10 not backward compatible with 2.9... that's why scala
applications/libraries is cross compiled with multiple scala version.
(that's why SBT will handle this natively, but I think in apache sbt is not
If you build yourself, you can do the following:
mvn install -DscalaVersion=2.10.3 -DkafkaArtifact=kafka_2.10
- Taylor
On May 21, 2014, at 5:32 PM, János Háber janos.ha...@finesolution.hu wrote:
https://github.com/apache/incubator-storm/blob/master/external/storm-kafka/pom.xml#L34
And 2.10
Thanks.
- Original Message -
From: Simon Cooper
At: Wednesday, May 21, 2014 06:16
This has already been reported:
https://issues.apache.org/jira/browse/STORM-307.
The workaround we’ve implemented is, in our storm init scripts, we always
delete the
what does the $mastercoord-bg0 represent ? It seems to have much less work
that my bolt spout. Also how can I set the parallelism of this master spout
?
when my other bolts are emitting and acking millions of tuples, this master
spout only emits/acks a couple dozen.
Also currently something in
Dear Taylor, I love your work, but:
- I don't want to build myself
- Dependent libraries (like tormenta-kafka) need a cross compiled version
of storm-kafka, without this they need to clone the project, change the
group id, handle every changes by hand, and publish to central repository.
- I need
Hi,
Is there a recommended supervisor or daemon tool for Storm nodes? I'm
using Supervisor for Storm and Zookeeper.
I heard some concern in using Supervisor, but I haven't researched into the
matter.
Any comments on this?
Thanks,
Connie
We use upstart. Supervisord would also work. Just anything to keep an eye
on it and restart it if it dies (a very rare occurrence).
Michael Rose (@Xorlev https://twitter.com/xorlev)
Senior Platform Engineer, FullContact http://www.fullcontact.com/
mich...@fullcontact.com
On Wed, May 21, 2014 at
János,
I sense and appreciate your frustration.
The initial goal with bringing the storm-kafka project under the Apache Storm
project umbrella is to provide a definitive source for the code and eliminate
fragmentation, which has been an issue in the past. This is a good first step
for many
Exactly what Michael said...
Any good process monitoring tool will work.
The only issue I've had with supervisord is not with the software, but rather
the name conflict with the Storm supervisor process -- it can confuse the hell
out of some people.
-Taylor
On May 21, 2014, at 9:29 PM,
I always like hearing the question: What happened to the supervisor
supervisor?!
-Cody
On Wed, May 21, 2014 at 7:48 PM, P. Taylor Goetz ptgo...@gmail.com wrote:
Exactly what Michael said...
Any good process monitoring tool will work.
The only issue I've had with supervisord is not with
Hi,
We submit storm jar to storm cluster using commandline, as 'storm jar'.
But how could it be done with the java client.
Thanks and Regards,
Komal Thombare
=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential
21 matches
Mail list logo
