Hi Alexei,
Thanks. I can't use autocommit because it degrades
performance. My spout emits tuples at the rate of 4000/second. I need to
add them to DB after some processing. So I commit in batches in bolt, But
my spout stops emitting tuples for sometime. In this case the uncommitted
data will be committed only when the bolt recieves another tuple. So,
during this time gap there are many uncommitted data. So is there a way to
make commit periodically?. Is creating a separate thread for this in the
prepare() method of bolt a good option?
On 20 March 2014 20:52, Alexei Osipov <[email protected]> wrote:
> If you don't care about choosing moment to commit your data the why you
> just don't use "autocommit" mode?
>
>
> On 3/20/2014 3:06 PM, Manthosh Kumar T wrote:
>
> I just want to call Connection.commit() for adding data to DB. Now I call
> commit in the bolt after some threshold. But when the spout stops emitting
> for some time, the uncomitted data are not yet added to DB. So if calling a
> function when a topology is killed isn't possible, is it possible to have a
> Time out in the bolt, so that I can commit data when no Tuple is received
> for some time?
>
>
> On 20 March 2014 16:39, Manthosh Kumar T <[email protected]> wrote:
>
>> Hi All,
>> When running a topology in cluster, is it possible to call a
>> function when in a bolt when a Topology is killed?. Or will
>> cluster.shutdown() work in the same way as in local mode when running in
>> Cluster mode?, if it is so, is it possible to call a function in bolt when
>> the cluster is shutdown?
>>
>> --
>> Cheers,
>> Manthosh Kumar. T
>>
>>
>
>
> --
> Cheers,
> Manthosh Kumar. T
>
>
>
--
Cheers,
Manthosh Kumar. T
