Deploying and Managing Apama Applications > Event Correlator Utilities Reference > Using a replay log to diagnose problems > Rotating the replay log
Rotating the replay log
While the replay log can get rather large, most file systems can handle large replay logs with no special action on your part. However, you might encounter one of the following situations:
*You want to archive your replay logs.
*Your operating system enforces a limit on file size.
*The replay log has become too large.
In these situations, you can rotate the replay log. Rotating the replay log means that the correlator closes the current replay log and starts sending messages to a new replay log. You should rotate the replay log only when you have a specific need to do so. You do not want to have thousands of replay logs in a directory since file systems do not handle this efficiently.
If you plan to rotate replay logs, specify the ${ID} tag when you specify the --replayLog option when you start the correlator.
To rotate the replay log, invoke the engine_management utility and specify the -r rotateReplayLog option. The name of the new replay log is the same as the name of the closed replay log except that the correlator increments the ID portion of the replay log filename by 1.
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.