Release, recovery and deferral of outbox batches still cost a write per row
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- csharp
- Área
- backend, databases, performance
Línea de trabajo
Start by reading OutboxDrainer.ReleaseAsync and the claim logic it uses for leased rows; then trace how each lane reads PluginState and builds the deferred-id exclusion list. Check the existing outbox tests before changing behavior. Done means each proposal item is fixed or explicitly declined in the PR, with tests covering every fix.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
These are left over from the review of PR #3404 (outbox lanes per owner). None of them loses an event; they cost writes, time or log noise.
- Release on shutdown, row by row and without a token. A stopping host releases each unclaimed row of a batch with its own conditional
UPDATE(OutboxDrainer.ReleaseAsync), and the update takes no cancellation token. A large batch can therefore hold shutdown forBatchSizewrites. - Recovery after a failed release is row by row. A release that fails leaves the row leased with its claim attempt counted. Once the lease lapses, the row is claimed alone because it still names an owner. A whole failed batch is then recovered one claim per row.
- Deferrals cost a write each while plugin state is down. When
PluginStatecannot be read, every row of a batch is released and deferred with one write each. Each later drain then repeats the read of the plugin state for every lane. - Deferrals are bounded by time only. A deferred row is skipped for
MissingHandlerDelay, and the set of deferred ids is not capped. Their ids also go into every claim as aNOT INparameter list. A long thread-pool starvation can make that list long.
Proposal
- Release the rest of a batch with one
UPDATE ... WHERE id IN (...), bounded by a short timeout. - After a lapsed lease, claim alone only the first row that names a dead owner, not each of them.
- Read plugin state once per lane pass, and on failure release the batch in one write.
- Cap the deferred set, for example at
BatchSize, and leave the oldest out of theNOT INlist.
Acceptance
- Each item fixed or explicitly declined in its PR, with tests for those fixed
- Lenguaje dominante
- C#
- Estrellas
- 567
- Forks
- 107
- Merge medio
- 1 h 19 min
- PR fusionados (30 d)
- 353
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de fluentcms/FluentCMS
-
area:localization plugin type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area:storage type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
area:testing type:bug
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
area:api area:publishing type:feature
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
fluentcms/FluentCMS#3473 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:storage plugin type:bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de fluentcms/FluentCMS
Issues similares
-
[Bug]: Threading.Analyzers 0.7.79 does not load on the .NET 10 SDK (CS9057), CHT rules silently offAbiertobug regression threading
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
CryptoHives/Foundation#362 ·
Los mantenedores suelen responder en 1 día
-
[Bug]: 本地歌词翻译显示错误Abiertobug need-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
Fervent-Tempo/AF-Media-Bar#321 ·
-
a-corriger documentation
Dificultad 1/5 Menos de una hora Aptitud para principiantes 87/100
christian-raj/S-Aloha#345 ·
-
bug 要トリアージ
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
worldInstancedOccluderNode reads its appendix count as one byte, but it is a VLQPosiblemente ocupada @spuddeh la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día