It's rigth the solution of this problem to be a Improvement? I am wait a solution for this problem some months, in the old versions(<4.0) this problem don't exists. What driver and relevant dependency versions are you using?ġ - Create a basic ChangeStream and listen the close event ģ - Execute failover test into the interface Mongo Atlas, or change the primary node of the replicaSet manually Ĥ - The application must receive close signal and stop receiving new updates. ![]() When this happen the class ChangeStream receives a close signal and the applications stop receiving new database updates. We have been using the Mongo resource "collection watcher" for update our caches into the applications, but we noticed that Mongo Atlas makes a not planning rebalance of the nodes ReplicaSet. Making this happen, it was necessary an upgrade from our services to new driver (>=4.0) where we found a problem that didn't use to happen in a previous versions (<4.0). ![]() We are on migration process of our Mongo servers to version 5.0.
0 Comments
Leave a Reply. |