Closed mekya closed 2 weeks ago
After Upgrade to 2.11.0, Command failed with error 85 (IndexOptionsConflict)
It should run properly.
It throws the following exception
com.mongodb.MongoCommandException: Command failed with error 85 (IndexOptionsConflict): 'Index: { v: 2, unique: true, key: { appName: 1 }, name: "appName_unique_index" } already exists with different options: { v: 2, key: { appName: 1 }, name: "appName_1" }' on server 83.229.8.13:27017. The full response is {"ok": 0.0, "errmsg": "Index: { v: 2, unique: true, key: { appName: 1 }, name: \"appName_unique_index\" } already exists with different options: { v: 2, key: { appName: 1 }, name: \"appName_1\" }", "code": 85, "codeName": "IndexOptionsConflict"}
The PR on the Enterprise side
https://gitlab.com/Ant-Media/Ant-Media-Enterprise/-/merge_requests/728
Short description
After Upgrade to 2.11.0, Command failed with error 85 (IndexOptionsConflict)
Environment
Steps to reproduce
Expected behavior
It should run properly.
Actual behavior
It throws the following exception
com.mongodb.MongoCommandException: Command failed with error 85 (IndexOptionsConflict): 'Index: { v: 2, unique: true, key: { appName: 1 }, name: "appName_unique_index" } already exists with different options: { v: 2, key: { appName: 1 }, name: "appName_1" }' on server 83.229.8.13:27017. The full response is {"ok": 0.0, "errmsg": "Index: { v: 2, unique: true, key: { appName: 1 }, name: \"appName_unique_index\" } already exists with different options: { v: 2, key: { appName: 1 }, name: \"appName_1\" }", "code": 85, "codeName": "IndexOptionsConflict"}