Skip to content

Run into "Internal Error: Corrupted BufferExtend" #64

@huchengjiang

Description

@huchengjiang

The decompressor occassionally running into this error. If restart the decompressor (decompressUnordered mode) can continue without the error in the same binary log location.

But it could happen again later, this is killing the quality in production by dumping Text log file.

The error reported from log.cc #2022.

                fprintf(stderr, "Internal Error: Corrupted BufferExtent\r\n");

Has anyone encountered this? Any helpful hints are appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions