does anyone received this problem?? and. how to re...
# general
a
does anyone received this problem?? and. how to resolve it?
g
i haven't seem something like this before; it's possible the segment file for
bypass_info_pivot_2024-05-08T05:00:00.000Z_2024-05-08T06:00:00.000Z_2024-05-08T05:00:00.807Z_155
is corrupted you can try this to force the server to reload the segment from deep storage: • shut down the historical that is throwing this error • remove the segment directory for
bypass_info_pivot_2024-05-08T05:00:00.000Z_2024-05-08T06:00:00.000Z_2024-05-08T05:00:00.807Z_155
from the local segment cache (the one containing
meta.smoosh
, etc) and also remove its descriptor from from the
info_dir
• start the historical back up if that resolves the error, it must have been the local copy on disk getting corrupted somehow it it doesn't resolve the error, it's possible the segment in deep storage is bad somehow