MigrationQueueDeleteTTLIndex throws an exception
Context: https://github.com/huggingface/datasets-server/pull/1238#discussion_r1202804263

While running migrations of type MigrationQueueDeleteTTLIndex, an error is thrown:
`pymongo.errors.OperationFailure: An equivalent index already exists with the same name but different options. Requested index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 600 }, existing index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 86400 }, full error: {'ok': 0.0, 'errmsg': 'An equivalent index already exists with the same name but different options. Requested index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 600 }, existing index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 86400 }', 'code': 85, 'codeName': 'IndexOptionsConflict', '$clusterTime': {'clusterTime': Timestamp(1684856718, 127), 'signature': {'hash': b'\x9e\x18\x11\xa9\xfd\x9c\xec\x12\x19\xeb\xa7\xad\x94\xfb\x86<Y\xdc\xb4n', 'keyId': 7184422908209397768}}, 'operationTime': Timestamp(1684856718, 127)}`

See also https://huggingface.slack.com/archives/C04L6P8KNQ5/p1684856801355259?thread_ts=1684855715.011289&cid=C04L6P8KNQ5 (internal) for details.

Maybe this is related to other k8s objects running at the same time of deploy and try to re create the old index. Should we stop all pods while deploying? Maybe scale to 0 replicas?
MigrationQueueDeleteTTLIndex throws an exception: Context: https://github.com/huggingface/datasets-server/pull/1238#discussion_r1202804263

While running migrations of type MigrationQueueDeleteTTLIndex, an error is thrown:
`pymongo.errors.OperationFailure: An equivalent index already exists with the same name but different options. Requested index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 600 }, existing index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 86400 }, full error: {'ok': 0.0, 'errmsg': 'An equivalent index already exists with the same name but different options. Requested index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 600 }, existing index: { v: 2, key: { finished_at: 1 }, name: "finished_at_1", background: false, expireAfterSeconds: 86400 }', 'code': 85, 'codeName': 'IndexOptionsConflict', '$clusterTime': {'clusterTime': Timestamp(1684856718, 127), 'signature': {'hash': b'\x9e\x18\x11\xa9\xfd\x9c\xec\x12\x19\xeb\xa7\xad\x94\xfb\x86<Y\xdc\xb4n', 'keyId': 7184422908209397768}}, 'operationTime': Timestamp(1684856718, 127)}`

See also https://huggingface.slack.com/archives/C04L6P8KNQ5/p1684856801355259?thread_ts=1684855715.011289&cid=C04L6P8KNQ5 (internal) for details.

Maybe this is related to other k8s objects running at the same time of deploy and try to re create the old index. Should we stop all pods while deploying? Maybe scale to 0 replicas?