summaryrefslogtreecommitdiff
path: root/jstests/replsets/sync2.js
diff options
context:
space:
mode:
authorMark Benvenuto <mark.benvenuto@mongodb.com>2016-05-28 17:55:12 -0400
committerMark Benvenuto <mark.benvenuto@mongodb.com>2016-05-28 17:55:12 -0400
commit6dcdd23dd37ef12c87e71cf59ef01cd82432efe0 (patch)
treec8cfb5acb62c80f375bc37e7d4350382deea6a37 /jstests/replsets/sync2.js
parentd4ac5673ea3f6cef4ce9dbcec90e31813997a528 (diff)
downloadmongo-6dcdd23dd37ef12c87e71cf59ef01cd82432efe0.tar.gz
SERVER-23971 Clang-Format code
Diffstat (limited to 'jstests/replsets/sync2.js')
-rw-r--r--jstests/replsets/sync2.js4
1 files changed, 1 insertions, 3 deletions
diff --git a/jstests/replsets/sync2.js b/jstests/replsets/sync2.js
index 481f59a13d9..8624d913538 100644
--- a/jstests/replsets/sync2.js
+++ b/jstests/replsets/sync2.js
@@ -35,9 +35,7 @@ assert.soon(function() {
replTest.awaitReplication();
jsTestLog("Checking that ops still replicate correctly");
-var option = {
- writeConcern: {w: 5, wtimeout: 30000}
-};
+var option = {writeConcern: {w: 5, wtimeout: 30000}};
// In PV0, this write can fail as a result of a bad spanning tree. If 2 was syncing from 4 prior to
// bridging, it will not change sync sources and receive the write in time. This was not a problem
// in 3.0 because the old version of mongobridge caused all the nodes to restart during