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

Improve log msg about the maxscale startup process

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.1.15
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-53

      Description

      We need to improve log msg about the maxscale startup process so we can know how many listeners are started and how many are left and if remaining are failed then what was the reason? Recently, we saw one issue where maxscale was not starting and giving error like "error : [binlogrouter] Could not post ' ' message to main worker"

      The reason behind it was, while having multiple listeners, it was taking time to load all user data from the backend servers. The default value of TimeoutStartSec in maxscale.service for MaxScale is 120. If all listeners do not start before 120 seconds then it got timed out but we didn't get this information in maxscale log. More descriptive log message will help a lot.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            niljoshi Nilnandan Joshi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration