The mergeAllChunksWithMaxNumberOfChunksTest test is issuing merge all chunks requests with a max number of chunks and then checks that there no over-merge happened.

However, when the CSRS steps down the following can happen:

• The original request succeeds, merging 2 chunks
• The shard receives a "not ok" reply due to CSRS stepdown
• The command is retried because of the idempotent retry policy
• An additional merge happens