Since it was initially assumed that data size aware balancing would land in v6.0, the chunk resize policy was structured to unconditionally happen on downgrade (from v6.0 to v5.x). As data size aware balancing landed in v6.1, it is needed to adapt that part of the code to only resize chunks in case the downgrade is happening from v6.x (x>0) to v6.0.