Thank you @MaBeuLux88_xxx for the detailed response.
In summary, if there is no “write” concern of majority, then there shouldn’t be any worry overall.
In our case, we have a 3 node High Availability Managing cluster, that we wanted to re-purpose with 27017 port allotted for arbiters. That way we will be able to handle the HA of Mongo as well, with the existing machines without deploying new nodes ONLY for arbiter.
Also I got your feedback on the P+S+S again based on the write concern. As I mentioned we were using Single node anyways for the existing system where we were not using the write concern anyways.
Also definitely we won’t run into the situation of all Arbiter nodes being down at the same time.
In summary the proposal for 3 arbiter nodes is for consistency on the High Availability nodes (from a deployment stand-point) and nothing else.
Please let me know if we should be considering any other factors for our case, other than write concern.
Thanks a lot.
Regds,
Sivakumar