Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12071 Official support for CockroachDB
  3. CAM-12232

Disable pessmistic locks on CRDB and do retries instead

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 7.14.0, 7.14.0-alpha3
    • None
    • engine
    • None

      • Pessimistic locks as we use them do not help us due to serializable isolation level => after the pessimistic lock unblocks, the tx still sees old data; it only fails when it tries to do a conflicting modification
      • Idea: we disable pessimistic locks for CRDB. This will lead to more failures in the corresponding commands (e.g. parallel deployment during server startup) => it should be possible to configure the retry interceptor for these cases

      Pessimistic locks are used in the following scenario:

      • create history cleanup jobs
      • deployment
      • telemetry
      • installation id
      • message correlation

      We can support retries in the following scenarios:

      • create history cleanup jobs
      • deployment
      • telemetry
      • installation id

      Retries for exclusive message correlation are useless, because the purpose of the feature is that the business logic during message correlation is guaranteed to run only once.

      We should write appropriate test cases and once more confirm that without the pessimistic locks, nothing bad happens.

        This is the controller panel for Smart Panels app

              nikola.koevski Nikola Koevski
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: