[SERVER-17150] logOp fassert when dropping collection on stepped-down primary Created: 02/Feb/15  Updated: 18/Sep/15  Resolved: 05/Feb/15

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.0.0-rc7
Fix Version/s: 3.0.0-rc8

Type: Bug Priority: Critical - P2
Reporter: Kamran K. Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-15308 Stepdown does not cancel active (back... Closed
related to SERVER-17163 Fatal error "logOp but not primary" i... Closed
related to SERVER-17179 check for replicaset stepdown in cloner Closed
related to SERVER-17205 logOp fassert when creating namespace... Closed
related to SERVER-17208 logOp fassert when creating namespace... Closed
is related to SERVER-15310 kill all operations before attempting... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

This bug does not seem to affect 2.6.7, only 3.0.

replSet error : logOp() but can't accept write to collection test.$cmd
Fatal Assertion 17405
 
#0  0x00007ff46aa1320b in raise (sig=5) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
#1  0x00000000018c32bc in mongo::breakpoint () at src/mongo/util/debugger.cpp:63
#2  0x00000000018b8373 in mongo::fassertFailed (msgid=17405) at src/mongo/util/assert_util.cpp:165
#3  0x00000000015e921e in mongo::repl::(anonymous namespace)::_logOpRS (txn=0x7ff43fafe7d0, opstr=0x1f99b67 "c", ns=0x5247728 "test.$cmd", logNS=0x0, obj=..., o2=0x0, bb=0x0, 
    fromMigrate=false) at src/mongo/db/repl/oplog.cpp:238
#4  0x00000000015ea122 in mongo::repl::logOp (txn=0x7ff43fafe7d0, opstr=0x1f99b67 "c", ns=0x5247728 "test.$cmd", obj=..., patt=0x0, b=0x0, fromMigrate=false)
    at src/mongo/db/repl/oplog.cpp:380
#5  0x0000000001336d7c in mongo::CmdDrop::run (this=0x2875540 <mongo::cmdDrop>, txn=0x7ff43fafe7d0, dbname=..., cmdObj=..., errmsg=..., result=..., fromRepl=false)
    at src/mongo/db/dbcommands.cpp:520
#6  0x00000000013326ff in mongo::_execCommand (txn=0x7ff43fafe7d0, c=0x2875540 <mongo::cmdDrop>, dbname=..., cmdObj=..., queryOptions=0, errmsg=..., result=..., fromRepl=false)
    at src/mongo/db/dbcommands.cpp:1273
#7  0x000000000133367c in mongo::Command::execCommand (txn=0x7ff43fafe7d0, c=0x2875540 <mongo::cmdDrop>, queryOptions=0, cmdns=0x512a414 "test.$cmd", cmdObj=..., result=..., 
    fromRepl=false) at src/mongo/db/dbcommands.cpp:1489
#8  0x0000000001333f5b in mongo::_runCommands (txn=0x7ff43fafe7d0, ns=0x512a414 "test.$cmd", _cmdobj=..., b=..., anObjBuilder=..., fromRepl=false, queryOptions=0)
    at src/mongo/db/dbcommands.cpp:1561
#9  0x0000000001535fa2 in mongo::runCommands (txn=0x7ff43fafe7d0, ns=0x512a414 "test.$cmd", jsobj=..., curop=..., b=..., anObjBuilder=..., fromRepl=false, queryOptions=0)
    at src/mongo/db/query/find.cpp:137
#10 0x0000000001537fca in mongo::runQuery (txn=0x7ff43fafe7d0, m=..., q=..., nss=..., curop=..., result=..., fromDBDirectClient=false) at src/mongo/db/query/find.cpp:606
#11 0x000000000143e06a in mongo::receivedQuery (txn=0x7ff43fafe7d0, c=..., dbresponse=..., m=..., fromDBDirectClient=false) at src/mongo/db/instance.cpp:220
#12 0x000000000143f214 in mongo::assembleResponse (txn=0x7ff43fafe7d0, m=..., dbresponse=..., remote=..., fromDBDirectClient=false) at src/mongo/db/instance.cpp:403
#13 0x000000000113f668 in mongo::MyMessageHandler::process (this=0x4dec130, m=..., port=0x5131a40, le=0x4e13f70) at src/mongo/db/db.cpp:206
#14 0x00000000018e14b0 in mongo::PortMessageServer::handleIncomingMsg (arg=0x5131a40) at src/mongo/util/net/message_server_port.cpp:229
#15 0x00007ff46aa0b182 in start_thread (arg=0x7ff43faff700) at pthread_create.c:312
#16 0x00007ff469b0c00d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111


Version: 51ae76922e



 Comments   
Comment by Githook User [ 05/Feb/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-15308 SERVER-17150 cancel current command on the primary when the node is stepped down

(cherry picked from commit 1e58c0374677a37c09438aa8c21d745cd5b08468)
Branch: v3.0
https://github.com/mongodb/mongo/commit/25d7e2bde8969c3a2c6725c3663eb21e7df86d21

Comment by Githook User [ 05/Feb/15 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-15308 SERVER-17150 cancel current command on the primary when the node is stepped down
Branch: master
https://github.com/mongodb/mongo/commit/1e58c0374677a37c09438aa8c21d745cd5b08468

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