Checking BIRT iHub bound processors

When the ihubd process starts the first ihubc process on a machine, the ihubd determines the number of processors to which BIRT iHub is bound and stores the list of bound processors.

If you change the processor binding, BIRT iHub does not recognize the changes until you shut down all ihubc processes on the machine and restart one of the ihubc processes.

For example, a cluster that has a maximum licensed CPU limit of nine processors consists of two nodes, machine A and machine B.

Machine A has four processors with no processor binding. All the processors can run Actuate processes. BIRT iHub manages a volume.

Machine B has eight processors with BIRT iHub bound to five processors. There is no ihubc process running on the machine, only the ihubd process.

The cluster counts four processors, the processors on machine A. If you start an ihubc process on machine B, BIRT iHub on machine A counts the five bound processors on the machine and increases the cluster processor count to nine, four on machine A and five on machine B.

If you bind the ihubd process on machine B to six processors, the change has no effect until you shut down all the running ihubc processes on machine B and restart an ihubc process on machine B.

After you stop the ihubc processes and restart an ihubc process on machine B, BIRT iHub System detects that the number of processors in the cluster is ten, which is greater than the maximum number of nine licensed processors. When the number of CPU cores exceeds the number of CPU cores your license permits, BIRT iHub does not start and returns an error message to System Console.

When BIRT iHub is running, each ihubc process periodically compares the list of processors to which it is bound with the list to which it was bound when it started. If the lists differ:

BIRT iHub writes a message with the processor information to the log file. The message contains the maximum number of processors the BIRT iHub license file permits and the following information:

If configured, BIRT iHub sends an e‑mail message to the administrator. The message states that the BIRT iHub System will shut down in one hour if the list of bound processors is not corrected. The e‑mail message contains the information that BIRT iHub sends to the log file.

You must rebind the ihubc process to the same processors to which it was originally bound. During the next hour, any attempt to use the ihubc services fails and a message is written to the appropriate log file. If the list of processors is not restored after an hour, each BIRT iHub in the cluster shuts down and writes an error to its log file.

After updating a CPU-limit license, the system administrator must perform a complete restart of the system to refresh the list of processors that BIRT iHub uses to periodically compare the list of currently bound processors to the list to which it was bound when it started. Before restarting, the system administrator must also edit the acpmdconfig.xml file to adjust the CPU affinity to the new settings specified in the <DaemonCPUaffinity> element.

BIRT iHub uses a separate ihubc process to manage each volume on a machine. When you take a volume online, ihubd starts an ihubc process.

When ihubd starts an ihubc process, ihubd compares the list of processors to which the ihubc process is bound to the original list of processors to which the ihubd is bound. If the lists differ:

A message in the configuration states that the binding of the new process differs from the original binding of the parent process.

Each Factory and View process periodically compares its list of bound processors with the list of processors to which it was bound at startup. If the lists differ, the process writes an error to its log file and shuts down.