Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3123

Thread group holding lock across thread join

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT2.9.3, 3.5.9
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Storage 2017-03-27, Storage 2017-04-17

      Description

      This is related to WT-3105. There are a few general issues to discuss regarding thread groups that I'd like to discuss with Alexander Gorrod.

      • The fix in WT-3105 means we always call wt_thread_group_start_one and wt_thread_group_stop_one with wait=false. They are currently the only callers of those functions. Should we remove the wait arg and just always do a try lock?
      • Should the thread group shrink code hold the thread group lock across the thread join call? That seems that is a potential problem area in general.
      • The way eviction works is that threads are started/stopped by a thread within the group. If/when we expand the use of thread groups to, say, async or LSM it seems that will continue to be the case (as opposed to some other outside-the-group thread manipulating the group). The latest hang in WT-3105 is general to this question.

        Attachments

          Activity

            People

            • Assignee:
              sue.loverso Susan LoVerso
              Reporter:
              sue.loverso Susan LoVerso
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: