Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7725

Spiral patch 028_mariadb-10.0.15.xa_commit_error.diff

Details

    Attachments

      Activity

        svoj Sergey Vojtovich created issue -
        svoj Sergey Vojtovich made changes -
        Field Original Value New Value
        Epic Link MDEV-7698 [ 50410 ]
        serg Sergei Golubchik made changes -
        Fix Version/s 10.1 [ 16100 ]
        svoj Sergey Vojtovich made changes -
        Assignee Sergey Vojtovich [ svoj ]

        Since in 2PC commit is not supposed to fail serg suggests that:
        1. Spider should crash the server whenever it gets an error.
        2. Use less error prone storage for XID's.

        svoj Sergey Vojtovich added a comment - Since in 2PC commit is not supposed to fail serg suggests that: 1. Spider should crash the server whenever it gets an error. 2. Use less error prone storage for XID's.
        svoj Sergey Vojtovich made changes -
        Component/s Storage Engine - Spider [ 10132 ]
        Fix Version/s 10.1.5 [ 18813 ]
        Fix Version/s 10.1 [ 16100 ]
        Resolution Won't Fix [ 2 ]
        Status Open [ 1 ] Closed [ 6 ]
        ratzpo Rasmus Johansson (Inactive) made changes -
        Workflow MariaDB v2 [ 60052 ] MariaDB v3 [ 67008 ]
        alvinr Alvin Richards (Inactive) made changes -
        Labels NRE-305367
        alvinr Alvin Richards (Inactive) made changes -
        NRE Projects NRE-305367
        alvinr Alvin Richards (Inactive) made changes -
        Labels NRE-305367
        serg Sergei Golubchik made changes -
        Workflow MariaDB v3 [ 67008 ] MariaDB v4 [ 132557 ]

        People

          svoj Sergey Vojtovich
          svoj Sergey Vojtovich
          Votes:
          0 Vote for this issue
          Watchers:
          3 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.