Details

    Description

      Galera Cluster version 3, has strict inconsistency policy: all transaction replication errors cause emergency abort for all nodes detecting the inconsistency.

      Galera Cluster 4 has more sophisticated inconsistency strategy where cluster runs inconsistency voting protocol and optimizes the way cluster reacts to detected inconsistency. With consistency voting, Galera Cluster can mitigate the harm of inconsistency for the cluster. In the best case, only one node has to abort, and majority can continue operating normally However, if the database has been inconsistent, for indefinitely long period, and application business logic may have been hurt

      Attachments

        Issue Links

          Activity

            jplindst Jan Lindström (Inactive) created issue -
            jplindst Jan Lindström (Inactive) made changes -
            Field Original Value New Value
            ralf.gebhardt Ralf Gebhardt made changes -
            Epic Link PT-78 [ 68559 ]
            jplindst Jan Lindström (Inactive) made changes -
            Labels tests
            ralf.gebhardt Ralf Gebhardt made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            julien.fritsch Julien Fritsch made changes -
            jplindst Jan Lindström (Inactive) made changes -
            Fix Version/s 10.5 [ 23123 ]
            Fix Version/s 10.4 [ 22408 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            Epic Link PT-78 [ 68559 ]
            ralf.gebhardt Ralf Gebhardt made changes -
            NRE Projects RM_104_galera RM_removed_104 RM_105_CANDIDATE
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Jan Lindström [ jplindst ] Alexey [ yurchenko ]
            jplindst Jan Lindström (Inactive) made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jplindst Jan Lindström (Inactive) made changes -
            Assignee Alexey [ yurchenko ] Jan Lindström [ jplindst ]
            jplindst Jan Lindström (Inactive) made changes -
            issue.field.resolutiondate 2019-08-28 06:21:00.0 2019-08-28 06:21:00.609
            jplindst Jan Lindström (Inactive) made changes -
            Fix Version/s 10.5.0 [ 23709 ]
            Fix Version/s 10.5 [ 23123 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            jplindst Jan Lindström (Inactive) made changes -
            Description Test suites:
            * galera_ee
            * galera_3nodes_ee
            Galera Cluster 4 has more sophisticated inconsistency strategy where cluster runs inconsistency voting protocol and optimizes the way cluster reacts to detected inconsistency. With consistency voting, Galera Cluster can mitigate the harm of inconsistency for the cluster. In the best case, only one node has to abort, and majority can continue operating normally However, if the database has been inconsistent, for indefinitely long period, and application business logic may have been hurt
            jplindst Jan Lindström (Inactive) made changes -
            Description Galera Cluster 4 has more sophisticated inconsistency strategy where cluster runs inconsistency voting protocol and optimizes the way cluster reacts to detected inconsistency. With consistency voting, Galera Cluster can mitigate the harm of inconsistency for the cluster. In the best case, only one node has to abort, and majority can continue operating normally However, if the database has been inconsistent, for indefinitely long period, and application business logic may have been hurt Galera Cluster version 3, has strict inconsistency policy: all transaction replication errors cause emergency abort for all nodes detecting the inconsistency.

            Galera Cluster 4 has more sophisticated inconsistency strategy where cluster runs inconsistency voting protocol and optimizes the way cluster reacts to detected inconsistency. With consistency voting, Galera Cluster can mitigate the harm of inconsistency for the cluster. In the best case, only one node has to abort, and majority can continue operating normally However, if the database has been inconsistent, for indefinitely long period, and application business logic may have been hurt
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 89048 ] MariaDB v4 [ 133661 ]

            People

              jplindst Jan Lindström (Inactive)
              jplindst Jan Lindström (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.