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

Add support for limiting the amount of data read.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 22.08.0
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-154, MXS-SPRINT-155, MXS-SPRINT-156, MXS-SPRINT-157

      Description

      MaxScale uses epoll together with non-blocking socket descriptors. When MaxScale is notified there is something to read on a socket, it will read and handle the data until EAGAIN is returned. That is necessary as the sockets are added to epoll in edge-triggered mode. Now, if a client is capable of writing so fast that MaxScale never is able to empty the socket, then that client will be able to monopolize the thread handling that particular socket. Thus, it should be possible to not ready everything before returning to epoll and checking for sockets ready to be read.

        Attachments

          Activity

            People

            Assignee:
            johan.wikman Johan Wikman
            Reporter:
            johan.wikman Johan Wikman
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.