Consider moving weakened standalone barriers to production

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - Q3+ Backlog
    • None

      This ticket is an umbrella ticket for investigating the long term solution for dealing with TSAN warnings caused by standalone barriers. As for the moment of the ticket creation, TSAN doesn't support standalone fences so they could cause false positive warnings. 

      The best option to deal with that warnings for now is to weaken them by replacing with atomic operations if possible. However, weakening the lock-free algorithm is not in the scope SPM-3838 so they should be weakened under TSAN build macro only. Each such decision should be coupled with FIXME linked to this ticket.

      The scope of this ticket is to search all the FIXMEs related and reconsider moving this weakening to the production. We should be especially careful there since memory synchronisation could be extremely unobvious in these places.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: