-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Foundations
-
487.81
-
None
-
None
If we randomly giving an invalid page id to page_log->plh_get call into PALite, then we'll get inconsistent behaviours (page id from 1 to 3 which is not exist):
- PALI:
- It will first trigger the mechanism of wait for materilisation introduced from SERVER-113585
id=11049803 grpcErrorMsg: "Timed out after 63s waiting for (LogId(100), TableId(2), PageId(3), LSN(7670810701597769742)) to materialize (highest LSN seen for the log is LSN(7670810701597769739))"
- After a long time retry, it will return an error code of 110 (not sure what this means).
- It will first trigger the mechanism of wait for materilisation introduced from SERVER-113585
- PALite
- It will return 0 as success, and count equal to 0.
The result of this leads to the confusion about this part, what expected is when we call plh_get on an page_id that's not exist, the return should be WT_NOTFOUND, but now we got an WT_OK with count = 0 so we need a double check.
So we need a discussion whether we need to align this.