After you scale up a Db2® Big SQL
instance to add new worker pods, the new workers are not being used by queries.
Symptoms
The new workers are not used. For example, you notice that performance isn't improved,
and the new worker pods are driving little CPU usage.
Causes
The new workers were not added to the Db2 nodegroup catalog table.
Resolving the problem
To confirm that the problem is that the new workers were not added to the nodegroup
catalog table, check the state of the cluster by running the bigsql-admin -health
command. This command also resolves any inconsistencies or missing rows in the nodegroup table. For
more information about this command, see Running the Db2 Big SQL health check command.