Write concern in MongoDB

36 views

Skip to first unread message

viki vignesh

unread,

Jul 11, 2018, 10:43:37 AM7/11/18

to mongodb-user

All,

I have below scenario and need help on that

Lets say i have replica node with set up of PSA with write concern as Majority

In some situation my secondary goes down, while my primary is still primary beacuse of arbiter, but it will not accept write operation beacuse of majority write concern

As a DBA can i change the write concern of whole cluster when secondary goes down or only the developers has the rights to do through coding ?

Wan Bachtiar

unread,

Jul 13, 2018, 3:57:31 AM7/13/18

to mongodb-user

In some situation my secondary goes down, while my primary is still primary beacuse of arbiter, but it will not accept write operation beacuse of majority write concern

Hi Viki,

The standard replica set deployment for production system is a three-member replica set (PSS). These sets provide redundancy and fault tolerance for MongoDB deployment.

As a DBA can i change the write concern of whole cluster when secondary goes down or only the developers has the rights to do through coding ?

Write Concern is intended to describe the level of acknoledgement requested from MongoDB for write operations from the client. It wouldn’t be preferable to change the default write concern from the server side. i.e. Application is requesting an acknoledgement of w:majority but the DBA set to w:1 (temporarily) which may cause the writes could possibly be rolled back.

I would suggest to replace the arbiter with a secondary member for fault tolerance.