Documentation Home
MySQL 9.1 Reference Manual
Related Documentation Download this Manual
PDF (US Ltr) - 40.3Mb
PDF (A4) - 40.4Mb
Man Pages (TGZ) - 259.3Kb
Man Pages (Zip) - 366.4Kb
Info (Gzip) - 4.0Mb
Info (Zip) - 4.0Mb


MySQL 9.1 Reference Manual  /  ...  /  MLE Component Option and Variable Reference

7.5.8.1 MLE Component Option and Variable Reference

The following table lists all MySQL system variables and status variables supported by the ML component. Detailed descriptions of these variables can be found in the next two sections.

Table 7.7 Multilingual Engine Component Variable Reference

Name Cmd-Line Option File System Var Status Var Var Scope Dynamic
mle_heap_status Yes Global No
mle_languages_supported Yes Global No
mle_memory_used Yes Global No
mle_oom_errors Yes Global No
mle_session_resets Yes Global No
mle_sessions Yes Global No
mle_sessions_max Yes Global No
mle_status Yes Global No
mle_stored_functions Yes Global No
mle_stored_procedures Yes Global No
mle_stored_program_bytes_max Yes Global No
mle_stored_program_sql_max Yes Global No
mle_stored_programs Yes Global No
mle_threads Yes Global No
mle_threads_max Yes Global No
mle.memory_max Yes Yes Yes Global Yes

MLE Component System Variables

This section provides a description of each system variable specific to the MLE component. For a summary table that lists all system variables supported by the MySQL server, see Section 7.1.5, “Server System Variable Reference”. For general information regarding manipulation of system variables, see Section 7.1.9, “Using System Variables”.

  • mle.memory_max

    Command-Line Format --mle.memory-max=value
    System Variable mle.memory_max
    Scope Global
    Dynamic Yes
    SET_VAR Hint Applies No
    Platform Specific Linux
    Type Integer
    Default Value 1300M
    Minimum Value 320M
    Maximum Value 64G
    Unit bytes

    Determines the maximum amount of memory to allocate to the MLE component. This variable is dynamic, but can be set only when the component is inactive; you can determine whether this is the case by checking the value of the mle_status system status variable.

    When increasing the value for this variable, you should be bear in mid that you must allow sufficient memory for other uses by the MySQL server such as buffer pools, connection memory, join buffers, and so on. In addition, there must be enough memory to allow system processes to operate correctly.

    Important

    Setting this value greater than the amount of memory available on the system causes undefined behavior.

    For more information about memory usage by the MLE component, see Section 7.5.8.3, “MLE Component Memory and Thread Usage”.

MLE Component Status Variables

This section provides a description of each status variable supported by the MLE component. For a summary table that listsall status variables supported by the MySQL server, see Section 7.1.6, “Server Status Variable Reference”. For information about status variables specific to NDB Cluster, see Section 25.4.3.9.3, “NDB Cluster Status Variables”.

The status variables have the following meanings: