# Issue with audit\_log\_filter component on Replica Nodes in 3-Node MySQL InnoDB Cluster (Percona MySQL 8.4.7) **URL:** \ **Category:** MySQL & MariaDB\ **Tags:** mysql, percona\ **Created:** [March 27, 2026, 9:49am UTC](https://forums.percona.com/t/issue-with-audit-log-filter-component-on-replica-nodes-in-3-node-mysql-innodb-cluster-percona-mysql-8-4-7/40412 "2026-03-27T09:49:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Dhivya\_Arumugam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dhivya_arumugam/32/21210_2.png) [@Dhivya\_Arumugam](https://forums.percona.com/u/Dhivya_Arumugam)\ **Post date:** [March 27, 2026, 9:49am UTC](https://forums.percona.com/t/issue-with-audit-log-filter-component-on-replica-nodes-in-3-node-mysql-innodb-cluster-percona-mysql-8-4-7/40412/1 "2026-03-27T09:49:02Z")
Hi Percona Support Team, I am testing the **`audit_log_filter` component of Percona MySQL 8.4.7** on a **3-node MySQL InnoDB Cluster (Group Replication)** setup and have observed inconsistent behavior between the primary and replica nodes. ### Environment - **Database Version:** MySQL CE 8.4.7 - **Topology:** 3-node MySQL InnoDB Cluster (Group Replication) - **Audit Log Filter Component:** `audit_log_filter` component from Percona MySQL 8.4.7 ### Configuration The audit filter rule is created and assigned as follows: ```auto MySQL localhost:3306 ssl SQL > SELECT * FROM mysql.audit_log_filter; +-----------+---------+---------------------------------------------------------------------------------------------------------------------------------+ | filter_id | name | filter | +-----------+---------+---------------------------------------------------------------------------------------------------------------------------------+ | 1 | log_ddl | {"filter": {"rule": {"log": true, "event_class": "query", "command_class": ["create", "alter", "drop", "truncate", "rename"]}}} | +-----------+---------+---------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.0005 sec) MySQL localhost:3306 ssl SQL > SELECT * FROM mysql.audit_log_user; +----------+----------+------------+ | username | userhost | filtername | +----------+----------+------------+ | % | % | log_ddl | +----------+----------+------------+ 1 row in set (0.0006 sec) MySQL localhost:3306 ssl SQL > select audit_log_session_filter_id(); +-------------------------------+ | audit_log_session_filter_id() | +-------------------------------+ | 1 | +-------------------------------+ ``` ### Observed Behavior - On the **primary node** , DDL operations are correctly captured in the audit log. - On the **replica nodes** , **no audit entries are generated** even though: ### Additional Observation When attempting to reload the filters on the replica: ```auto SELECT audit_log_filter_flush(); ``` The following error is returned: ```auto ERROR: Could not reinitialize audit log filters ``` ### Expected Behavior Since the filter metadata tables are replicated across the cluster, the audit plugin on replica nodes should load the filters and log the relevant events locally. ### Actual Behavior Replica nodes do not generate audit logs despite having the filter configuration present. ---
**Author:** ![Dhivya\_Arumugam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dhivya_arumugam/32/21210_2.png) [@Dhivya\_Arumugam](https://forums.percona.com/u/Dhivya_Arumugam)\ **Post date:** [March 28, 2026, 2:05am UTC](https://forums.percona.com/t/issue-with-audit-log-filter-component-on-replica-nodes-in-3-node-mysql-innodb-cluster-percona-mysql-8-4-7/40412/2 "2026-03-28T02:05:33Z")
I have filed a new bug report ([Jira](https://perconadev.atlassian.net/browse/PS-10988)) on this. However, I am unable to edit the description of this jira so i have posted the details in the comment section. ---
**Author:** ![yunus.uyanik](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus.uyanik/32/19250_2.png) [@yunus.uyanik](https://forums.percona.com/u/yunus.uyanik)\ **Post date:** [March 30, 2026, 12:08pm UTC](https://forums.percona.com/t/issue-with-audit-log-filter-component-on-replica-nodes-in-3-node-mysql-innodb-cluster-percona-mysql-8-4-7/40412/3 "2026-03-30T12:08:36Z")
Hi, The installation script includes `INSTALL COMPONENT 'file://component_audit_log_filter';` and this won’t be transferred like any other component installation or config changes either. How did you perform the installation for other nodes? Also, you mentioned the database version is MySQL CE 8.4.7, which is an enterprise feature in upstream MySQL. ---
**Author:** ![Dhivya\_Arumugam](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dhivya_arumugam/32/21210_2.png) [@Dhivya\_Arumugam](https://forums.percona.com/u/Dhivya_Arumugam)\ **Post date:** [March 30, 2026, 12:48pm UTC](https://forums.percona.com/t/issue-with-audit-log-filter-component-on-replica-nodes-in-3-node-mysql-innodb-cluster-percona-mysql-8-4-7/40412/4 "2026-03-30T12:48:16Z")
Hello Yunus, For the replica nodes, we temporarily disabled `read_only` and then executed the component installation manually using: INSTALL COMPONENT ‘file://component\_audit\_log\_filter’; After the installation completed, we re-enabled `read_only` on the replica nodes. However, we are observing that the issue still occurs specifically on replica servers running the **Percona MySQL 8.4.7 distribution**. The same behavior is described in the [ticket](https://perconadev.atlassian.net/browse/PS-10137?focusedCommentId=451841) comment we referenced earlier.