storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julien Nioche <lists.digitalpeb...@gmail.com>
Subject Re: Is SpoutOutputCollector thread-safe?
Date Wed, 17 Feb 2016 15:00:03 GMT
Is that true of all OutputCollectors or just SpoutOutputCollector? Is
http://storm.apache.org/documentation/Troubleshooting.html#nullpointerexception-from-deep-inside-storm
<http://storm.apache.org/documentation/Troubleshooting.html> still an issue
with 0.10.0 and above?

Couldn't find any reference to this in
http://storm.apache.org/2015/11/05/storm0100-released.html

Thanks

Julien


On 16 February 2016 at 17:59, Abhishek Agarwal <abhishcool@gmail.com> wrote:

> It is not thread safe in 0.9.4.  It is thread safe in later versions
> (0.10.0 onwards)
>
> Excuse typos
> On Feb 16, 2016 11:01 PM, "Evgeniy Khyst" <evgeniy.khist@gmail.com> wrote:
>
>> Hello!
>>
>> I'm currently using Apache Storm 0.9.4 and have question about
>> thread-safety of *SpoutOutputCollector*. Is it safe to call *emit *method
>> from different threads?
>> In documentation (http://storm.apache.org/documentation/Concepts.html)
>> it is said that *OutputCollector *is not thread-safe, and all emits,
>> acks, and fails must happen on the same thread.
>> But in Javadoc (
>> https://storm.apache.org/apidocs/backtype/storm/spout/ISpout.html) it is
>> said that *SpoutOutputCollector* is thread-safe and should be saved as
>> an instance variable of this spout object.
>> Please, provide a little bit more details about thread-safety of
>> *SpoutOutputCollector* and validity of calling *emit *method from
>> different threads.
>>
>> Thanks.
>>
>> Best regards,
>> Evgeniy
>>
>


-- 

*Open Source Solutions for Text Engineering*

http://www.digitalpebble.com
http://digitalpebble.blogspot.com/
#digitalpebble <http://twitter.com/digitalpebble>

Mime
View raw message