Github user koeninger commented on the pull request:
https://github.com/apache/spark/pull/10089#issuecomment-162252793
Sounds good. If you can add that maxRatePerPartition handling this would be
ready to go from my point of view
On Dec 5, 2015 3:59 PM, "Jason White" <[email protected]> wrote:
> This patch solved our skew problem. Below is a 15-minute snapshot of our
> lag earlier this week, showing a single partition getting slowly worse. It
> would get to about 8 million messages behind overnight.
>
> https://monosnap.com/file/VG0rXFZn05bKIIDLFIHOxfNOWKOxy5
>
> And the most recent 24 hour period, after this patch went live on our
> system.
>
> https://monosnap.com/file/DMSzLP8lFKJ0DxHuiWcxZHKqVeJHWL
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/10089#issuecomment-162250749>.
>
---
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]
