[SERVER-4721] writeback ids can be missed in particular cases Created: 19/Jan/12  Updated: 11/Jul/16  Resolved: 17/Jan/13

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Caused by: com.mongodb.CommandResult$CommandFailure: command failed [command failed [getlasterror]

{ "serverUsed" : "mmsrrdmongos1.10gen.cc:27017" , "assertion" : "got writeback waitfor for older id oid: 4f17a1e7c012a92f45000000 s.id: 4f17a1e7c012a92f45fffff8 ident: cbi4.ny.10gen.cc:27018:269072" , "assertionCode" : 14041 , "errmsg" : "db assertion failure" , "ok" : 0}

at com.mongodb.CommandResult.getException(CommandResult.java:75)
at com.mongodb.CommandResult.throwOnError(CommandResult.java:121)
at com.xgen.svc.mms.dao.BaseDao.checkLastError(BaseDao.java:307)
at com.xgen.svc.mms.dao.BaseDao.checkLastError(BaseDao.java:302)
at com.xgen.svc.mms.svc.ping.RrdSvc$IncrementProcessor.run(RrdSvc.java:160)



 Comments   
Comment by Eliot Horowitz (Inactive) [ 17/Jan/13 ]

This was fixed by the changes to writeback id order generation.

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