Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/268#issuecomment-59317470
Hi Ted,
You are trying to achive three things:
1. When a worker is down, we don't want the upstream worker to fail in a
chaining manner.
2. When some connection is unavailable, we don't want other connection to
wait for this connection.
3. When the message come too fast, we need to strategy to handle it.
Whether drop it, or cache it. Seems your timecachemap is used for this purpose.
We better split these to small patches, and solve 1 and 2 in this patch. I
will work with you and contribute on this pull request.
---
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.
---
