Upgrading Milvus version guidelines

[ifrancke-pryoninc]

Hello. For context, I recently ran into this bug in Milvus v2.5.4 where some segments were empty, which I did not identify until trying to create and restore a backup (using milvus-backup). Even after upgrading to v2.5.5, collections which were ingested using v2.5.4 are all potentially corrupted, but I don't know how to tell which ones triggered that bug. I have a few questions about that scenario:

1. For this specific bug, is there any way to tell if a segment is empty when it should not be? Is there a way to scan segments, or even more generally, is there a way to check a collection's health? What would you recommend I do to look for this?
2. In general, is it recommended to reindex all collections after upgrading Milvus? Are there any guidelines for upgrading Milvus that you recommend?

[xiaofan-luan]

directly upgrade to 2.5.10 should be fine.

everything is compatible and only contains several bug fixes.

the problem should be automatically solved after upgrade