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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • v4.4
    • Execution Team 2021-05-03
    • 115
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: