-
Type: Task
-
Resolution: Done
-
None
-
Affects Version/s: None
-
Component/s: None
Sometimes opening a bulk cursor on an empty table can return EBUSY. The particular trigger appears to be when a checkpoint is started after the table create, and running when the bulk cursor open call happens.
We should generate a test case to reproduce the behavior, and fix it so that EBUSY isn't returned.
- related to
-
WT-1 placeholder WT-1
- Closed
-
WT-2 What does metadata look like?
- Closed
-
WT-3 What file formats are required?
- Closed
-
WT-4 Flexible cursor traversals
- Closed
-
WT-5 How does pget work: is it necessary?
- Closed
-
WT-6 Complex schema example
- Closed
-
WT-7 Do we need the handle->err/errx methods?
- Closed
-
WT-1398 Don't fail to open bulk cursors because a checkpoint is running
- Closed
-
WT-1399 Switch to holding the checkpoint lock when opening a bulk cursor.
- Closed