Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-33043

Possible performance optimization when using spider_internal_sql_log_off=0/1

    XMLWordPrintable

Details

    Description

      MDEV-29659 and more specifically discussions around the manual update in MDEV-33041 highlighted a possible Spider performance optimization. It would be reflected in this manual update we were considering:

      Please note that not granting SUPER and setting spider_internal_sql_log_off to 0 or 1 [may/will] lead to
      		 
      slowdowns as SET SQL_LOG_OFF statements will be executed for each query on the data node.

      The first step would be to clarify if this is the case. If so, it can likely be optimized as in some cases these statements may not be needed (for example if it was in the correct on/off state already), or possibly grouping of statements, etc.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29659 Got error 1227 when reading table and ERROR 1227 (42000): Access denied; you need (at least one of) the SUPER privilege(s) for this operation on SELECT or HANDLER READ when using spider_internal_sql_log_off=0

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33041 Improved documentation for spider_internal_sql_log_off

          • Major - Major loss of function.
          • Confirmed

          Activity

            People

              ycp Yuchen Pei
              Roel Roel Van de Paar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.