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

Internal system threads with kIgnoreConflictsAllWrites set and running wiredTigerPrepareConflictRetry code should not be required to be killable for stepdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2021-05-03
    • Linked BF Score:
      115

      Description

      We set index builds to ignore prepare conflicts using the kIgnoreConflictsAllowWrites setting, which appears to only be used to set a flag on a WT request, but then we also enforce that internal threads can be killed for step-down in order to avoid hangs with said threads hitting prepare conflicts, without any apparent exception for threads that have kIgnoreConflictsAllowWrites set.

      I believe there should be an exception to the client->canKillSystemOperationInStepdown() invariant where internal threads with kIgnoreConflictsAllowWrites set should not be required to be killable.

        Attachments

          Activity

            People

            Assignee:
            dianna.hohensee Dianna Hohensee
            Reporter:
            dianna.hohensee Dianna Hohensee
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: