Hi all,

This may be an old question, but what is the correct way of using Singleton
pattern with Storm?

Currently we have a topology with around 200 bolts, of which around 50 read
and write data from/to Cassandra. Each of these 50 bolts creates a new
Cassandra session, which to my understanding of Cassandra is not great. We
have tried solving this issue with several implementations of singletons:
lazy static, eager static and enum. All of these implementations have
worked in dev environment running on single server, but have fallen apart
on QA environment which has two supervisor hosts. I'm new to Storm so I
have no idea if we are missing something crucial or obvious.

Thanks & Regards,
Denis Sevosteenko

Reply via email to