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

Server audit won't log the replication process at replication slave

Details

    • 10.1.22

    Description

      I have one replication slave at my site, and I enable the server audit plug-in at slave server.

      I think there are many replication log (binlog replay) in the server audit log, but there is only the operations that on slave server will be logged.

      If I want to log the replication log replayed process, is the server audit plug-in will be done?

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          sujunmin Su, Jun-Ming created issue -
          elenst Elena Stepanova made changes -
          Field Original Value New Value
          Fix Version/s 10.1 [ 16100 ]
          Assignee Alexey Botchkov [ holyfoot ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Sprint 10.1.22 [ 143 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Rank Ranked lower
          serg Sergei Golubchik made changes -
          Summary Server audit wont log the replication process at replication slave Server audit won't log the replication process at replication slave
          serg Sergei Golubchik made changes -
          Affects Version/s 10.1.18 [ 22110 ]
          Environment Windows 2012 Standard 64 bits
          MariaDB 10.1.18
          Issue Type Bug [ 1 ] Task [ 3 ]
          serg Sergei Golubchik made changes -
          Fix Version/s 10.1 [ 16100 ]
          serg Sergei Golubchik made changes -
          ralf.gebhardt Ralf Gebhardt made changes -
          ralf.gebhardt Ralf Gebhardt added a comment -

          The audit for such changes should be done on the master from my point of view. In which case would auditing of the slave be different to an audit of the master?

          ralf.gebhardt Ralf Gebhardt added a comment - The audit for such changes should be done on the master from my point of view. In which case would auditing of the slave be different to an audit of the master?
          sujunmin Su, Jun-Ming added a comment -

          Thanks for your responding.

          I have 2 reasons for this issue.

          1. Prevent the performance of master server low.
          Because of the performance of master server and needed to do audit (for information scecurity process), I want to do audit on read-only slave server because all master server operation will be replayed on slave server.

          2. Troubleshoot for delayed slave serer.
          Because of solving the problem for delayed slave server, I need to check the replay process on all transation from master server, it is convinent for me to read audit logs.

          sujunmin Su, Jun-Ming added a comment - Thanks for your responding. I have 2 reasons for this issue. 1. Prevent the performance of master server low. Because of the performance of master server and needed to do audit (for information scecurity process), I want to do audit on read-only slave server because all master server operation will be replayed on slave server. 2. Troubleshoot for delayed slave serer. Because of solving the problem for delayed slave server, I need to check the replay process on all transation from master server, it is convinent for me to read audit logs.
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 78845 ] MariaDB v4 [ 130569 ]
          ralf.gebhardt Ralf Gebhardt made changes -
          Fix Version/s N/A [ 14700 ]
          Assignee Alexey Botchkov [ holyfoot ]
          Resolution Won't Do [ 10201 ]
          Status Open [ 1 ] Closed [ 6 ]

          People

            Unassigned Unassigned
            sujunmin Su, Jun-Ming
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.