

Product Administration › Data Collector Caching of Polled Data When the Data Aggregator Host is Unavailable › Modify the Data Cache Memory Limit
Modify the Data Cache Memory Limit
You can modify the amount of data that Data Collector caches when Data Aggregator is unavailable.
Follow these steps:
- Calculate the amount of memory that is required for data caching.
- Make a note of the amount of memory that is required for data caching.
- Log in to the computer where Data Collector is installed. Log in as the root user or a sudo user with access to a limited set of commands.
Note: For more information about the sudo user, see the Data Aggregator Installation Guide.
- Stop Data Collector using this command:
service dcmd stop
- Modify the IM_MAX_MEM memory setting for Data Collector:
- Access the Data Collector installation directory/apache-karaf-2.3.0/jms/local-jms-broker.xml file.
- Change the IM_MAX_MEM limit to two times the value you noted in step 2. Verify that this value is not more than the available RAM on the system.
- Modify the cache memory limit for the JMS broker on Data Collector:
- Access the Data Collector installation directory/apache-karaf-2.3.0/jms/local-jms-broker.xml file.
- Locate the following line:
<memoryUsage limit=”value”/>
- value
-
Is the current cache limit setting.
- Modify the current cache limit setting with the value that you calculated previously and save the file.
- Make Data Collector aware of the changes to the jms/local-jms-broker.xml file. Type the following command to deploy a fake .lock file. A fake .lock file makes Data Collector think that there was an ungraceful shutdown:
echo `date` > /opt/IMDataCollector/apache-karaf-2.3.0/.lock
- Restart Data Collector using this command:
service dcmd start
The cache memory limit is configured.
Copyright © 2015 CA Technologies.
All rights reserved.
 
|
|