SERVER-17151 ConfigCoordinator should not call fsync

This is expensive to do, especially with WiredTiger and is not a
deterministic check. This change replaces it with something cheaper, but
has the same outcome - validates that previous writes were successfully
journaled, which is an approximate predictor that subsequent writes have
high chance of succeeding.

1 files changed, 2 insertions, 3 deletions

diff --git a/src/mongo/db/auth/authz_manager_external_state_s.cpp b/src/mongo/db/auth/authz_manager_external_state_s.cpp
index 20e47afaed1..5d70845324f 100644
--- a/src/mongo/db/auth/authz_manager_external_state_s.cpp
+++ b/src/mongo/db/auth/authz_manager_external_state_s.cpp
@@ -245,7 +245,7 @@ namespace mongo {
             const NamespaceString& collectionName,
             const BSONObj& document,
             const BSONObj& writeConcern) {
-        return clusterInsert(collectionName, document, writeConcern, NULL);
+        return clusterInsert(collectionName, document, NULL);
     }
 
     Status AuthzManagerExternalStateMongos::update(OperationContext* txn,
@@ -262,7 +262,6 @@ namespace mongo {
                 updatePattern,
                 upsert,
                 multi,
-                writeConcern,
                 &response);
 
         if (res.isOK()) {
@@ -279,7 +278,7 @@ namespace mongo {
             const BSONObj& writeConcern,
             int* numRemoved) {
         BatchedCommandResponse response;
-        Status res = clusterDelete(collectionName, query, 0 /* limit */, writeConcern, &response);
+        Status res = clusterDelete(collectionName, query, 0 /* limit */, &response);
 
         if (res.isOK()) {
             *numRemoved = response.getN();