Overview: I have a 3 member replica set configuration. 1 primary, 1 secondary and 1 arbiter. All 3 are running and are in perfect sync with each other.
Problem: All the instances were stopped for server maintenance. They were started in the following order:
- Primary instance.
- Secondary instance.
- Arbiter instance.
After all the 3 instance services were started, the arbiter failed to start correctly in the replica set. Upon checking the logs, I found the following line being printed repeatedly
Thu Jul 12 18:32:20 [rsStart] replSet can't get local.system.replset config from self or any seed (yet)
Thu Jul 12 18:32:30 [rsStart] replSet can't get local.system.replset config from self or any seed (yet)
Thu Jul 12 18:32:40 [rsStart] replSet can't get local.system.replset config from self or any seed (yet)
Thu Jul 12 18:32:50 [rsStart] replSet can't get local.system.replset config from self or any seed (yet)
Steps performed to resolve:
- Stopped the arbiter instance.
- Deleted the local db files from arbiter's data folder.
- Removed the instances from the replica set (including secondary).
- Started the arbiter instance.
- Added both the secondary and arbiter instance to the replica set
I am trying to figure out the following questions:
- Why is the above log statement printed repeatedly?
- What might be the cause of such an issue?
