Please introduce the same "gating" mechanism that was inplemented on BSERV-9417 for updates on sta_remember_me_token

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: None
    • None
    • 5
    • 11

      In BSERV-9417: Reduce Database load by 'gating' the number of non-critical updates done (fixed in Bitbucket Server 4.13.0) we introduced a "gating" mechanism to prevent issues on the tables that are updated frequently, however this did not include sta_remember_me_token updates.

      There are cases being reported where if a VIP has multiple SNAT Ips, it will invalidate the token and cause deadlocks on the database:

      2018-11-25 09:16:32,624 WARN [http-nio-7990-exec-11] *91TLAEx556x281319x3 10.34.113.41,10.33.168.133 "GET /rest/chaperone/1/chaperone/watch-repository HTTP/1.1" o.h.e.jdbc.spi.SqlExceptionHelper SQL Error: 0, SQLState: 40P01
2018-11-25 09:16:32,624 ERROR [http-nio-7990-exec-11] *91TLAEx556x281319x3 10.34.113.41,10.33.168.133 "GET /rest/chaperone/1/chaperone/watch-repository HTTP/1.1" o.h.e.jdbc.spi.SqlExceptionHelper ERROR: deadlock detected
Detail: Process 27867 waits for ShareLock on transaction 320331793; blocked by process 27869.
Process 27869 waits for ShareLock on transaction 320331794; blocked by process 27867.
Hint: See server log for query details.
Where: while deleting tuple (142,56) in relation "sta_remember_me_token"

      Please introduce the same "gating" mechanism that was inplemented on BSERV-9417 for updates on sta_remember_me_token

            Assignee:
            Unassigned
            Reporter:
            Andre Marques (Inactive)
            Votes:
            6 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: