Ensure Range Deleter Service acquires lock before registering task

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In BF-40795, we see that the memory for UUID gets freed when the range deleter task is removed. The same memory later gets accessed when the op observer tries to register a task. Specifically the memory for the range deleter task id.
      The range deleter service registers a task, by taking the task as a reference rather than a copy. There is likely a concurrent operation that frees the UUID before it gets accessed. 

            Assignee:
            David Chen
            Reporter:
            David Chen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: