cockroachdb / cockroachdb/sequelize-cockroachdb
concurrent transactions with write followed by reading fails due to timeout
- Langage dominant
- JavaScript
- Étoiles
- 55
- Forks
- 18
- Métriques de merge des PR
- Aucune PR mergée en 30 j
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
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Évaluation
Cette issue n'a pas encore été évaluée.