CASSSIDECAR-451: Sidecar CDC should resolve real keyspace replication factors from the driver#343
CASSSIDECAR-451: Sidecar CDC should resolve real keyspace replication factors from the driver#343Klose6 wants to merge 3 commits into
Conversation
jberragan
left a comment
There was a problem hiding this comment.
Thanks for adding, not sure why this was neglected in the Sidecar implementation.
yeah, we found this during the cdc e2e testing. |
|
@jberragan @bbotella could you take a look when you got a chance? thanks in advance! |
|
Hi!! Really sorry for the delay!! I've been out traveling for a while, and just made it back. I'll be taking a look this week. |
np, thank you so much! |
@jyothsnakonisa Sure I’ll wait for your PR to be merged first since it already contains my change. After that, I can rebase/update my branch accordingly if needed(but overall looks my changes is not needed after your PR). Thanks for coordinating this. |
|
@Klose6 I merged my PR to fix CDC issues yesterday, can u rebase and see if you need to add anything? |
I just did a rebase and overall looks good, no need to add extra things, your PR uses the SchemaSupplier for the CDC enabled tables and my PR uses the InstanceMetadataFetcher, both will work but SchemaSupplier is simpler, I think we can just close this PR, thank you! |
Currently the analytics library uses ReplicationFactorSupplier.DEFAULT (SimpleStrategy/RF=1), which causes peer discovery to find only one replica per token range, it is better to add the support to resolve real keyspace replication factors from the driver.