[SERVER-40184] Crash in server after bulk write error Created: 18/Mar/19  Updated: 06/Dec/22  Resolved: 18/Mar/19

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

Type: Bug Priority: Major - P3
Reporter: John Stewart (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongos_27017.log    
Issue Links:
Duplicate
duplicates SERVER-40052 Shutdown in mongos can trigger BatchW... Closed
Assigned Teams:
Sharding
Operating System: ALL
Steps To Reproduce:

I am creating the sharded cluster using mlaunch:
{{ VERSION=4.1.9}}
{{ MONGO_PATH=/usr/local/m/versions/${VERSION}/bin}}mlaunch --binarypath ${MONGO_PATH} --replicaset --name "repl0" --sharded a1 a2 a3 --mongos 3 --dir ~/dbData --setParameter enableTestCommands=1 -vvvv

So far, I can only reproduce this on my Macbook by running the transactions test runner for the Java driver.

Participants:

 Description   

While testing my implementation for sharded transaction recovery token using the transactions tests in the Java driver, the server crashes on one of the tests.

My Macbook unexpectedly shut down, and after restarting, the crash occurs on a transactions test.

When running the transactions test, the log shows the expected `WriteConflict` error, followed immediately by an abort. I am attaching the log file that contains the abort and stack trace.

 



 Comments   
Comment by Kaloian Manassiev [ 18/Mar/19 ]

This is a duplicate of another sequence, which also causes the same issue SERVER-40052, so I am closing it as duplicate.

john.stewart, since your repro steps are easier I am going to copy them to SERVER-40052, thank you!

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