134: ReadConcernMajorityNotAvailableYet

What does it mean?

A read with majority read concern was requested, but a majority-committed snapshot is not yet available. The server cannot currently provide this consistency level.

Why does it happen?

The replica set has just started or is unstable, majority writes have not yet been committed, replication lag, not enough members reachable, or the cluster is still in its startup phase.

How to fix it

Wait briefly and retry; the read succeeds once the majority snapshot is available. Check replica set health and replication lag (rs.status()). Make sure enough members are up. If not required, consider a lower read concern (e.g. local).