I have facing Write Operation issue on MongoDB Primary node

[Ramachandra_Tummala]

I think your majority data bearing nodes should acknowledge the write but it is not happening so primary is waiting
You have majority but arbiter is non data bearing
Check this thread

Best practices ReplicaSet MongoDB

Good day, colleagues! We use a highly loaded MongoDB database in a ReplicaSet configuration, which includes one primary node, 3 secondary nodes and one arbiter. One of the secondary nodes became in the recovering state, and at the same time, one of the secondary nodes was stopped. Multiple “slow query” type errors were recorded. We are using version 4.4.3. Tell me what configuration we should use to avoid such problems and maybe there are some best practices for configuring the database.