summaryrefslogtreecommitdiff
path: root/jstests/sharding/exhaust_hello_topology_changes.js
diff options
context:
space:
mode:
Diffstat (limited to 'jstests/sharding/exhaust_hello_topology_changes.js')
-rw-r--r--jstests/sharding/exhaust_hello_topology_changes.js4
1 files changed, 2 insertions, 2 deletions
diff --git a/jstests/sharding/exhaust_hello_topology_changes.js b/jstests/sharding/exhaust_hello_topology_changes.js
index b0173c9bc40..51b381838a5 100644
--- a/jstests/sharding/exhaust_hello_topology_changes.js
+++ b/jstests/sharding/exhaust_hello_topology_changes.js
@@ -1,8 +1,8 @@
/**
- * Test to check that the RSM receives a hello reply "immediately" (or "quickly") after a RS
+ * Test to check that the RSM receives an isMaster reply "immediately" (or "quickly") after a RS
* topology change when using the exhaust protocol. In order to test this, we'll set the
* maxAwaitTimeMS to much higher than the default (5 mins). This will allow us to assert that the
- * RSM receives the hello replies because of a topology change rather than maxAwaitTimeMS being
+ * RSM receives the isMaster replies because of a topology change rather than maxAwaitTimeMS being
* hit. A replica set node should send a response to the mongos as soon as it processes a topology
* change, so "immediately"/"quickly" can vary - we specify 5 seconds in this test ('timeoutMS').
*