There are some configurations that result in verifying the metadata that get EBUSY. The problem is when the metadata is bulk loaded in wt_turtle_init, it leaves a metadata cursor open in the session and that is readlocked. Then, when we go to verify later and get a write lock, we get EBUSY because we already hold a read lock.
- Assignee:
- Susan LoVerso
- Reporter:
- Susan LoVerso
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated:
- Resolved: