Table locks (new in V11.0) were unexpectedly preventing the reuse of empty index nodes, causing indexes to consume more disk space than expected. Rebuilding affected indexes will recover the space. Upgrading to V11.5.1 or newer will likely automatically prune this space over time. The logic has been modified to correct this and prevent this issue going forward.