Poor data collection performance If the data collection process is consuming large volumes of memory or failing to finish, you may need to adjust the Data Collector Batch Size setting, which defines the maximum number of records to extract or load for the Data Collector in a single batch. The default value is set to 2000
.
Slow data collection times Typically, data collection should run in under 5 minutes. If the data collection process is more than 10 minutes, then you should increase the size of the Data Trim Interval setting.
Database connection timeouts If your Discover databases are experiencing repeated timeouts, you may need to adjust the Database Connection Timeout setting. The default connection timeout is set to 30
seconds. After the system was running for a while and traffic was increased, your hardware may not be able to manage the traffic level at the current setting.
Data collection performance from multiple canisters By default, Discover can collect from two canisters at one time. If your environment has more canisters, you can increase the size of the Data Collection - Max Concurrent
setting. The appropriate setting depends on your hardware environment.
Database is getting too large If the size of your database is pushing the limits of your storage, you may consider adjusting some settings.
Error - an existing connection was forcibly closed by the remote host When this error occurs frequently, you should check log information as described here.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.