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

[PATCH] group commit status variable addition

Details

    Description

      currently we have a status variable for the total group_commits. This compromises of group commits due to binlog_commit_wait_count, binlog_commit_wait_usec or indeed conflicting transactions that need to be in a separate group.

      Showing a breakdown as to the reason of the group commit will enable a more informed tuning of the system variables controlling the group commit and also identify how often these aren't taking part in the group determination.

      patch: https://github.com/MariaDB/server/pull/30

      Attachments

        Issue Links

          Activity

            Pushed to 10.1.5. Thanks, Daniel!

            knielsen Kristian Nielsen added a comment - Pushed to 10.1.5. Thanks, Daniel!
            danblack Daniel Black added a comment -

            Pushed to 10.1.5. Thanks, Daniel!

            Welcome. Thanks for the merge.

            Any chance of getting this into 10.0? seems like the most invasive bit is the extra brief lock on LOCK_prepare_ordered when when fetching status variables.

            danblack Daniel Black added a comment - Pushed to 10.1.5. Thanks, Daniel! Welcome. Thanks for the merge. Any chance of getting this into 10.0? seems like the most invasive bit is the extra brief lock on LOCK_prepare_ordered when when fetching status variables.
            danblack Daniel Black added a comment -

            I've added status variables to the KB.

            danblack Daniel Black added a comment - I've added status variables to the KB.

            > Any chance of getting this into 10.0? seems like the most invasive bit is
            > the extra brief lock on LOCK_prepare_ordered when when fetching status
            > variables.

            Probably you should ask this on the maria-developers@ mailing list. I don't
            personally have any strong opinion one way or the other.

            The "normal" policy is to not introduce new features in stable releases.

            knielsen Kristian Nielsen added a comment - > Any chance of getting this into 10.0? seems like the most invasive bit is > the extra brief lock on LOCK_prepare_ordered when when fetching status > variables. Probably you should ask this on the maria-developers@ mailing list. I don't personally have any strong opinion one way or the other. The "normal" policy is to not introduce new features in stable releases.

            > I've added status variables to the KB.

            Thanks, Daniel, much appreciated.

            knielsen Kristian Nielsen added a comment - > I've added status variables to the KB. Thanks, Daniel, much appreciated.

            People

              knielsen Kristian Nielsen
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.