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

ExeMgr spawns infinite number of threads

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 5.6.2
    • Icebox
    • ExeMgr

    Description

      show variables like '%version%'
      -> ;
      ---------------------------------------------------------------------------+

      Variable_name Value

      ---------------------------------------------------------------------------+

      in_predicate_conversion_threshold 1000
      innodb_version 10.6.4
      protocol_version 10
      slave_type_conversions  
      system_versioning_alter_history ERROR
      system_versioning_asof DEFAULT
      tls_version TLSv1.1,TLSv1.2,TLSv1.3
      version 10.6.4-MariaDB
      version_comment MariaDB Server
      version_compile_machine x86_64
      version_compile_os Linux
      version_malloc_library system
      version_source_revision 2db692f5b4d6bb31a331dab44544171c455f6aca
      version_ssl_library OpenSSL 1.1.1c FIPS 28 May 2019
      wsrep_patch_version wsrep_26.22

      MariaDB [(none)]> SELECT calgetversion();
      -----------------

      calgetversion()

      -----------------

      5.6.2

      ----------------


      1. ) after we start the ETL the number of Threads increase infinite.
      2.) when we cancel the execution the number of Threads is still higher than at the beginning

      Can you please help us to find a parameter where we can limit the max Threads spawned by ExeMgr.

      Thank you.
      Br Andreas

      Attachments

        Activity

          People

            Unassigned Unassigned
            aeae81 andreas eschbacher
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.