Document Elastic Cluster - Command failed with error 303: 'Field 'writeConcern' is currently not supported' on server

[Jeff-Steele]

We were using a normal Document DB cluster with specified instances and tried to switch to an Elastic Cluster. This resulted in our Mongock change sets started to fail. It appears to fail before getting to any changesets and when Mongock is initiating and trying to create its indexes.

Caused by: com.mongodb.MongoCommandException: Command failed with error 303: 'Field 'writeConcern' is currently not supported' on server <redacted>:27017. The full response is {"code": 303, "errmsg": "Field 'writeConcern' is currently not supported", "ok": 0.0, "errorUUID": "5655b0ac-8c19-41d7-a4d6-4c1390b779f2"}
	at com.mongodb.internal.connection.ProtocolHelper.getCommandFailureException(ProtocolHelper.java:210) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.InternalStreamConnection.receiveCommandMessageResponse(InternalStreamConnection.java:520) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.InternalStreamConnection.sendAndReceiveInternal(InternalStreamConnection.java:448) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.InternalStreamConnection.lambda$sendAndReceive$0(InternalStreamConnection.java:375) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.InternalStreamConnection.sendAndReceive(InternalStreamConnection.java:378) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.UsageTrackingInternalConnection.sendAndReceive(UsageTrackingInternalConnection.java:111) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.DefaultConnectionPool$PooledConnection.sendAndReceive(DefaultConnectionPool.java:748) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.CommandProtocolImpl.execute(CommandProtocolImpl.java:68) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:208) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:113) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:82) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:73) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.connection.DefaultServer$OperationCountTrackingConnection.command(DefaultServer.java:298) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.lambda$executeCommand$5(SyncOperationHelper.java:209) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.lambda$withSourceAndConnection$0(SyncOperationHelper.java:131) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.withSuppliedResource(SyncOperationHelper.java:156) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.lambda$withSourceAndConnection$1(SyncOperationHelper.java:130) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.withSuppliedResource(SyncOperationHelper.java:156) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.withSourceAndConnection(SyncOperationHelper.java:129) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.SyncOperationHelper.executeCommand(SyncOperationHelper.java:207) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.CreateIndexesOperation.execute(CreateIndexesOperation.java:105) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.internal.operation.CreateIndexesOperation.execute(CreateIndexesOperation.java:60) ~[mongodb-driver-core-5.2.1.jar:?]
	at com.mongodb.client.internal.MongoClusterImpl$OperationExecutorImpl.execute(MongoClusterImpl.java:379) ~[mongodb-driver-sync-5.2.1.jar:?]
	at com.mongodb.client.internal.MongoCollectionImpl.executeCreateIndexes(MongoCollectionImpl.java:941) ~[mongodb-driver-sync-5.2.1.jar:?]
	at com.mongodb.client.internal.MongoCollectionImpl.createIndexes(MongoCollectionImpl.java:923) ~[mongodb-driver-sync-5.2.1.jar:?]
	at com.mongodb.client.internal.MongoCollectionImpl.createIndexes(MongoCollectionImpl.java:918) ~[mongodb-driver-sync-5.2.1.jar:?]
	at com.mongodb.client.internal.MongoCollectionImpl.createIndex(MongoCollectionImpl.java:903) ~[mongodb-driver-sync-5.2.1.jar:?]
	at io.mongock.driver.mongodb.sync.v4.repository.MongoSync4RepositoryBase.createRequiredUniqueIndex(MongoSync4RepositoryBase.java:92) ~[mongodb-sync-v4-driver-5.5.1.jar:?]
	at io.mongock.driver.mongodb.sync.v4.repository.MongoSync4RepositoryBase.ensureIndex(MongoSync4RepositoryBase.java:53) ~[mongodb-sync-v4-driver-5.5.1.jar:?]
	at io.mongock.driver.mongodb.sync.v4.repository.MongoSync4RepositoryBase.initialize(MongoSync4RepositoryBase.java:38) ~[mongodb-sync-v4-driver-5.5.1.jar:?]
	at io.mongock.driver.core.driver.ConnectionDriverBase.initialize(ConnectionDriverBase.java:49) ~[mongock-driver-core-5.5.1.jar:?]
	at io.mongock.runner.core.executor.ChangeExecutorBase.initializationAndValidation(ChangeExecutorBase.java:440) ~[mongock-runner-core-5.5.1.jar:?]
	at io.mongock.runner.core.executor.system.SystemUpdateExecutor.executeMigration(SystemUpdateExecutor.java:56) ~[mongock-runner-core-5.5.1.jar:?]
	at io.mongock.runner.core.executor.system.SystemUpdateExecutor.executeMigration(SystemUpdateExecutor.java:22) ~[mongock-runner-core-5.5.1.jar:?]
	at io.mongock.runner.core.executor.MongockRunnerImpl.execute(MongockRunnerImpl.java:57) ~[mongock-runner-core-5.5.1.jar:?]
	... 77 more

I've tried changing the WriteConcern to all the different values and even making a new one of 0 but still get the same error. Any thoughts on how to work around or fix this problem?

[Jeff-Steele]

Thought I had tried using ACKNOWLEDGED but apparently had used UNACKNOWLEDGED.

[dieppa]

Thought I had tried using ACKNOWLEDGED but apparently had used UNACKNOWLEDGED.

thanks!!