Replicaset objects are outdated (become unusable) on each router.cfg() call. That is not very user friendly. And was done in order to prevent users from keeping results of router.route() for long. But it does not give a protection against going to a wrong bucket location anyway, and makes it harder to use route() IMO.
It might make sense to stop outdating the replicaset objects unless they are not deleted from the config, or it was a module reload.
Replicaset objects are outdated (become unusable) on each
router.cfg()
call. That is not very user friendly. And was done in order to prevent users from keeping results ofrouter.route()
for long. But it does not give a protection against going to a wrong bucket location anyway, and makes it harder to useroute()
IMO.It might make sense to stop outdating the replicaset objects unless they are not deleted from the config, or it was a module reload.