BUG REPORT
Describe the bug
When bookie GC encounters an entryLog file with disordered data, a IllegalArgumentException are not caught, resulting in the death of the GC thread and the end of the GC process.
This problem is encountered again in the next GC, resulting in the subsequent entrylog being unable to GC.
The problem described in this issue(#3604) will cause the entryLog file to be disordered, and will cause the IllegalArgumentException when parsing the entrylog file.
In our case, due to the disorder of the entrylog file, the exception in the above figure appeared. This exception is not a subclass of IOException and cannot be caught.
@hangc0276
BUG REPORT
Describe the bug
When bookie GC encounters an entryLog file with disordered data, a IllegalArgumentException are not caught, resulting in the death of the GC thread and the end of the GC process.
This problem is encountered again in the next GC, resulting in the subsequent entrylog being unable to GC.
The problem described in this issue(#3604) will cause the entryLog file to be disordered, and will cause the IllegalArgumentException when parsing the entrylog file.
In our case, due to the disorder of the entrylog file, the exception in the above figure appeared. This exception is not a subclass of IOException and cannot be caught.
@hangc0276