{kb-symptom}
When CDP Agent does not have enough available connections to open 4 threads during MySQL restore, CDP cannot restore all tables ("Too many connections" issue). But after restoring some of the tables, CDP consumes a lot of CPU resources. This issue affects the performance of the machine and the use of CPU is not solved until we restart the {{cdp-server}} service.
{kb-resolution}
The issue has been corrected in CDP 4.2.0. CDP does not consume lot of CPU resources when there are no tasks being executed after MySQL restore when the number of connections is reached.
{kb-related-articles}
When CDP Agent does not have enough available connections to open 4 threads during MySQL restore, CDP cannot restore all tables ("Too many connections" issue). But after restoring some of the tables, CDP consumes a lot of CPU resources. This issue affects the performance of the machine and the use of CPU is not solved until we restart the {{cdp-server}} service.
{kb-resolution}
The issue has been corrected in CDP 4.2.0. CDP does not consume lot of CPU resources when there are no tasks being executed after MySQL restore when the number of connections is reached.
{kb-related-articles}