1

W SHARDING [replSetDistLockPinger] pinging failed for distributed lock pinger :: caused by :: WriteConcernFailed: waiting for replication timed out. Error details: { wtimeout: true }

In my MongoDB logs i found these kind of error at particular time (18:21 -18:39)on all primaries and secondaries in my replica set and config servers what causes this kind of issues & will it effect to the cluster and whats the solution to resolve this kind of issue

1 Answer 1

1

Your SECONDARY nodes are lagging on replication and your write concern dictates that write to the database should be acknowledged with X nodes, but before the system got enough acks, there was write timeout.

Check rs.printSlaveReplicationInfo() on all replica sets during time when you have hight load.

2
  • Will this effect to the cluster is it risky
    – ashk
    Commented Nov 24, 2017 at 20:10
  • Only, if you lost your primary (so primary status is moved to other node in replica set) during time when all your secondaries are lagging with replication same time/moment. In that moment you could lost some insert/update if your write concern is one (1). But generally answer to question is no. Your cluster is fine.
    – JJussi
    Commented Nov 25, 2017 at 8:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.