content_image/870514.jpg content_image/870515.jpg content_image/870516.jpg
<img src='content_image/870514.jpg'>

This parameter determines the number of threads to create when rebuilding ordered indexes during a system or node start, as well as when running ndb_restore --rebuild-indexes . It is supported only when there is more than one fragment for the table per data node (for example, when COMMENT="NDB_TABLE=PARTITION_BALANCE=FOR_RA_BY_LDM_X_2"  is used with CREATE TABLE ). 

Setting this parameter to 0 (the default) disables multithreaded building of ordered indexes. 

This parameter is supported when using ndbd  or ndbmtd . 

You can enable multithreaded builds during data node initial restarts by setting the TwoPassInitialNodeRestartCopy  data node configuration parameter to TRUE . 

• LockExecuteThreadToCPU 

<img src='content_image/870515.jpg'>

When used with ndbd , this parameter (now a string) specifies the ID of the CPU assigned to handle the NDBCLUSTER  execution thread. When used with ndbmtd , the value of this parameter is a comma- separated list of CPU IDs assigned to handle execution threads. Each CPU ID in the list should be an integer in the range 0 to 65535 (inclusive). 

The number of IDs specified should match the number of execution threads determined by MaxNoOfExecutionThreads . However, there is no guarantee that threads are assigned to CPUs in any given order when using this parameter. You can obtain more finely-grained control of this type using ThreadConfig . 

LockExecuteThreadToCPU  has no default value. 

• LockMaintThreadsToCPU 

<img src='content_image/870516.jpg'>

This parameter specifies the ID of the CPU assigned to handle NDBCLUSTER  maintenance threads. 

The value of this parameter is an integer in the range 0 to 65535 (inclusive). There is no default value . 

