Change ID generation approach for housekeeper table to improve performance of parallel API requests to delete

    • S25-W26/27, S25-W28/29, S25-W30/31, S25-W34/35, S25-W36/37, S25-W38/39, S25-W42/43, S25-W44/45, S25-W46/47, S25-W48/49, S25-W50/51/52/01
    • 5

      Currently when deleting large amount of items or triggers which may caused when deleting different hosts in parallel API requests, for example, often locks to "housekeeper" row of "ids" table occurred for the first API request.

      The proposed solution is to use CUID-type IDs or native DBMS ID generation approach (bigserial (for Postgres) or AUTO_INCREMENT (for MySQL)) for primary key's field values, instead of "ids" table row. 

            Assignee:
            Vladimirs Maksimovs
            Reporter:
            Vladimirs Maksimovs
            Team C
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 155h 35m
                155h 35m