Event loop duplicate
lsbardel opened this issue · 0 comments
lsbardel commented
- pulsar version: 2.0
Description
Setting the EventLoopPolicy can cause a dead lock if some async components already have initialised they loop (a use case in the lux
was found where a data store had already its own event loop).
This is a critical bug which may lead to an important design decision to not allow long lasting components to hold a reference to the event loop.
Proposal
- hold a reference to the event loop only if explicitly passed to it?