Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Fix Version/s: 10.0.9
    • Component/s: None
    • Labels:
      None

      Description

      There is relationship between LOCK_flush and LOCK_open. Even though it is not on a hot path, it indirectly interferes with TABLE_SHARE::tdc.flushed. The latter is on hot path and will eventually be moved out of LOCK_open.

      The sole purpose of LOCK_flush is to let tdc_remove_table() wait for concurrent FLUSH TABLES. Replace global rwlock with per-share condition variable.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                svoj Sergey Vojtovich
                Reporter:
                svoj Sergey Vojtovich
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 40 minutes
                  40m