Does replication.content.useFileStorage work reliably?

[MeasurableBusinessResults]

Hi all,

we tried enabling replication.content.useFileStorage in /system/console/configMgr/com.day.cq.replication.impl.ReplicationContentFactoryProviderImpl to improve the speed of replication and also to keep some temporary data out of the repository.

It seems to work in principle but we have discovered 2 issues:

• for clustered environments (more than 1 publisher) it seems not to reliably replicate to all publishers
• lots of *.ser and *.ser.status files left over in the crx-quickstart/replication folder, despite the content havin been successfully replicated to the publisher node. These seem to remain around and not being cleaned up, eventually filling up the disk

My questions:

1. has anyone used this successfully in a production environment for a longer time (CQ 5.6.1)?
2. is there anything specific to watch out for when using this feature (we also use workflows with replication on the author)?

[Sham_HC · Accepted solution]

*  It is not meant for cluster please do not use. 

*   Temporary workaround use cron job to cleanup & file a daycare to fix it.