Chore/replication replicas #467
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 7dc9a65 The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
rkistner
reviewed
Jan 15, 2026
modules/module-mongodb-storage/src/storage/implementation/MongoSyncRulesLock.ts
Outdated
Show resolved
Hide resolved
rkistner
reviewed
Jan 15, 2026
…powersync-service into chore/replication-replicas
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using two replication pods, the pod waiting for lock will continuously log:
{"code":"PSYNC_S1003","description":"Sync rules: 3 have been locked by another process for replication, expiring at 2026-01-15T08:32:12.270Z.","name":"ServiceError"}The change only allows it to log once, it will then output an info log when it regains the lock.