Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/870#issuecomment-155434976
@danielschonfeld Yes we needs something like that. We are using a single
timer thread for all of the system metrics to be able to do something similar,
but there is no possibility of them blocking. It is all atomic memory
operations when the timer goes off so having a single thread shared between
them is not a big deal.
With the disruptor queue if the queue is full the thread will block trying
to flush the messages. This could be a very long period of time. This is why
I went with the ScheduledThreadPoolExecutor. The problem here is that it has
no way to spin up new threads under load or tear them down when idle. I could
spend some time and build my own, but this seems to solve a lot, but not all of
the load problem.
I am going to try and spend some time to create something that can do all
of that, but it is not something I can put together in a few hours and expect
it to work.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
