Hello Team,

I am not sure this comes in which category either in bug or improvement or something else.

Version: 3.0.4
Storage Engine: MMAPV1

I have a three-member replica set with 1 primary and 2 secondaries:

A - Primary
B - Secondary
C - Secondary
Initially I had only one Member A and all CRUD operations were performed on it only.

After some time I introduced 2 secondaries, B and C. Now again for some reason, secondaries were removed and rejoined in cluster.

Then I have stepdown node A to make node C primary.

Now it seems to be abnormal:

Node A:
rs1:SECONDARY> show dbs
TEST 2136.457GB

Node B:
rs1:PRIMARY> show dbs
TEST 351.329GB

Node C:
rs1:SECONDARY> show dbs
TEST 2136.457GB

-------------------------------

Node B becomes primary and now application is showing "No data found error"

B becomes primary after failover, I made Node A primary manually.
but is this any criteria to check syncronization first and then elect for the Primary Node . Please suggest