cockroachdb / cockroachdb/sequelize-cockroachdb

concurrent transactions with write followed by reading fails due to timeout

Abierto
#66 5 comentarios 1 reacción 0 asignados Ver en GitHub
Lenguaje dominante
JavaScript
Estrellas
55
Forks
18
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.