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

Ensure that connection ID is in 32bit range

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 10.2.13
    • Server
    • None
    • 10.2.13

    Description

      Connectors assume that connection ID(often referred to as thread_id in the source) is 32bit , because this is what server sends them in the first packet. However, server handles connection IDs as 64bit integers, which means we overflow can happen, and connection ID sent to client is no longer valid,

      MySQL happens to have fixed this bug in 5.7 with https://dev.mysql.com/worklog/task/?id=7293.

      I believe we can think of a better scalable allocation algorithm not involving any kinds of hashes.

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. MDEV-35706 Shrink my_thread_id to uint32_t

          • Major - Major loss of function.
          • Open
          relates to

          Task - A task that needs to be done. MDEV-15086 Return the full 64 bits of thread ID in handshake packet

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            wlad Vladislav Vaintroub created issue -
            wlad Vladislav Vaintroub made changes -
            Field Original Value New Value
            Assignee Vladislav Vaintroub [ wlad ]
            wlad Vladislav Vaintroub made changes -
            Component/s Server [ 13907 ]
            wlad Vladislav Vaintroub made changes -
            Description Connectors assume that connection ID is 32bit, because this is what server sends them in the first packet. However, server handles connection IDs as 64bit integers, which means we overflow can happen, and connection ID sent to client is no longer valid,

            MySQL happens to have fixed this bug in 5.7 with https://dev.mysql.com/worklog/task/?id=7293.

            I believe we can think of a better scalable allocation algorithm not involving any kinds of hashes.             		Connectors assume that connection ID(often referred to as thread_id in the source) is 32bit , because this is what server sends them in the first packet. However, server handles connection IDs as 64bit integers, which means we overflow can happen, and connection ID sent to client is no longer valid,

            MySQL happens to have fixed this bug in 5.7 with https://dev.mysql.com/worklog/task/?id=7293.

            I believe we can think of a better scalable allocation algorithm not involving any kinds of hashes.
            serg Sergei Golubchik made changes -
            wlad Vladislav Vaintroub made changes -
            Fix Version/s 10.2 [ 14601 ]
            serg Sergei Golubchik made changes -
            Sprint 10.2.13 [ 228 ]
            wlad Vladislav Vaintroub made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            wlad Vladislav Vaintroub made changes -
            issue.field.resolutiondate 2018-02-01 14:00:40.0 2018-02-01 14:00:40.068
            wlad Vladislav Vaintroub made changes -
            Fix Version/s 10.2.13 [ 22910 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Confirmed [ 10101 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 85162 ] MariaDB v4 [ 153660 ]
            ParadoxV5 Jimmy Hú made changes -

            People

              wlad Vladislav Vaintroub
              wlad Vladislav Vaintroub
              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.