Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/21038
The log in the jira looks like it's from a consumer rebalance, i.e. more
than one driver consumer was running with the same group id.
Isn't the underlying problem here that the user is creating multiple
streams with the same group id, despite what the documentation says? The log
even says s/he copy-pasted the documentation group id "group
use_a_separate_group_id_for_each_stream"
I don't think we should silently "fix" that. As a user, I wouldn't expect
app A to suddenly start processing only half of the partitions just because
entirely different app B started with the (misconfigured) same group id.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]