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

Make ColumnStore work under valgrind

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 1.1.6
    • None
    • None
    • 2018-13

    Description

      Need an option in ExeMgr and other processes to bypass the results of setupResources() as this fails under valgrind causing immediate abort.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MCOL-1495 Memory leak in WriteEngineServ

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

          Bug - A problem which impairs or prevents the functions of the product. MCOL-1346 Debian9 fails to startup in buildbot

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            LinuxJedi Andrew Hutchings (Inactive) added a comment -

            For QA: there is a new '-d' option available for WriteEngine and PrimProc, it will all valgrind to work with them. The flag already exists for ExeMgr and this has been modified to allow valgrind to work.

            LinuxJedi Andrew Hutchings (Inactive) added a comment - For QA: there is a new '-d' option available for WriteEngine and PrimProc, it will all valgrind to work with them. The flag already exists for ExeMgr and this has been modified to allow valgrind to work.
            dleeyh Daniel Lee (Inactive) added a comment -

            Build verified: 1.1.6-1 source

            [root@localhost ~]# cat mariadb-columnstore-1.1.6-1-centos7.x86_64.bin.tar.gz.txt
            /root/columnstore/mariadb-columnstore-server
            commit 1741c7e7d522d1245ec9c1e4c7c7474574f09bd2
            Merge: 2adc4b5 6abef48
            Author: benthompson15 <ben.thompson@mariadb.com>
            Date: Tue Jun 19 09:51:48 2018 -0500

            Merge pull request #113 from mariadb-corporation/davidhilldallas-patch-3

            update readme

            /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
            commit c4e9b0ce3a396edd2353eb44532336e9db857f86
            Merge: ac45350 ffb76bb
            Author: David.Hall <david.hall@mariadb.com>
            Date: Wed Jun 27 17:36:13 2018 -0500

            Merge pull request #511 from mariadb-corporation/MCOL-1467-1

            MCOL-1467 - changes to get back to 1.1.6

            Confirmed that the -d options on 1.1.5-1 does not work for Valgrind.
            Verified that the -d options for both processes do work with Valgrind.

            dleeyh Daniel Lee (Inactive) added a comment - Build verified: 1.1.6-1 source [root@localhost ~] # cat mariadb-columnstore-1.1.6-1-centos7.x86_64.bin.tar.gz.txt /root/columnstore/mariadb-columnstore-server commit 1741c7e7d522d1245ec9c1e4c7c7474574f09bd2 Merge: 2adc4b5 6abef48 Author: benthompson15 <ben.thompson@mariadb.com> Date: Tue Jun 19 09:51:48 2018 -0500 Merge pull request #113 from mariadb-corporation/davidhilldallas-patch-3 update readme /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine commit c4e9b0ce3a396edd2353eb44532336e9db857f86 Merge: ac45350 ffb76bb Author: David.Hall <david.hall@mariadb.com> Date: Wed Jun 27 17:36:13 2018 -0500 Merge pull request #511 from mariadb-corporation/ MCOL-1467 -1 MCOL-1467 - changes to get back to 1.1.6 Confirmed that the -d options on 1.1.5-1 does not work for Valgrind. Verified that the -d options for both processes do work with Valgrind.

            People

              dleeyh Daniel Lee (Inactive)
              LinuxJedi Andrew Hutchings (Inactive)
              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.