Return
-
Title
How to run a manual compaction -
Description
Some times a manual compaction may need to be run to free up disk space before the scheduled job is run. -
Cause
Database Growing -
Resolution
First verify there is enough space on disk to run compaction.Compaction requires an equal amount of free space as the size of the storage folder "D:\Program Files\Quest\UC Analytics\Storage"If there is not enough space on the drive you will need to increase the free space on the drive with the storage folder.Or move the storage folder to a drive with enough free space.Have a look at this KB on Moving the Storage folder to a new drive. https://support.quest.com/unified-communications-analytics/kb/146231If you do not have or cannot add enough free space to the current UCA server to run the compaction you can move the Storage folder to another server with a drive that has enough free space to complete compaction.If you need to move the storage folder to a network drive you will also need to change the "UC Analytics Storage Engine" service from using the "Local System" account to a Domain account that is a local administrator on the UCA server and has full control of the remote share. Map a drive to the remote and use the above kb to change to the mapped drive.Once compaction has completed following the procedure to move the storage folder back to the original server.To perform the compaction.1. Stop the following UCA Services: "Dell UC Analytics Data Engine" and "Dell UC Analytics Query Engine".Note: In a multi server deployment stop the above services on all UCA servers.2. Open a command prompt using Run As Administrator.3. Change directory to the Storage engine bin directory: I.e. CD "C:\Program Files\Quest\UC Analytics\Storage Engine\bin"4. Run the command nodetool with no parameters. It should display usage. If it errors out, you may need to set an Environment Variable (for the current User) for JAVA_HOME. The directory is something like: C:\Program Files\JAVA\jre1.8.0_60. You will need to adjust the java version to what is on your machine. If it runs correctly, you can move to the next step.5. Run the following command to get the Compaction History:a. nodetool -p 7299 compactionhistory > compactionhistory.txt6. Please zip and send this compactionhistory.txt back to us for additional analysis.7. Run the following commands to execute compaction: --Note copying and pasting the commands may cause an error, you may need to type the commandsa. nodetool –p 7299 setcompactionthroughput 0b. nodetool –p 7299 flushc. nodetool –p 7299 compactNote: compaction may take several hours to run. -
Additional Information
If the database is still growing quickly, review your collections and make sure you are collection only the data you need. For example if you are collecting data from the Message body this will case a lot more data to go into the database and increase the size rapidly. Also note, that if the compaction fails due to requiring more disk space, you will need to increase the disk space temporarily until the compaction is complete.