[SERVER-9261] [TTLMonitor] error processing ttl logOp() not primary Created: 05/Apr/13  Updated: 10/Dec/14  Resolved: 05/Apr/13

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

Type: Bug Priority: Minor - P4
Reporter: David Verdejo Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: error, not, primary, ttlmonitor
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Fri Apr 05 13:21:35.194 [initandlisten] db version v2.4.1
Fri Apr 05 13:21:35.194 [initandlisten] git version: 1560959e9ce11a693be8b4d0d160d633eee75110
Fri Apr 05 13:21:35.194 [initandlisten] build info: windows sys.getwindowsversion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49


Attachments: PNG File mongodb_ttl_error.PNG    
Issue Links:
Duplicate
duplicates SERVER-9053 TTL index asserts on 2.4 secondary Closed
Operating System: Windows
Steps To Reproduce:

Create a replica set and then create a collection with an TTL index

Participants:

 Description   

On the log, I see the following errors related to TTLMonitor:

Fri Apr 05 17:34:04.725 [conn17288] end connection 172.29.102.67:4505 (73 connections now open)
Fri Apr 05 17:34:04.803 [TTLMonitor] Assertion: 13312:replSet error : logOp() but not primary?
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\util\stacktrace.cpp(189) mongo::printStackTrace+0x3e
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\util\assert_util.cpp(159) mongo::msgasserted+0xc1
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\db\oplog.cpp(176) mongo::_logOpRS+0x1d6
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\db\ops\delete.cpp(125) mongo::deleteObjects+0xaa3
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\db\ttl.cpp(107) mongo::TTLMonitor::doTTLForDB+0x12a5
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\db\ttl.cpp(147) mongo::TTLMonitor::run+0x2c4
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\mongo\util\background.cpp(65) mongo::BackgroundJob::jobBody+0x316
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\third_party\boost\boost\bind\mem_fn_template.hpp(165) boost::_mfi::mf1<void,mongo::BackgroundJob,boost::shared_ptr<mongo::BackgroundJob::JobStatus> >::operator()+0x47
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\third_party\boost\boost\thread\detail\thread.hpp(63) boost::detail::thread_data<boost::_bi::bind_t<void,boost::_mfi::mf1<void,mongo::BackgroundJob,boost::shared_ptr<mongo::BackgroundJob::JobStatus> >,boost::_bi::list2<boost::_bi::value<mongo::BackgroundJob * __ptr64>,boost::_bi::value<boost::shared_ptr<mongo::BackgroundJob::JobStatus> > > > >::run+0x31
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe ...\src\third_party\boost\libs\thread\src\win32\thread.cpp(180) boost::`anonymous namespace'::thread_start_function+0x21
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe f:\dd\vctools\crt_bld\self_64_amd64\crt\src\threadex.c(314) _callthreadstartex+0x17
Fri Apr 05 17:34:05.255 [TTLMonitor] mongod.exe f:\dd\vctools\crt_bld\self_64_amd64\crt\src\threadex.c(292) _threadstartex+0x7f
Fri Apr 05 17:34:05.255 [TTLMonitor] KERNEL32.DLL BaseThreadInitThunk+0x1a
Fri Apr 05 17:34:05.255 [TTLMonitor] ERROR: error processing ttl for db: cacheagg 13312 replSet error : logOp() but not primary?
Fri Apr 05 17:34:05.630 [initandlisten] connection accepted from 172.29.102.74:1856 #17289 (74 connections now open)



 Comments   
Comment by Scott Hernandez (Inactive) [ 05/Apr/13 ]

This is fixed in 2.4.2 with SERVER-9053.

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