TiFlash v8.5.8: MergeDelta repeatedly fails with “invalid field index” after a zero-length partial Page read, including after restart
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
- 35/100
Línea de trabajo
Start with the reported read path: Segment::prepareMergeDelta through ColumnFileTiny::fillColumns to Page::getFieldData, then inspect the zero-length branch in BlobStore.cpp around line 891. Compare the persisted PageEntry field offsets with the ColumnFileTiny schema metadata for the referenced Page, using read-only diagnostics before recovery. The issue is resolved when the evidence distinguishes those causes and identifies which Page and schema metadata to preserve.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Background MergeDelta repeatedly failed on the same Segment and Page on one TiFlash instance. We counted 2,260 failed attempts in approximately 30 minutes. The same Segment, Page and field-index error appeared again within seconds of a subsequent TiFlash restart.
Environment: TiFlash v8.5.8, engine Git hash reported at restart 3abdec8bff315647a056e6bf910abd4b59af2011, Linux x86-64.
Observed errors (identifiers redacted consistently):
BlobStore.cpp:891
Reading with fields but entry size is 0
page_id=<TABLE_A>.<PAGE_A>
fields=[1, 2]
PageEntry.size=365272
field_offsets begins with [0, 0, 0, 0, ...]
DeltaMergeStore_InternalBg.cpp:452
Execute task on segment failed, task=MergeDelta
segment_id=<SEGMENT_A>
Try to getFieldData with invalid field index
[page_id=<PAGE_A>] [valid=true] [field_index=2]
Failing read path (selected frames):
Segment::prepareMergeDelta
→ Segment::ensurePlace
→ ColumnFileSetReader::readPKVersion
→ ColumnFileTiny::fillColumns
→ Page::getFieldData(2)
The logged PageEntry had a nonzero total size. The zero-length warning occurred on the partial read for fields [1, 2]. In the corresponding BlobStore source, the zero-length branch returns a Page with empty data and no populated field offsets. This explains the subsequent lookup failure. We have not determined how the stored field offsets were produced.
Observed impact: Across three samples spanning about five and a half minutes, Delta rows on the affected Segment increased by 665, reaching approximately 673,000 rows and 463 MiB. The logical Delta ColumnFile count increased by 425, reaching approximately 226,000. The Segment epoch and Stable row count stayed constant across these samples.
Reproduction: The existing affected replica reproduced the error across a process restart. We do not have a procedure to create the original Page state on a fresh cluster.
What read-only diagnostics would help distinguish a problem in the persisted PageEntry field offsets from a mismatch between ColumnFileTiny schema metadata and the referenced Page? We would also appreciate guidance on which Page and schema metadata to preserve before attempting replica recovery.
- Lenguaje dominante
- C++
- Estrellas
- 1k
- Forks
- 428
- Merge medio
- 2 d 7 h
- PR fusionados (30 d)
- 100
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin 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 pingcap/tiflash
-
component/compute type/bug
Dificultad 2/5 1-2 días Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Out-of-bounds read in MyDateTime formatting from unvalidated packed valuesPosiblemente ocupada @ChangRui-Ryan la tomó hoy. Abiertoaffects-25.10 affects-26.3 affects-26.9 affects-7.5 affects-8.1 affects-8.5 severity/major type/bug
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
Los mantenedores suelen responder en 1 día
-
component/storage severity/moderate type/bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
pingcap/tiflash#11335 · 5 comentarios ·
Los mantenedores suelen responder en 1 día
-
Missing validation in JSON constructors, LEFT expressions, and CH-block decodingPosiblemente ocupada @windtalker la tomó hoy. Abiertotype/bug
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
[disagg] Query fails with Code: 11000 NoSuchKey when S3 GC (ScanThenDelete) removes a DMFile that a compute node still readsPosiblemente ocupada @JinheLin la tomó hace 6 días. Abiertomay-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/moderate type/bug
pingcap/tiflash#11291 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de pingcap/tiflash
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
useless statementAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
grizzlypeak3d/DJV#962 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día