You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While implementing replica get and testing with the mock, I noticed an issue which comes up depending on the key. When configured with 2 nodes and 1 replica, I get NMVs for the active node both for upsert and get. See this simple example:
String id = "4c03805d-adc9-47a7-9014-bd94c693a2bb";
collection.upsert(id, "Hello, World!");
Thread.sleep(1000);
collection.get(id);
I am not sure what is causing this, but my code seems to work against a real cluster. Maybe it has something to do with how the mock handles its config/topo?
The text was updated successfully, but these errors were encountered:
While implementing replica get and testing with the mock, I noticed an issue which comes up depending on the key. When configured with 2 nodes and 1 replica, I get NMVs for the active node both for upsert and get. See this simple example:
I am not sure what is causing this, but my code seems to work against a real cluster. Maybe it has something to do with how the mock handles its config/topo?
The text was updated successfully, but these errors were encountered: