To troubleshoot, follow this checklist:
|1||Check if the processes or applications are running outside of Vertica.
Look at the host uptime or use Linux commands to view the list of processes, memory usage, and CPU activity.
Other commands to view server activity are as follows:
|If yes, possibly move those processes to other servers to reduce their impact on the Vertica database host.
If no, go to Step 2.
|2||Check if memory is low and actively using swap space.|
|2a.||Use the top command to view available memory and swap space usage. Output from the top command appears as below for memory use:
|2b.||You can see the total memory installed (16333388k), and the amount of used memory (4355992k).
Swap used should be 0 as in the example.
A non-zero value for swap used indicates swap activity and one possible cause for slow host response.
For individual processes, the top command returns memory use for each process.
This helps you identify any misconfigured applications.
|2c.||Set the vm.swappiness value to 1 on each Vertica host.
The default value is 60, because the system easily uses some space on the swap disks.
A value of 1 avoids swapping to disk unless absolutely necessary.
As root, change the value to 1:
If no, go to Step 3.
|2d.||To verify the setting:
|3||Verify if your security and operation system patches are up to date. Operating system patches can be installed using the yum command.|
|3a.||To download and install latest patches, run:
|3b.||To view certain packages, for example, the latest security updates, run:
||If yes, install and update all security and Linux patches.|
|3c.||To install all patches, run:
||If no, go to Step 4.|
|3d.||To install only security patch updates, run:
|4||Review errors and warnings in the vertica.log file located in the catalog directory.
Are there errors or other issues that might cause the host to be slow?
|If yes, check the errors or issues in the Vertica log files and correct them.
If no, contact Vertica Technical Support.