Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-2745

User loading is limited at startup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:
      SkySQL Dev/Test

      Description

      Original title: SkySQL:Data inconcistencies observed in replicas after upgrade to maxscale:2.4.2

      After upgrade from maxscale:2.3.9 to maxscale to maxscale:2.4.2 in SkySQL, we started observing replicas data inconsistencies in the scenario of topology initialization followed by immediate data load.

      Detail of these issues can be found here:
      https://jira.mariadb.org/browse/DBAAS-1319
      https://jira.mariadb.org/browse/DBAAS-1318

      We did a bit of a research on our end investigating possible root cause in various moving parts - test clusters/topologies setup , operator/K8s, etc.
      were not able to find anything obvious, apart from the maxscale migration from 2.3.9 to 2.4.2

      So far we tried a couple of suggestion from the MaxScale team :

      • Consistent Critical Read Filter
      • Using Causal reads
        unfortunately without much of a success.

      Please advice, if you need further detail on the issue or any other form of support we can provide you with to speed up the resolution process

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            nedyalko.petrov Nedyalko Petrov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: