This is a question about Storm 0.82.

What are the implications of running without any acking? I realise that
reliability is then not guaranteed, but without ackers I understand that
the "topology.max.spout.pending" doesn't apply. But the Storm docs state
that it is highly-desirable to set this value to prevent "queue explosion".

https://github.com/nathanmarz/storm/wiki/Running-topologies-on-a-production-cluster

Yet the docs also say that by disabling acking, one can improve performance.

https://github.com/nathanmarz/storm/wiki/Guaranteeing-message-processing

So, is running without ackers something to be considered for production
systems? And if so, what throttles the Storm system from flooding the
topology with too many tuples (which I presumes eats up memory, heap,
whatever)?

Thanks,

Philip

Reply via email to