[SERVER-38419] Crash in rename collection Created: 05/Dec/18  Updated: 04/Dec/20  Resolved: 30/Jul/19

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

Type: Bug Priority: Major - P3
Reporter: Dharshan Rangegowda Assignee: Kelsey Schubert
Resolution: Incomplete Votes: 0
Labels: st-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-52926 [3.6] Mongo db crash with Got signal:... Closed
is related to SERVER-37443 Reuse in-memory catalog objects throu... Closed
Operating System: ALL
Sprint: Storage NYC 2019-01-14, Storage NYC 2019-01-28, Storage NYC 2019-02-11, Storage NYC 2019-02-25, Storage NYC 2019-03-11, Storage NYC 2019-03-25
Participants:

 Description   

Server version is 3.6.6

2018-12-05T00:32:51.888+0000 I COMMAND [conn64] renameCollection: renaming collection no UUID from proxy.tmp.agg_out.24751 to proxy.tmp2_site_time_hour
 2018-12-05T00:32:52.162+0000 I STORAGE [conn64] dropCollection: proxy.tmp2_site_time_hour (no UUID) - renaming to drop-pending collection: proxy.system.drop.1543969972i1t149.tmp2_site_time_hour with drop optime \{ ts: Timestamp(1543969972, 1), t: 149 }
 2018-12-05T00:32:52.498+0000 F - [conn64] Invalid access at address: 0
 2018-12-05T00:32:52.553+0000 F - [conn64] Got signal: 11 (Segmentation fault).
 
 ----- BEGIN BACKTRACE -----
 mongod(_ZN5mongo15printStackTraceERSo+0x41) [0x5627eb4d3aa1]
 mongod(+0x2252CB9) [0x5627eb4d2cb9]
 mongod(+0x2253326) [0x5627eb4d3326]
 libpthread.so.0(+0xF690) [0x7f48c668f690]
 mongod(_ZN5mongo24KVCollectionCatalogEntryD1Ev+0x22) [0x5627e9e3d562]
 mongod(_ZN5mongo24KVCollectionCatalogEntryD0Ev+0x11) [0x5627e9e3d5c1]
 mongod(_ZN5mongo26KVDatabaseCatalogEntryBase19AddCollectionChange8rollbackEv+0x53) [0x5627e9e33633]
 mongod(_ZN5mongo22WiredTigerRecoveryUnit6_abortEv+0xE7) [0x5627e9cd7e87]
 mongod(_ZN5mongo15WriteUnitOfWorkD1Ev+0x52) [0x5627e9c89ce2]
 mongod(+0x94298B) [0x5627e9bc298b]
 mongod(+0xF28F72) [0x5627ea1a8f72]
 mongod(_ZN5mongo16renameCollectionEPNS_16OperationContextERKNS_15NamespaceStringES4_RKNS_23RenameCollectionOptionsE+0x62) [0x5627ea1ac5f2]
 mongod(+0xCAEE4F) [0x5627e9f2ee4f]
 mongod(_ZN5mongo23ErrmsgCommandDeprecated3runEPNS_16OperationContextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_7BSONObjERNS_14BSONObjBuilderE+0x46) [0x5627eae04da6]
 mongod(_ZN5mongo12BasicCommand11enhancedRunEPNS_16OperationContextERKNS_12OpMsgRequestERNS_14BSONObjBuilderE+0x76) [0x5627eae07826]
 mongod(_ZN5mongo7Command9publicRunEPNS_16OperationContextERKNS_12OpMsgRequestERNS_14BSONObjBuilderE+0x1F) [0x5627eae0244f]
 mongod(+0xC23B65) [0x5627e9ea3b65]
 mongod(+0xC2530D) [0x5627e9ea530d]
 mongod(_ZN5mongo23ServiceEntryPointMongod13handleRequestEPNS_16OperationContextERKNS_7MessageE+0x2B4) [0x5627e9ea6194]
 mongod(_ZN5mongo19ServiceStateMachine15_processMessageENS0_11ThreadGuardE+0xBA) [0x5627e9eb28ea]
 mongod(_ZN5mongo19ServiceStateMachine15_runNextInGuardENS0_11ThreadGuardE+0x97) [0x5627e9eae297]
 mongod(+0xC316D1) [0x5627e9eb16d1]
 mongod(_ZN5mongo9transport26ServiceExecutorSynchronous8scheduleESt8functionIFvvEENS0_15ServiceExecutor13ScheduleFlagsENS0_23ServiceExecutorTaskNameE+0x1A2) [0x5627eadc2c02]
 mongod(_ZN5mongo19ServiceStateMachine22_scheduleNextWithGuardENS0_11ThreadGuardENS_9transport15ServiceExecutor13ScheduleFlagsENS2_23ServiceExecutorTaskNameENS0_9OwnershipE+0x15F) [0x5627e9ead0ff]
 mongod(_ZN5mongo19ServiceStateMachine15_sourceCallbackENS_6StatusE+0xAF5) [0x5627e9eaf645]
 mongod(_ZN5mongo19ServiceStateMachine14_sourceMessageENS0_11ThreadGuardE+0x23B) [0x5627e9eaff3b]
 mongod(_ZN5mongo19ServiceStateMachine15_runNextInGuardENS0_11ThreadGuardE+0x11D) [0x5627e9eae31d]
 mongod(+0xC316D1) [0x5627e9eb16d1]
 mongod(+0x1B43165) [0x5627eadc3165]
 mongod(+0x21077B4) [0x5627eb3877b4]
 libpthread.so.0(+0x7DE5) [0x7f48c6687de5]
 libc.so.6(clone+0x6D) [0x7f48c63b1bad]
 ----- END BACKTRACE -----
 2018-12-05T00:34:05.838+0000 I CONTROL [main] ***** SERVER RESTARTED *****
 2018-12-05T00:34:05.910+0000 I CONTROL [initandlisten] MongoDB starting : pid=31836 port=27017 dbpath=/mnt/mongo/data 64-bit host=prodmongo-secondary.ql2.com
 2018-12-05T00:34:05.910+0000 I CONTROL [initandlisten] db version v3.6.6
 2018-12-05T00:34:05.910+0000 I CONTROL [initandlisten] git version: 6405d65b1d6432e138b44c13085d0c2fe235d6bd
 



 Comments   
Comment by Danny Hatcher (Inactive) [ 30/Jul/19 ]

Closing due to lack of response.

Comment by Kelsey Schubert [ 18/Mar/19 ]

Hi dharshanr@scalegrid.net,

Sorry for the long delay getting back to you. We haven't been able to reproduce this issue. Have you encountered this segmentation fault since your initial report? If so, could you upload your complete log files and diagnostic.data? This will allow us to continue to investigate.

Thank you,
Kelsey

Comment by Ramon Fernandez Marina [ 05/Dec/18 ]

Thanks for your report dharshanr@scalegrid.net; we're sending this to the Storage team for investigation, please stay tuned.

Cheers,
Ramón.

Generated at Thu Feb 08 04:48:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.