Hi All,

I posted this question in user's mailing list as well. I am posting here
because I
am not sure whether this is a bug in trident or not.

I am playing with a trident topology having a single spout. The topology
simply
counts the words emitted and stores it in redis [1]. I run this topology on
4 worker
nodes.

I deliberately shutdown one worker node and restart it and monitor the batch
replay (I am logging the transaction id of the batches being emitted).

I see the last batch which didn't complete before the shutdown gets
re-emitted
again and again without succeeding. Any idea why this happens?
(I created the spout implementing `ITridentSpout`.)

If I don't crash the server, the topology runs normally and finishes.

Thanks in advance for any explanation about this.

[1] http://redis.io/

Regards,
Thilina

Reply via email to