Use PostgreSQL advisory locks to enforce only one subscription instance #98
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.
PostgreSQL's
pg_try_advisory_lock
function is used to acquire a session lock on the subscription id to guarantee that only once uniquely named subscription instance can run.Each subscription now has its own connection. When the subscription process goes down, the connection will terminate and its lock will be released.
This supports running EventStore on multiple independent nodes without requiring them to form a cluster, but still guarantees subscriptions run once.