[SERVER-5197] replSet initial sync failing, error applying oplog 0 assertion db/pdfile.h:488 Created: 05/Mar/12  Updated: 15/Aug/12  Resolved: 05/Mar/12

Status: Closed
Project: Core Server
Component/s: Internal Code, Replication
Affects Version/s: 2.0.3
Fix Version/s: None

Type: Bug Priority: Blocker - P1
Reporter: Liu Qishuai Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

PRIMARY is 1.8.3, adding a new 2.0.3 server in the replica set.


Issue Links:
Depends
depends on SERVER-5177 fetching of docs in initial sync can ... Closed
Operating System: Linux
Participants:

 Description   

Mon Mar 5 08:48:08 [rsSync] replSet initial sync cloning db: admin
Mon Mar 5 08:48:08 [rsSync] replSet initial sync query minValid
Mon Mar 5 08:48:09 [rsSync] replSet initial oplog application from 192.168.168.9:27017 starting at Mar 5 04:42:10:8 to Mar 5 08:48:09:aa
Mon Mar 5 08:48:09 [rsSync] Assertion failure database db/pdfile.h 488
Mon Mar 5 08:48:09 [rsSync] replSet initial sync failing, error applying oplog 0 assertion db/pdfile.h:488
Mon Mar 5 08:48:09 [rsSync] replSet initial sync failed during applyoplog
Mon Mar 5 08:48:09 [rsSync] replSet cleaning up [1]
Mon Mar 5 08:48:09 [rsSync] replSet cleaning up [2]
Mon Mar 5 08:48:15 [rsSync] replSet initial sync pending
Mon Mar 5 08:48:15 [rsSync] replSet syncing to: 192.168.168.9:27017
Mon Mar 5 08:48:15 [rsSync] replSet initial sync drop all databases
Mon Mar 5 08:48:15 [rsSync] dropAllDatabasesExceptLocal 9



 Comments   
Comment by Eliot Horowitz (Inactive) [ 12/Mar/12 ]

Only the new one.
And can be put back to 2.0.3 once the sync is done.

Comment by Y. Wayne Huang [ 12/Mar/12 ]

Eliot, if you would take a few extra seconds to carefully detail the workaround, it would save a lot of us some trouble. Does only the new replicaset member have to run 2.0.2 or the entire replicaset?

Comment by Eliot Horowitz (Inactive) [ 05/Mar/12 ]

You've hit: SERVER-5177
You can either use 2.0.2 or the 2.0 nightly

Generated at Thu Feb 08 03:08:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.