[Bug] Faster Log Devices don't Release Lock on File After Dispose.
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.6k
- Forks
- 595
- PR merge metrics
- No merged PRs in 30d
Description
Running
_store.Log.FlushAndEvict(true);
_store.Dispose();
FasterDb still has a lock on the device files. Files are only freed when you exit process.
Exception
System.IO.IOException: The process cannot access the file 'DATA.0' because it is being used by another process.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the FlushAndEvict(true) and Dispose sequence shown in the report, then inspect how disposal handles the DATA.0 device file. Confirm the fix by verifying that the file can be opened or deleted after disposal, and add a regression test if the existing test layout provides a suitable location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100