Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Have all instances correctly respond to REPLICATE command. #7475

Merged
merged 4 commits into from May 13, 2020

Conversation

erikjohnston
Copy link
Member

Before all streams were only written to from master, so only master needed to respond to REPLICATE commands.

Currently all instances can write to the cache invalidation stream, but don't respond to REPLICATE. This is a bug, which can lead to missed rows from cache invalidation stream if an instance is restarted, however all the caches will be empty in that case so its not a problem.

@erikjohnston erikjohnston requested a review from a team May 12, 2020 14:19
@erikjohnston erikjohnston changed the title Have all instance correctly respond to REPLICATE command. Have all instances correctly respond to REPLICATE command. May 12, 2020
@erikjohnston erikjohnston force-pushed the erikj/replication_streams_replicate branch from b14a0d8 to 7836849 Compare May 12, 2020 15:40
Copy link
Contributor

@clokep clokep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this looks fine.

@erikjohnston erikjohnston merged commit 7ee24c5 into develop May 13, 2020
@erikjohnston erikjohnston deleted the erikj/replication_streams_replicate branch May 13, 2020 09:27
phil-flex pushed a commit to phil-flex/synapse that referenced this pull request Jun 16, 2020
…g#7475)

Before all streams were only written to from master, so only master needed to respond to `REPLICATE` commands.

Before all instances wrote to the cache invalidation stream, but didn't respond to `REPLICATE`. This was a bug, which could lead to missed rows from cache invalidation stream if an instance is restarted, however all the caches would be empty in that case so it wasn't a problem.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants