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

buffer overflow detected and data corruption

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • 10.3.11, 10.3.12
    • N/A
    • None
    • Ubuntu 16.04.5 LTS

    Description

      We are getting Assertion failure every time memory usage of MySQL spikes up to overall system's memory.

      Every time Assertion failure reports different file in code location "/home/buildbot/buildbot/build/mariadb-10.3.11/storage", but every time we see same **buffer overflow detected** statement in mysqld log.

      We only see "buffer overflow detected" like its a pattern. I've attached stack trace as well my.cnf file.

      We are having below server with hardware configuration,
      Ubuntu 16.04.5 LTS
      Memory: 72G
      Cores: 36
      Our Scenario: writing a 50k as a batch insert, we insert about more than 100G of data.

          • We have a few suspects, but still, we are unable to get convinced what was the issue.

      1. We are writing about 100 inserts with "on duplicate key update" - is that possible to get all indexes back into memory as pages(old/young pages) and it's not clearing
      2. I was trying to insert same 50k inserts for about 2m records, I see, there was memory spike about to 2%(based on data size), every time I run it, again and again, it gets added up.

      Important: when we see this issue, table data also getting corrupted. that's the huge worries on our side.

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              sathishjob Sathish Kumar S
              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.