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

Log warning if reverse name resolution takes significant time

    XMLWordPrintable

    Details

    • Sprint:
      MXS-SPRINT-159, MXS-SPRINT-160

      Description

      Currently it is difficult to diagnose the Maxscale stall due to reverse DNS lookups.

      Customer would like skip_name_resolve default value to be set to true.

      When Slow reverse DNS lookups during authentication cause MaxScale to stall, the log output does not give an indication as to what is happening. Is it possible to add something to the log that indicates starting reverse dns lookup, and ending reverse dns lookup? And/or checking the amount of time that takes and possibly suggesting setting skip_name_resolve to be set to true.

      2022-05-25 16:00:08 info : (391) [MariaDBProtocol] Client 'my_user'@'::ffff:10.180.66.24' is attempting a COM_CHANGE_USER to 'rw_user'.
      2022-05-25 16:00:14 info : (216) Found matching user 'my_user'@'%' for client 'my_user'@'::ffff:10.180.66.248' with sufficient privileges.

        Attachments

          Activity

            People

            Assignee:
            esa.korhonen Esa Korhonen
            Reporter:
            mpflaum Maria M Pflaum
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.