What does currentDBsizeMB actually represent?
Seeing some discrepancies in the actual file system consumption between our indexers and cold storage volumes (which are nvme over IP mounts on different servers)
Does currentDBsizeMB include just hot? hot/warm? or hot/warm/cold?
Does it include replica copies or just one and you have to multiply the value by your replication factor to get the "true" size of the index on disk?
I have been unable to find a definitive answer on this, appreciate anyone in advance that can help shed some light on this field.
