Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-68

[ma-2.0.13][5.6.10]MySQL server has gone away error with larger data sets

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.12
    • 3.0.1, 2.0.15
    • None
    • Windows 64-bit and 32-bit, but only from a VM

    Description

      We've a table with about 41 columns in Aurora database with varieties of data types. There are only 12 rows in the table; however row-size in few of the row is really large (500MB+). Total data-size is roughly about 1.7GB here (12 rows X 41 columns).

      Same application works fine if I switch to MySQL ODBC driver (any latest version); however with MariaDB ODBC driver I see "MySQL server has gone away" error. Sometime we had also seen "Connection is lost" message in the same case.

      I'm attaching table schema and ODBC traces of both failing MariaDB ODBC driver as well passing MySQL ODBC driver for your reference.

      Attachments

        1. MariaDB_MySQLServerGoneAway.7z
          25 kB
        2. mariadb-connector-odbc-2.0.15-win32.msi
          3.95 MB
        3. mariadb-connector-odbc-2.0.15-win64.msi
          4.05 MB
        4. screenshot-1.png
          screenshot-1.png
          63 kB
        5. SQL01.txt
          13 kB
        6. StandAloneRepro.cpp
          9 kB
        7. StandAloneRepro.out
          5 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. ODBC-96 Lost connection to MySQL server error when truncate table query is executed

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 21 older comments
            rdhuvad Rahul Dhuvad added a comment -

            Sounds good. Truncate bug is something seen consistently with our customers; for us it's 20% chance to see issue during truncate operation; remaining 80% is doing other select/insert operation of the application. We are trying to see if your private patch can be provided to the customer to try out the fix.

            rdhuvad Rahul Dhuvad added a comment - Sounds good. Truncate bug is something seen consistently with our customers; for us it's 20% chance to see issue during truncate operation; remaining 80% is doing other select/insert operation of the application. We are trying to see if your private patch can be provided to the customer to try out the fix.
            Lawrin Lawrin Novitsky added a comment -

            If nothing goes wrong, public release will follow soon

            Lawrin Lawrin Novitsky added a comment - If nothing goes wrong, public release will follow soon
            Bajarunas Tomas added a comment -

            Which commit fixes the issue?

            Bajarunas Tomas added a comment - Which commit fixes the issue?
            Lawrin Lawrin Novitsky added a comment -

            The problems & the fix were in Connector/C. Do you still need commit id for it?

            Lawrin Lawrin Novitsky added a comment - The problems & the fix were in Connector/C. Do you still need commit id for it?
            Bajarunas Tomas added a comment - - edited

            I see. All good, thanks, I was wondering, since I couldn't see anything related to that in mariadb-connector-odbc repo

            Bajarunas Tomas added a comment - - edited I see. All good, thanks, I was wondering, since I couldn't see anything related to that in mariadb-connector-odbc repo

            People

              Lawrin Lawrin Novitsky
              rdhuvad Rahul Dhuvad
              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.