This topic provides information about the steps that you can take to troubleshoot various performance issues.
Symptoms:
OutOfMemoryError
(%BMC_ITDA_HOME%\logs)GC overhead limit exceeded
error (%BMC_ITDA_HOME%\logs)Solution: Use one or more of the following steps to troubleshoot overall performance issues.
Ensure that the maximum Java heap sizes are properly set for each component.
For more information, see Component configuration recommendations.intervalInHrs
property) is properly set for both the Collection Station and the Console Server + Search. For more information, see Component configuration recommendations.Symptom: High CPU utilization on the server hosting the Indexer.
Solution: Use one or more of the following steps to troubleshoot the Indexer performance issues:
org.apache.flume.ChannelException: The channel has reached it's capacity. This might be the result of a sink on the channel having too low of batch size, a downstream system running slower than normal, or that the channel capacity is just too low.
intervalInHrs
property is properly set based on the expected load. By default, every index is optimized every 2 hours. If you have 6-hour interval indices and too much data in the index, the optimizer takes a long time to run and significantly degrades the overall system performance. For more information, see Component configuration recommendations.OutOfMemoryError
or the GC overhead limit exceeded
error in the log file, the Indexer might still have higher CPU utilization due to excessive Java garbage-collection activity. This issue can occur if the maximum Java heap size setting is too low and needs to be adjusted. For more information, see Component configuration recommendations.by
parameter, make sure that the by field has low cardinality (a low number of unique values).Restart the Indexer after making any configuration changes. For more information, see Starting or stopping product services.
Symptom: High CPU utilization on the server hosting the Collection Station.
Solution: Use one or more of the following steps to troubleshoot the Collection Station performance issues:
intervalInHrs
is properly set based on the expected load. By default, every index is optimized every 2 hours. If you have 6-hour interval indices and too much data in the index, the optimizer takes a long time to run and significantly degrades the overall system performance. For more information, see Component configuration recommendations.OutOfMemory
Error
or GC overhead limit exceeded
errors occurred. If such errors did occur, increase the Collector Station’s maximum Java heap size. For more information, see Component configuration recommendations.Restart the Collection Station after making any configuration changes. For more information, see Starting or stopping product services.
Symptom: High CPU utilization on the server hosting the Console Server.
Solution: Use one or more of the following steps to troubleshoot the Console Server performance issues:
OutOfMemory
Error
or the GC overhead limit exceeded
error. If you find either of these errors, increase the Console Server’s maximum Java heap size. For more information, see Component configuration recommendations.by
parameter, ensure that the by field has low cardinality (a low number of unique values).collection.thread.pool.size
property to a value much higher than the default value, then try decreasing this value. Restart the Console Server after making any configuration changes. For more information, see Starting or stopping product services.
Symptom | Solution |
---|---|
High CPU utilization on the server hosting the Configuration Database. | Increase the polling interval of the data collectors configured. |
| Increase the maximum memory required for the Configuration Database For more information, see Component configuration recommendations. |
When you are performing any operation (adding, editing, cloning, and so on) related to data collectors, the Configuration Database goes down |
|
Symptom: Poll interval of the data collectors is falling behind schedule.
Solution: Use the following steps to resolve this issue:
collection.thread.pool.size
property.