Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/19789
Yeah, subscribepattern could definitely be an issue.
As far as unit testing, have you tried anything along the lines of setting
the cache size artificially low and then introducing new topicpartitions?
On Mon, Nov 20, 2017 at 11:43 AM, Daroo <notificati...@github.com> wrote:
> I see you point, but it's kind of difficult to size it properly when you
> use SubscribePattern (i.e. dynamic number of topics/partitions) consumer
> strategy
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/19789#issuecomment-345772062>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAGABxwDwzBPfH-VH8BoU8g3BjyMj_JQks5s4bpYgaJpZM4QklrV>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
