Github user tgravescs commented on the issue:
https://github.com/apache/spark/pull/18388
sorry I didn't get a chance to review this. Started but kept getting
distracted by other higher priority things. I think we should expand the
description of the config to say what happens when the limit is hit. Since its
not using real flow control a user might set this thinking nothing bad will
happen, but its dropping connections so could cause failures if the retries
don't work.
I'll file a separate jira for that.
Also what was the issue with implementing the actual flow control part?
Was it just adding a queueing type mechanism? We should file a separate jira
so we can add that later.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
