osantana85
commented
6 months ago Hello @Vladcorjuc , we couldn't reproduce this error. It should be caused by something specific to your configuration, environment o even MongoDb Atlas. Could you share any additional detail about your configuration that can be useful to understand the origin of it?
Description
We noticed that our spring-boot microservices wich are using mongock will throw the following exception: com.mongodb.MongoCommandException: Command failed with error 26 (NamespaceNotFound): 'ns does not exist: {DATABASE_NAME}.mongockChangeLog' where _{DATABASENAME} is our database name.
This does not happen frequently, we suspect that a connection reset occurred.
PRIORITY
NORMAL
Version and environment
Mongock
Environment
Steps to Reproduce
Steps to reproduce are unknown since this happens rarely.
Behaviour
Expected behavior: No error should be thrown and migration should work as expected.
Actual behavior: An error is thrown : com.mongodb.MongoCommandException: Command failed with error 26 (NamespaceNotFound): 'ns does not exist: {DATABASE_NAME}.mongockChangeLog' on server {MONGODB_SERVER}. The full response is {"ok": 0.0, "errmsg": "ns does not exist: {DATABASE_NAME}.mongockChangeLog", "code": 26, "codeName": "NamespaceNotFound", "$clusterTime": {"clusterTime": {"$timestamp": {"t": 1710957686, "i": 3}}, "signature": {"hash": {"$binary": {"base64": "QNKnOK7Nmvqb8rrHKD4EZUP8s9A=", "subType": "00"}}, "keyId": 7292061381421957121}}, "operationTime": {"$timestamp": {"t": 1710957686, "i": 3}}}
How often the bug happens: 4%
Link to repository using Mongock
Not Available