Difference between revisions of "Failed to flush chunk"
Jump to navigation
Jump to search
(5 intermediate revisions by the same user not shown) | |||
Line 7: | Line 7: | ||
.... | .... | ||
[[Trace_Error]] on | [[Trace_Error]] on | ||
+ | |||
[[mapper_parsing_exception]] | [[mapper_parsing_exception]] | ||
+ | [[Replace_Dots]] | ||
+ | |||
+ | {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"}],"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] [[tried to parse field]] [null] as object, [[but found a concrete value]]"},"status":400} | ||
+ | status":400,"error":{"type":"[[mapper_parsing_exception]]","reason":"object mapping for [kubernetes.labels.app] tried to parse field [app] as object, [[but found a concrete value]]"}}} | ||
+ | * https://github.com/fluent/fluent-bit/issues/4386 | ||
Latest revision as of 14:51, 27 December 2022
Activate Trace_Error
to understand the issue:
[OUTPUT] .... Trace_Error on
mapper_parsing_exception Replace_Dots
{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"}],"type":"mapper_parsing_exception","reason":"object mapping for [Data.PASSED] tried to parse field [null] as object, but found a concrete value"},"status":400}
status":400,"error":{"type":"mapper_parsing_exception","reason":"object mapping for [kubernetes.labels.app] tried to parse field [app] as object, but found a concrete value"}}}
Buffer_Size False
.flb
tail.0 paused (mem buf overlimit) Backpressure [error] [upstream] connection #... timed out after ... still running on route Retry_Limit
See also[edit]
Advertising: