[SERVER-44815] Adding arbiter to PSS deployment using mmap causes 4.0.13 server to segfault Created: 24/Nov/19  Updated: 19/Dec/19  Resolved: 19/Dec/19

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

Type: Bug Priority: Major - P3
Reporter: Oleg Pudeyev (Inactive) Assignee: Dmitry Agranat
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-43079 failpoint triggered by LogicalSession... Closed
depends on PYTHON-1948 Test retryable reads on MMAPv1 Backlog
Duplicate
is duplicated by SERVER-43079 failpoint triggered by LogicalSession... Closed
Related
is related to RUBY-2023 mmap/mlaunch evergreen configurations... Closed
Backwards Compatibility: Fully Compatible
Operating System: Linux
Participants:

 Description   

In the Ruby driver test suite we have had mmapv1 configurations on 4.0 servers. These are tested in standalone and RS (PSS) topologies and have worked fine up to yesterday.

Yesterday I added an arbiter to the replica set topologies to test handshake/authentication against arbiters. This is causing segfaults in mongods in the mmapv1 deployments.

Build 1: https://evergreen.mongodb.com/build/mongo_ruby_driver_mmapv1__mongodb_version~4.0_topology~replica_set_ruby~ruby_2.6_os~rhel70_storage_engine~mmapv1_patch_8cf29a2bc69e3e6f6cba0dfe658c978f5dc7ef8d_5dd981d51e2d176959d58768_19_11_23_19_00_39/

Build 2: https://evergreen.mongodb.com/build/mongo_ruby_driver_mmapv1__mongodb_version~3.6_topology~replica_set_ruby~ruby_2.6_os~rhel70_storage_engine~mmapv1_patch_8cf29a2bc69e3e6f6cba0dfe658c978f5dc7ef8d_5dd981d51e2d176959d58768_19_11_23_19_00_39/

If you look at the server logs, 2 out of 3 mongods in each build have died with segfaults. The remaining mongod is unable to establish a primary hence the test suite fails from that point on.

Please disregard the claimed 3.6 server version, both builds are using 4.0.13.

What additional information do I need to provide?


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