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

MariaDB does not start if more than 128 cpu's are available

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 5.5.33a
    • 5.5.34
    • None
    • None
    • IBM systemx with 8 cpus with 10 cores with 2 threads = 160 available cpu's

    Description

      MAX_THREAD_GROUPS 128 setting prevents MariaDB from starting. No configuration is read at the time this check is made. Solution: make allocating the structure dynamic, make default to be always less than MAX_THREAD_GROUPS, or make MAX_THREAD_GROUPS bigger.

      ./sql/threadpool_unix.cc:static thread_group_t all_groups[MAX_THREAD_GROUPS];
      ./sql/threadpool.h:#define MAX_THREAD_GROUPS 128
      ./sql/sys_vars.cc: VALID_RANGE(1, MAX_THREAD_GROUPS), DEFAULT(my_getncpus()), BLOCK_SIZE(1),

      Server does not start if my_getncpus() > MAX_THREAD_GROUPS and there is no configuration option around that.

      Attachments

        Issue Links

          Activity

            People

              svoj Sergey Vojtovich
              hyvatti Jaakko Hyvätti
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.