urban meadow
Hello - we have a globally-distributed Mongo cluster as low latency is critical for our use cases ... and that's why we typically use readPreference=nearest ... but it seems that the new Mongo transaction support is causing an error: [07:39:53] ERROR (payload): MongoTransactionError: Read preference in a transaction must be primary, not: nearest
Is it possible to configure Payload to use readPreference=nearest for standard reads but readPreference=primary for write transactions? Or otherwise is possible to disable Mongo Transactions for certain collections?
halcyon hinge