Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-5285

SkySQL OOM Crash? Memory not being released? testing

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 6.3.1
    • 23.02.2
    • PrimProc
    • None
    • SkySQL AWS 32x 128 single node

    Description

      Currently theres a customer whose memory appears not to be released in skysql.

      The current work around is that RDBA/ SRE has to manually mcsShutdown and mcsStart every couple days. However the customer often has to file a ticket saying its crashed and to restart before the scheduled stop/start to clear memory.

      Link to Logs & Configs in comment below

      Attachments

        1. columnstoreMetrics.txt
          159 kB
          Allen Herrera
        2. columnstoreMetrics-11-16-2022.txt
          1.19 MB
          Allen Herrera
        3. libjemalloc.so-1.2
          9.69 MB
          Leonid Fedorov
        4. Screen Shot 2022-10-31 at 4.35.28 PM.png
          241 kB
          Allen Herrera
        5. Screen Shot 2022-10-31 at 4.38.14 PM.png
          152 kB
          Allen Herrera

        Issue Links

          is blocked by

          Task - A task that needs to be done. MCOL-5343 Jmalloc profiling

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Task - A task that needs to be done. MCOL-5260 ASAN check memory leaks/overwrites

          • Critical - Crashes, loss of data, severe memory leak.
          • Stalled

          Activity

            People

              leonid.fedorov Leonid Fedorov
              allen.herrera Allen Herrera
              Votes:
              0 Vote for this issue
              Watchers:
              8 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.