cockroachdb / cockroachdb/sequelize-cockroachdb

concurrent transactions with write followed by reading fails due to timeout

Open
#66 5 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
55
Forks
18
PR merge metrics
No merged PRs in 30d

Description

Relevant test: https://github.com/sequelize/sequelize/blob/main/test/integration/cls.test.js#L120-L137

Context:
Doing a write in a transaction (and not committing) that uses one table and a read from the same table in a separate transaction causes timeout.

This is expected behaviour in Cockroach as serializable transactions cause writes to hold exclusive locks.

We do not expect the behaviour from the test above to succeed or Cockroach to change in a way such that the above test will succeed. We'll likely have to document that this is expected behaviour for sequelize-cockroachdb if we can't find a workaround.

Relevant issue: https://github.com/cockroachdb/cockroach/issues/61269

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.