Operational Defect Database

BugZero found this defect 18 days ago.

MongoDB | 2659793

dropIdent returning EBUSY during rollback_to_stable can crash server

Last update date:

5/1/2024

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

Failing to drop idents for an unfinished index build during recovery does not use the ident reaper and return any drop ident failure to higher level. As part of rollback to stable we re-open the catalog and restart unfinished index builds as needed. As we are in rollback to stable we're not able to modify the catalog (as we cannot perform timestamped writes) we'll reuse the ident name by dropping the previous ident and re-creating a new with the same name. Link. However, if dropping this ident fails, the status is returned and eventually converted to an exception here causing the catalog to not finish its setup as we throw here. This is completely unrecoverable and leads to further exceptions being thrown which terminates the process as we're already handling an existing exception (the failure to start the index build due to the failure to drop the ident)

Top User Comments


Steps to Reproduce


Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Needs Scheduling

Learn More

Search:

...