Github user knusbaum commented on the pull request:
https://github.com/apache/storm/pull/236#issuecomment-72969470
@nathanmarz, @revans2, @d2r
Do we still want this? If so I'll upmerge and fix all the problems:
1. easy, I'll take care of this.
2. I can also monitor the batch-transfer-queue.
3. This one's trickier. It depends on what you mean by "thread-safe." They
are certainly thread-safe in the sense that nothing will get corrupted. I've
read the disruptor code for 2.10.1, and only reads are ever done by the
additional code. They may be off by an amount if a write is done during, but it
won't corrupt any values.
---
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.
---
