image-2020-09-18-13-03-12-805.png
[MXS-3199] KafkaCDC read stream data too slow Created: 2020-09-18 Updated: 2020-11-05 Resolved: 2020-11-05 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cdc |
| Affects Version/s: | 2.5.3 |
| Fix Version/s: | 2.5.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Wilson Lau | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
image-2020-09-18-13-03-12-805.png
|
| Sprint: | MXS-SPRINT-118 |
| Description |
|
tail -f KafkaCDC log , found its GTID increased slowly,It lags far behind master's GTID |
| Comments |
| Comment by markus makela [ 2020-09-18 ] |
|
Does the difference in the latest GTID processed by kafkacdc and the one in the master keep growing? That is, does the number of transactions that kafkacdc lags behind increase? |
| Comment by Wilson Lau [ 2020-09-19 ] |
|
Yes, kafkacdc :2020-09-19 13:56:56 info : XID for GTID '8-800-120616741': 92697707 lags= 120944626 - 120616741 is so large |
