Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-64498

Check for both cache-full and rollback when the application uses cache_max_wait_ms

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • Execution Team 2022-04-04

      WT-8767 is going to make a change where the application threads set to timeout after a duration of waiting on eviction will return a WT_ROLLBACK instead of WT_CACHE_FULL. In WiredTigerRecordStore::_initNextIdIfNeeded when trying to determine the largest record id we check the return of WT_CACHE_FULL. This will break once WT-8767 will be merged to MongoDB.

      To help with the transition from cache full error to the rollback, this ticket should make the above code check for both WT_CACHE_FULL and WT_ROLLBACK.

      A follow on ticket, SERVER-64461, is filed to take on from there, and do other changes needed to handle the WT_ROLLBACK return with a new rollback reason.

            yujin.kang@mongodb.com Yujin Kang Park
            sulabh.mahajan@mongodb.com Sulabh Mahajan
            0 Vote for this issue
            5 Start watching this issue