Nearest read preference should take account of database load
I understand it only take account of network latency however this node can have high load and would give a poor response. Instead, I wished the driver would contact the more distant network latency node that has less CPU/memory load.
1
vote
Albert
shared this idea