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

Proxy side net_write_timeout and net_read_timeout

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 2.5.0
    • mariadbbackend
    • None
    • MXS-SPRINT-82, MXS-SPRINT-83

    Description

      Put a proxy(mxs) between client and db will let server variables net_write_timeout and net_read_timeout not work, for example,if current client is hang,server's reponse cannot send to client, it will block on tcp send operation, with time gos on, it will trigger net_write_timeout to break this conneciion, but if put proxy(mxs) in the middle, if proxy is health ,server can always send data to proxy without block;

      Proposal:
      Use session track mechanism to track latest net_write_timeout/net_read_timeout value, and apply it in proxy side;

      Attachments

        Activity

          People

            marko.rajala Marko Rajala (Inactive)
            dapeng dapeng huang
            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.