filter_multiline: synchronize buffered output-processor appends with the flush timer

Abierto
  • ¿Algo no está bien?
#12,680 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
c
Área
backend, testing

Línea de trabajo

Start with plugins/filter_multiline/ml.c and trace cb_ml_filter(), get_or_create_stream(), flush_callback(), and shutdown alongside the multiline core append and auto-flush paths. Then inspect output worker dispatch in flb_output.c and flb_output.h, and the runtime tests named in the issue. Done means real multi-worker dispatch and timer flushes are covered, records flush correctly, shutdown is safe, classic-filter and input-processor tests pass, and ThreadSanitizer reports no races.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Summary

Track the pre-existing synchronization problem when buffered multiline parser mode runs as an output processor.

As identified in the discussion on PR #12678, output processors execute from output flush helpers on worker threads, while cb_ml_init() initializes the multiline auto-flush timer on the main scheduler. The worker path and timer can therefore access the same multiline state concurrently.

get_or_create_stream() mutates ctx->ml_streams, and flb_ml_append_event() mutates parser group buffers. The timer flush path reads or modifies that state and invokes flush_callback(), which looks up stream metadata through get_by_id().

This can cause data races and inconsistent stream or parser state. This issue tracks the synchronization concern; no runtime crash reproduction is claimed here.

Scope and required changes

  • Establish safe ownership or synchronization for buffered multiline parser state when used as an output processor.
  • Serialize stream creation, lookup, list mutation, and parser appends with timer-driven flushes. Account for concurrent output workers sharing the processor context.
  • Review flush callbacks, emitter interactions, and shutdown/destruction under the same ownership model. Avoid deadlocks or callback re-entry problems.
  • Document the threading contract and preserve existing classic-filter and input-processor behavior.
  • Add regression coverage that exercises real output worker dispatch concurrently with timer flushes.

Possible approaches include a shared synchronization mechanism or confining parser operations and timer flushes to one owner thread. The implementation should select and document the appropriate approach.

Affected areas

  • plugins/filter_multiline/ml.c: cb_ml_init(), cb_ml_filter(), get_or_create_stream(), get_by_id(), flush_callback(), and shutdown/destruction.
  • Multiline core auto-flush and append paths.
  • Output processor initialization and output flush helpers (flb_output.c and flb_output.h).
  • tests/runtime/filter_multiline.c and appropriate output-processor runtime coverage.

Acceptance criteria

  • Output-worker appends and timer flushes cannot access shared stream lists or parser buffers without synchronization or single-thread ownership.
  • Tests exercise actual output worker dispatch, including multiple workers, while timer flushes occur. Do not use a formatter test hook that bypasses worker dispatch.
  • Tests verify correct multiline concatenation and pending-content flushing without missing or duplicate records.
  • A ThreadSanitizer run of the concurrency regression reports no races in the affected multiline state.
  • Shutdown completes without deadlocks or invalid memory access.
  • Classic-filter and input-processor multiline tests continue to pass.

Relationship to PR #12678

This is separate from idle-stream eviction. PR #12678 disables idle eviction for output processors to avoid adding stream frees to the existing race. Disabling eviction does not serialize existing appends and timer flushes. Keep that safeguard until output-processor stream lifecycle safety is established; enabling eviction is not required by this issue.

Requested by @baizhenyu.

Lenguaje dominante
C
Estrellas
8.2k
Forks
2k
Merge medio
3 d 20 h
PR fusionados (30 d)
99

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluent/fluent-bit

Todos los issues de fluent/fluent-bit

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.