How to support & monitor the Axigen X1 upgrade of search indexes for better search performance

For better search performance, Axigen X1 rebuilds the search indexes and normalized messages upon upgrade. Under certain conditions, this might use additional system resources — processing power and disk space — for a short period of time following the upgrade. Several related recommendations are detailed below.

Resolution

Following the Axigen X1 upgrade, the existing disposable metadata information (indexes and normalized messages) is automatically deleted and then re-constructed progressively, following the usage pattern of the platform (for example, new and more efficient metadata is created when a user accesses the WebMail interface and performs the first search in a particular folder).

Therefore, we recommend to increase the total message storage size of that particular domain before starting the upgrade procedure, in case the "Percent from available size" value reported by CLI show disposablemetadatainformation is bigger than 70%. This can be achieved by increasing* the maximum file size of the existing message storage location (for example from 500 MB to 600 MB for a 20% increase) or by adding a new message storage location.

	<domain#> show disposablemetadatainformation
	* Current size: 25056266 Kb
	* Maximum available size: 34406400 Kb
	* Percent from available size: 73 %
	* Maximum storage capacity: 68812800 Kb
	* Percent from storage capacity: 36 %
	+OK: command successful

*) Before this action please check that your new configuration will not over pass the physical available space you can actually use on your storage dedicated for Axigen.


Another option is to increase the percentage from storage capacity allocated to disposable metadata (for example from 25% to 30%).

The removal process of the old disposable metadata information can be monitored by checking in the PROCESSING log file for the following lines (available only if the PROCESSING service log level is set to "Protocol Communication"):

	2017-02-22 17:07:14 +0200 16 host62 PROCESSING:60000017: >> Started unlink procedure for large mailbox 'volatileData.v0.0'; remaining items: 3495351; unlinked items: 250; failed unlinks: 0; storage switches: 1; container switches: 1; I/O load: 0.9869
	2017-02-22 17:07:16 +0200 16 host62 PROCESSING:60000017: >> Executing unlink procedure for large mailbox 'volatileData.v0.0'; remaining items: 3485184; unlinked items: 10420; failed unlinks: 0; storage switches: 7; container switches: 7; I/O load: 0.9679
	...
	2017-02-22 17:39:53 +0200 16 host62 PROCESSING:60000017: >> Executing unlink procedure for large mailbox 'volatileData.v0.0'; remaining items: 4156; unlinked items: 3487860; failed unlinks: 4554; storage switches: 1525; container switches: 2515; I/O load: 1.0000
	2017-02-22 17:39:58 +0200 16 host62 PROCESSING:60000017: >> Finished unlink procedure for large mailbox 'volatileData.v0.0'; remaining items: 0; unlinked items: 3492016; failed unlinks: 4554; storage switches: 1525; container switches: 2515