[KAFKA-387] Add support for honouring MongoDB read preference in change stream after promotion Created: 30/Sep/23 Updated: 02/Oct/23 |
|
| Status: | Investigating |
| Project: | Kafka Connector |
| Component/s: | Source |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Unknown |
| Reporter: | Bob Tiernay | Assignee: | Robert Walters |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When change streams are in a `getMore` loop against an open cursor, they do not respect the read preference defined in the connection if there is a promotion event that invalidates the primary / secondary status of the server it is streaming from. This feature is to leverage SDAM and monitor the server's status, and if the read preference is invalidated, close the cursor noting the resume token, re-open against a read preference compatible node, and resume streaming from the resume token. This feature is key in order to keep load off the primary node. |
| Comments |
| Comment by PM Bot [ 30/Sep/23 ] |
|
Hi rtiernay@gmail.com, thank you for reporting this issue! The team will look into it and get back to you soon. |