Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/21038
Thanks @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".
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
