Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-11920

Camunda provides a mode that MariaDB Galera Cluster does not support.

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • 7.13.0
    • documentation
    • None
    • Camunda docs

      Camunda provides a mode that MariaDB Galera Cluster does not support.

       

        This is the controller panel for Smart Panels app

          1. 11.PNG
            11.PNG
            102 kB
          2. 22.PNG
            22.PNG
            105 kB

            [CAM-11920] Camunda provides a mode that MariaDB Galera Cluster does not support.

            Hi lucky dog,

            Thank you for the bug report. It seems like Camunda only supports the loadbalance mode. I will forward this ticket for scheduling.

            In the meantime, feel free to submit a PR that fixes this issue.

            Best,
            Nikola

            Nikola Koevski added a comment - Hi lucky dog , Thank you for the bug report. It seems like Camunda only supports the loadbalance mode. I will forward this ticket for scheduling. In the meantime, feel free to submit a PR that fixes this issue. Best, Nikola

            lucky dog added a comment -

            I found that failover is the alias of loadbalance, and I concurrently tested that my flow (including message events, tiemer events) is normal in sequential mode, why do you say Camunda only supports the loadbalance mode?

            lucky dog added a comment - I found that failover is the alias of loadbalance, and I concurrently tested that my flow (including message events, tiemer events) is normal in sequential mode, why do you say Camunda only supports the loadbalance mode?

            Nikola Koevski added a comment - - edited

            Hey lucky dog,

            Sorry, I completely mixed up the modes in my last reply. I missed the MariaDB docs statement that failover is the alias of the loadbalance mode:

            loadbalance mode docs: Before 2.4.2, this option was named `failover` - alias still exist for compatibility

            In this case, the bug is that we need to clarify the documentation that Camunda supports the loadbalance and sequential modes since failover is an alias of loadbalance. We also need to remove loadbalance from the list of unsupported modes.

            However, it's still unclear why the Camunda docs state the loadbalance and failover modes as separate. Maybe at some point, they were, so this needs to be confirmed before changing the docs.

            Best,
            Nikola

            Nikola Koevski added a comment - - edited Hey lucky dog , Sorry, I completely mixed up the modes in my last reply. I missed the MariaDB docs statement that failover is the alias of the loadbalance mode: loadbalance mode docs: Before 2.4.2, this option was named `failover` - alias still exist for compatibility In this case, the bug is that we need to clarify the documentation that Camunda supports the loadbalance and sequential modes since failover is an alias of loadbalance . We also need to remove loadbalance from the list of unsupported modes. However, it's still unclear why the Camunda docs state the loadbalance and failover modes as separate. Maybe at some point, they were, so this needs to be confirmed before changing the docs. Best, Nikola

            lucky dog added a comment -

            The URL format I use: JDBC: MariaDB: failover://192.168.1.1:32980192.168.1.2:32980192.168.1.3:32980 / process engine,

            I designed a BPMN process, which includes message events and message Association operations, and then I had a deadlock during the concurrent test.

            lucky dog added a comment - The URL format I use: JDBC: MariaDB: failover://192.168.1.1:32980192.168.1.2:32980192.168.1.3:32980 / process engine, I designed a BPMN process, which includes message events and message Association operations, and then I had a deadlock during the concurrent test.

            We are closing this ticket as part of our backlog grooming. Reasons:

            • The environment is not supported anymore

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: The environment is not supported anymore

              thorben.lindhauer Thorben Lindhauer
              lucky dog lucky dog
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: