Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2293
@kevinconaway
I think I'm late on commenting to JIRA issue. Performance hit is not
avoidable in this case.
As I commented earlier, if we have consensus that the use case is minor
(initiating poll to user@/dev@, or any other approaches), we can consider about
not supporting thread-safety on output collector for the benefit of major use
cases. We could even make grouper code thread-unsafe and gain more performance
improvement if we're OK to drop it.
If we drop thread-safety of output collector, even wrapping output
collector will not work if you have the case - N tasks : 1 executor, because
output collector instance is created per each task but executor send queue is
shared.
---
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.
---
