[SERVER-14523] SECONDARY in RECOVERING state after a resync Created: 10/Jul/14 Updated: 16/Nov/21 Resolved: 11/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sridhara Huchappa | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Run reSync operation on a SECONDARY with full-sync after clean-up of data directory. |
| Participants: |
| Description |
|
We run a resync on SECONDARY on a prod replica. During the process, oplog on secondary was set to 131GB by mongo where as the PRIMARY oplog is only 3GB. SECONDARY oplog PRIMARY Oplog erep:PRIMARY> db.printReplicationInfo() erep:RECOVERING> rs.status() , , , Question: what is the max oplog size we can use for both and should I make them both 131GB or go higher? |
| Comments |
| Comment by Ramon Fernandez Marina [ 11/Jul/14 ] |
|
sridharah, the too stale to catch up message means your secondary has fallen behind and it's no longer replicating data. At this point it needs to be re-synced from the primary. Note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Also, please review the documentation on the oplog, and how to change the oplog size for more information. |
| Comment by Sridhara Huchappa [ 10/Jul/14 ] |
|
More information from the oplog: Thu Jul 10 14:46:45.946 [rsBackgroundSync] replSet not trying to sync from wslermdb01sp:27017, it is vetoed for 8 more seconds |
| Comment by Sridhara Huchappa [ 10/Jul/14 ] |
|
The error message we see in the mongod.log on SECONDARY is : |