[MXS-3807] Using the binlog router as the source for KafkaCDC router is unreliable Created: 2021-10-07 Updated: 2022-12-09 Resolved: 2021-12-09 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cdc |
| Affects Version/s: | 6.1.4 |
| Fix Version/s: | 6.2.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Kyle Joiner (Inactive) | Assignee: | Niclas Antti |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-145, MXS-SPRINT-146 |
| Description |
|
When using the KafkaCDC router pointed to a Server in Maxscale using MariaDB monitor errors occur when starting the Kafka router on a verified GTID location: Kafka: FindCoordinator response error: Group authorization failed. |
| Comments |
| Comment by markus makela [ 2021-10-07 ] |
|
Does this occur if authentication is not enabled? The error is from Kafka which means it has nothing to do with the binlogrouter and suggests a problem with how the Kafka cluster authenticates MaxScale. |
| Comment by Kyle Joiner (Inactive) [ 2021-10-11 ] |
|
When pointing the Kafka router directly at the Galera cluster nodes there is no error so it does not seem to be an authentication problem. |
| Comment by Naresh Chandra [ 2021-11-03 ] |
|
When pointing the Kafka router directly at the Galera cluster nodes there was no error but with same credentials if we pointing the Kafka router from Binlog router then its not working. CASE1: When we use only KafkaCDC without Binlog router
CASE2: When we use only KafkaCDC with Binlog router
Both the CASE1 and CASE2, Kafka broker is common, so the issue is not with Kafkabroker or KafkaCDC router, issue is between KafkaCDC and Binlog router. |
| Comment by Naresh Chandra [ 2021-11-19 ] |
|
Can we fix this issue in the next release? |