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

Shard map refresh is not logged on any level

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.11
    • Fix Version/s: 2.5.4
    • Component/s: schemarouter
    • Labels:
      None

      Description

      Folks,

      Working with an initially simple sharding with 10 servers/backends, I got the following variables added to a basic configuration file (/etc/maxscale.cnf):

      refresh_databases=1
      refresh_interval=5
      

      The refresh_interval configured as 5 seconds is too low for the number of database schemas which are going to be added and removed from the shardings. I'm planning to increase that value as I see lots of resources being spent by that activity.

      The primary goal here is that I can't see any events being added to the log, even enabling the log-priority info, I can't see any mapping refresh, any re-mapping due to a lousy database context change (when you do a bad USE <non-existing-db>.

      Is it possible to add that information over a notice class in the log file?

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            wagnerbianchi Wagner Bianchi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration