[SERVER-27670] Add more user-friendly error message for EBUSY returns from WiredTiger Created: 12/Jan/17  Updated: 18/May/17  Resolved: 13/Mar/17

Status: Closed
Project: Core Server
Component/s: Storage, WiredTiger
Affects Version/s: None
Fix Version/s: 3.5.5

Type: Improvement Priority: Minor - P4
Reporter: Stennie Steneker (Inactive) Assignee: David Hows
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently the error-messages generated following an EBUSY return from WiredTiger can be very confronting and opaque.

For example, running a full validate on a WiredTiger collection may sometimes return a transient EBUSY error which is very opaque:

verify() returned EBUSY. Not treating as invalid.

This is actually a warning that something else was accessing a file at the same time (eg. a checkpoint); retrying the validate should succeed.

A more user-friendly error message could clarify the affected file and suggested action, eg:

Could not verify collection-0-1763735954797746426.wt as the file was being actively updated. This should be a transient issue: re-run validate to check again.



 Comments   
Comment by Githook User [ 13/Mar/17 ]

Author:

{u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}

Message: SERVER-27670 Improve error messages reported on EBUSY return from WiredTiger
Branch: master
https://github.com/mongodb/mongo/commit/b890af7de045d1d91b01f90a453d81fc6631b29d

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