I was working with mongDB interface to azure cosmos and using the .net core driver.
Here if i execute:
it throws an exception after approximately 5 seconds of type MongoDB.Driver.MongoExecutionTimeoutException
However if i instead manually make it async with:
await Task.Factory.StartNew(() => Collection.DeleteMany(filter)).ConfigureAwait(false);
it does as intended.
I tried specifying the SocketTimeout to amend initial problem, but depending on what documentation i find it is either non-existent per default (0) or 30 seconds (?) and anyway setting it to 10 minutes doesn’t change anything as exception is throw way before and again simply using the syncronous version avoid the problem so I suppose it is a bug or am i doing something wrong, could issue be with it being the Azure cloud abstraction solely?
Anybody else have experience with this or will take over reported issue so i won’t have to register as participant to fix it myself, in this splendid open source driver project= 0:-)
Thanks and Br,