DiskUsages with negative total or free space are unserialisable #48413
Labels
>bug
:Data Management/Stats
Statistics tracking and retrieval APIs
Team:Data Management
Meta label for data/management team
Today
DiskUsage
useswriteVLong()
to write its sizes in bytes, so serialising a negative size results in anIllegalStateException
.One possible source of negative sizes was if the
DiskThresholdDecider
subtracted more relocating shards than the free space of the disk, and this is being addressed in #48392. This was benign since we never serialised the resultingDiskUsage
objects. However according toDiskUsageTests
we can get negative sizes in other ways too. I'm not sure this is true in Elasticsearch today, but it warrants a more careful investigation. Maybe we can fix the tests and then add assertions that the sizes are always non-negative, or maybe we need to fix the serialisation to deal with negative sizes.The text was updated successfully, but these errors were encountered: