You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue with your module at all but I've seen today a production system having set eagerOrphanCleanup=true as you commented in your README.md, please add comment:
Caution: setting eagerOrphanCleanup=true will delete the content file immediately when the trash is beeing emptied or when a node is beeing removed having the aspect sys:temporary set. orphanProtectDays will no longer apply and you could not recover files in that timeframe! In a production system a content file should be kept at least one day on the storage (given you use a file system store) to catch them in the backup.
To avoid to first copy all content nodes first to contentstore.deleted and then delete them which may cause a lot unwanted IO it may be easier to configure
dir.contentstore.deleted=/dev/null
This will still cause a lot of read IO but avoids at least the IO for write and remove.
Better option would be of cource Alfresco implements an option to not copy the files to contentstore.deleted but remove them during cleanup run.
The text was updated successfully, but these errors were encountered:
Not an issue with your module at all but I've seen today a production system having set
eagerOrphanCleanup=true
as you commented in your README.md, please add comment:Caution: setting
eagerOrphanCleanup=true
will delete the content file immediately when the trash is beeing emptied or when a node is beeing removed having the aspectsys:temporary
set. orphanProtectDays will no longer apply and you could not recover files in that timeframe! In a production system a content file should be kept at least one day on the storage (given you use a file system store) to catch them in the backup.To avoid to first copy all content nodes first to contentstore.deleted and then delete them which may cause a lot unwanted IO it may be easier to configure
This will still cause a lot of read IO but avoids at least the IO for write and remove.
Better option would be of cource Alfresco implements an option to not copy the files to contentstore.deleted but remove them during cleanup run.
The text was updated successfully, but these errors were encountered: