Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/21038
I can't think of a valid reason to create a configuration to allow it. It
just fundamentally doesn't make sense to run different apps with the same
group id.
Trying to catch and rethrow the exception with more information might make
sense.
On Wed, Apr 11, 2018, 20:05 Saisai Shao <notificati...@github.com> wrote:
> Thanks @koeninger <https://github.com/koeninger> for your comments. I
> think your suggestion is valid, the log here is just pasted from JIRA, but
> we also got the same issue from customer's report.
>
> Here in the PR description, I mentioned that using two apps with same
> group id to mimic this issue. But I'm not sure the real use case from our
> customer, maybe in their scenario such usage is valid.
>
> So I'm wondering if we can add a configuration to control whether it
> should be fail or just warning. Also I think exception/warning log should
> be improved to directly tell user about consumer rebalance issue, rather
> than throwing from Kafka as "no current assignment for partition xxx".
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/21038#issuecomment-380641782>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAGAB-6ISk53Qsrh0Hwopdc8uk-F4ZFrks5tnqhEgaJpZM4TPftQ>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
