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

Do not let pinloki trigger the watchdog during file reading

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • None
    • 6.1.2
    • pinloki
    • None

    Description

      If a large amount of data has been read to pinloki files, the pinloki file reader may take longer than the watchdog timeout during startup.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          YK Yakov Kushnirsky added a comment -

          Marcus & Niclas thank you for taking on this and commenting!
          I will then ask the customer to try comment out

          WatchdogSec=30s
          NotifyAccess=all

          in /lib/systemd/system/maxscale.service? Or at least increase, e.g. WatchdodSec=300s

          YK Yakov Kushnirsky added a comment - Marcus & Niclas thank you for taking on this and commenting! I will then ask the customer to try comment out WatchdogSec=30s NotifyAccess=all in /lib/systemd/system/maxscale.service? Or at least increase, e.g. WatchdodSec=300s
          nantti Niclas Antti added a comment -

          Dup MXS-3570

          nantti Niclas Antti added a comment - Dup MXS-3570

          People

            nantti Niclas Antti
            nantti Niclas Antti
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.