Failover test on Atlas with Scala driver leads to an exception and interrupted processing

One further piece of information I have.

I repeated the tests by not using the Atlas failover feature, instead changing instance size from M10 to M20 and back. This causes a primary restart every time. There wasn’t a single write concern error. After that, tried the failover feature again and it resulted in the write concern error as always.

I’m getting really suspicious of what the Atlas failover test is actually doing.

Valtteri