[SERVER-40730] renameCollection within dropCollection causes signal: 11 (Segmentation fault) - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Duplicate
Affects Version/s: 4.0.8
Fix Version/s: None
Component/s: Storage
Labels:
None

Operating System:
ALL
Steps To Reproduce:

Hide

Using mongo 4.0.8 in shard configuration: 4 replicas consisting of 3 or 2 members with arbiter. Ubuntu 16.04 in docker.

Not quite sure how to reproduce, because on 4.0.8 version we were working for more than two weeks and all were ok until yesterday.

Show
Using mongo 4.0.8 in shard configuration: 4 replicas consisting of 3 or 2 members with arbiter. Ubuntu 16.04 in docker. Not quite sure how to reproduce, because on 4.0.8 version we were working for more than two weeks and all were ok until yesterday.
Sprint:
Storage NYC 2019-05-06

Description

Yesterday got crash of one node with error:
2019-04-18T12:30:01.397+0300 F - [conn577437] Invalid access at address: 0
2019-04-18T12:30:01.602+0300 F - [conn577437] Got signal: 11 (Segmentation fault).
Replica changed primary and at night we got another crash with same error on this new primary.
Parts of logs with crashes are included

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

diagnostic.data.z01
140.00 MB
Apr 21 2019 09:53:58 AM UTC
diagnostic.data.z02
140.00 MB
Apr 21 2019 09:53:57 AM UTC
diagnostic.data.zip
115.79 MB
Apr 21 2019 09:53:52 AM UTC
rs0-0.log
8 kB
Apr 19 2019 10:58:34 AM UTC
rs0-2.log
8 kB
Apr 19 2019 10:58:34 AM UTC

Issue Links

duplicates

SERVER-39419 Stepdown interrupting a running dropDatabase command could leave unclean state

Closed

Activity

People

Assignee:: Benety Goh

Reporter:: Yuriy [X]

Participants:: Benety Goh, Eric Sedor, Yuriy [X]

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: Apr 19 2019 10:59:07 AM UTC

Updated:: May 01 2019 03:25:50 PM UTC

Resolved:: May 01 2019 03:25:50 PM UTC