Github user Hailei commented on the pull request:
https://github.com/apache/storm/pull/566#issuecomment-106778432
>we can remove the background flushing task and related synchronization
altogether, removing the source of deadlock. We'd simply write and buffer onto
the unbounded buffer of Channel
+1 I agree with you.flushMessages don't check isWritable,So the last
message batch check it is not useful.
Block client thread until there is space (back pressure) is better.It can
snap out of OOM.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
