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

Query Cache on Primary-Secondary-Secondary not invalidated on updates

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.5.13
    • 10.5.14
    • Query Cache, Replication
    • None
    • bitnami/mariadb Helm Chart on Kubernetes running on Linux

    Description

      When running Primary-Secondary-Secondary setup DML operations on Primary do not trigger query caches on Secondaries to be invalidated when binary log is in ROW format.

      Reproduce as follows (given a table ):

      On Primary:

      insert into test values (123);
      select * from test; #=> gives 123
      

      On Secondaries:

      select * from test; => gives nothing
      select * from test where 1=1; # or select SQL_NO_CACHE * from test; => gives 123
      

      Excerpt from my.cnf for Primary and Secondaries:

      binlog_format=row
      query_cache_type=1
      query_cache_limit=4M
      query_cache_size=256M
      

      Attachments

        Issue Links

          Activity

            Have been able to reproduce on 10.5.13 with primary --> replica. Still need to check other versions and write up test case...

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - Have been able to reproduce on 10.5.13 with primary --> replica. Still need to check other versions and write up test case...

            I tested this with 10.5.15 and could not see the behavior with a primary server and two replicas (and could see it with 10.5.13). I later stumbled upon MDEV-27047, which I believe this bug duplicates. I made the assumption that the replication geometry was simple, with the primary replicating to two replicas who are unaware of each other, but I could test again if the geometry is something a bit more complicated, say one replica is in between the primary and second replica (however, I still think the issue would still be the same as MDEV-27047).

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - I tested this with 10.5.15 and could not see the behavior with a primary server and two replicas (and could see it with 10.5.13). I later stumbled upon MDEV-27047 , which I believe this bug duplicates. I made the assumption that the replication geometry was simple, with the primary replicating to two replicas who are unaware of each other, but I could test again if the geometry is something a bit more complicated, say one replica is in between the primary and second replica (however, I still think the issue would still be the same as MDEV-27047 ).

            tbienias could I please verify the exact setup of the primary and two replicas to test this and see if it is a duplicate bug or not? Thank you.

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - tbienias could I please verify the exact setup of the primary and two replicas to test this and see if it is a duplicate bug or not? Thank you.

            Could this be a duplicate of MDEV-27047, which affected 10.5.13 and 10.6.5 and was fixed in 10.5.14 and 10.6.6?

            marko Marko Mäkelä added a comment - Could this be a duplicate of MDEV-27047 , which affected 10.5.13 and 10.6.5 and was fixed in 10.5.14 and 10.6.6?

            Could this be a duplicate of MDEV-27047, which affected 10.5.13 and 10.6.5 and was fixed in 10.5.14 and 10.6.6?

            Yes, I wrote this above.

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - Could this be a duplicate of MDEV-27047 , which affected 10.5.13 and 10.6.5 and was fixed in 10.5.14 and 10.6.6? Yes, I wrote this above.

            tbienias please try upgrading to 10.5.14. I will resolve this bug as a Duplicate for now.

            angelique.sklavounos Angelique Sklavounos (Inactive) added a comment - tbienias please try upgrading to 10.5.14. I will resolve this bug as a Duplicate for now.

            People

              angelique.sklavounos Angelique Sklavounos (Inactive)
              tbienias Tim Bienias
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.