Wait to acquire lock on t5memory queries

XMLWordPrintable

    • High
    • None
    • Wait to acquire lock on t5memory queries to improve user experience in UI
    • None

      Problem

      We do lock on the whole TM as we can't lock records.

      This may cause inability to acquire read lock (for searches) if someone already got write lock (for update in maintenance) and this results in really poor UX.

      Solution

      We have to wait a bit to non-blocking acquire of lock. Maybe ~20 sec or so.

      This will allow user to get shared lock if someone doing relatively fast mutations (like update) and still get an error if TM is really busy (like import or reorganise)

            Assignee:
            Sanya Mikhliaiev
            Reporter:
            Sanya Mikhliaiev
            None
            None
            Leon Kiz, Stephan Bergmann, Sylvia Schumacher
            Leon Kiz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None