-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Block Manager
-
None
-
Storage Engines
-
None
-
None
To support current testing it would be useful to keep retrying if WT can't read a page in the disagg block manager.
Currently the reread loop in __block_disagg_read_multiple retries 100 times, sleeping between retries for a gradually increasing amount of time, and then returns EIO if it has failed to read the page after 100 tries. So we just want to keep trying at a slow pace.
- is related to
-
WT-15432 Coverity analysis defect 176691: Invalid type in argument to printf format specifier
-
- Closed
-
-
WT-15697 Change all python layered tests to use a configurable PALI
-
- Closed
-
-
WT-15589 Verify each read we do is behind the page materialisation frontier
-
- Open
-
-
WT-15718 Favour internal SQLite3 library during build
-
- Closed
-
-
WT-15734 Consider removing the layered manager thread
-
- Closed
-
- related to
-
WT-15560 Assertion fail - test/format with precise checkpoint
-
- Closed
-
-
WT-15678 Memory leak in __wti_block_disagg_write_internal
-
- Closed
-
-
WT-15246 Re-enable prepared testing that depends on new delta data format
-
- Closed
-
-
WT-15522 Configure the error log from cmake & determine the default value
-
- Closed
-
-
WT-15720 Handle stepdowns in test/format by restarting WT before stepping down
-
- Closed
-
-
WT-15736 Split "maximum page size seen at eviction" to 3 seperate statistics
-
- Closed
-
-
WT-15768 Update/remove infinite retry loop in disagg block. manager
-
- Needs Scheduling
-
-
WT-15629 (disagg.mode=leader) Test/format key OOO (internal page delta)
-
- Closed
-
-
WT-15682 Increase the read timestamp lag to avoid conflict with prepare timestamp
-
- Closed
-