[SERVER-31657] improve assert.soon function logging in implicitly_retry_on_database_drop_pending.js Created: 20/Oct/17  Updated: 01/Jan/18  Resolved: 01/Jan/18

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Max Hirschhorn
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-32095 Attach client.application.name to con... Closed
Participants:
Linked BF Score: 0

 Description   

The FSM suite retries certain CRUD operations on receiving a DatabaseDropPending error from the server. In build failures with multiple dropDatabase invocations and timeout errors on CRUD operations, it would be useful to know when the CRUD operation started. One place where this information would help is in the following log message:

insert command failed due to the plan_cache_drop_database database being marked as drop-pending. Waiting for th
e latest operation to become majority confirmed before trying again.

This log message is printed here:

https://github.com/mongodb/mongo/blob/0966ba7c98dcd47d6fff753cf380d1c38c2c3d2b/jstests/libs/override_methods/implicitly_retry_on_database_drop_pending.js#L153



 Comments   
Comment by Max Hirschhorn [ 01/Jan/18 ]

The changes proposed in SERVER-32095 should be able to provide sufficient context to associate an FSM worker thread with its corresponding server connection, so I'm closing this ticket as "Won't fix". The issue with the implicitly_retry_on_database_drop_pending.js override has been reported in SERVER-32497.

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