topic Re: History nodes should be "Orphean" but are not in Alfresco Archive

History nodes should be "Orphean" but are not

fiston — Tue, 22 Nov 2016 17:16:30 GMT

Hi all,I have a problem with some nodes that should be "Orphean" but are not.Using the Alfresco SDK, I was uploadling a document with ContentWriter: ContentWriter contentWriter = serviceRegistry.getContentService().getWriter(nodeRef, ContentModel.PROP_CONTENT, true); content

Re: History nodes should be "Orphean" but are not

kaynezhang — Tue, 29 Nov 2016 02:24:52 GMT

By default orphaned content will keep 14 days, so only content that are 14 days ago wil be deleted

Re: History nodes should be "Orphean" but are not

cesarista — Tue, 29 Nov 2016 17:24:42 GMT

Hi:

As Kayne says orphaned content (deleted from trash) has 14 days period of retention. Then it is moved to contentstore.deleted. HINT: Another way for deleting versions is to remove versionable aspect for the document.

Check this figure from Toni de la fuente's blog for understanding content deletion in Alfresco:

Understanding Alfresco Content Deletion – : : blyx.com : : Blog : : Toni de la Fuente : :

http://blyx.com/wp-content/uploads/2014/08/Slide1.png

If you need to delete content urgently because your disk is near full, you can change these properties in alfresco-global.properties

system.content.eagerOrphanCleanup=true
#system.content.orphanProtectDays=14

system.content.orphanProtectDays=1

system.content.orphanCleanup.cronExpression=0 0 4 * * ?

For tracking orphans, you can query in your database:

SELECT * FROM alf_content_url where orphan_time is not null

And finally, you can control the maximum number of versions with the addon:

GitHub - jottley/alfresco-maxversion-policy

Regards.

--C.

Re: History nodes should be "Orphean" but are not

fiston — Tue, 29 Nov 2016 17:55:36 GMT

The problem is that the files are not orphaned.

- I've removed a content file

- then I emptied the trash

- then I set the orphanProtectDays to 0

- finally I ran contentStoreCleanerTrigger manually

The content files and all of its versions (about 21000) are not set as orpheaned.

orphan_time is null for each of those node

But they are present on contentstore

Nodes are no more available in workspace or archive Stores so I cannot set any aspect.

I think something went wrong when I've emptying the trash due to the number of versions of this nodes and I am looking for a solution in order to remove all of the versions of this file from contentstore.

Thanks

Re: History nodes should be "Orphean" but are not

kaynezhang — Wed, 30 Nov 2016 03:27:52 GMT

You mean you delete the node from share,the node is archived ,but the version hierarchy of that node are not archived?

Re: History nodes should be "Orphean" but are not

fiston — Wed, 30 Nov 2016 10:16:50 GMT

Yes the version hierarchy of that node are not archived.

I can find them on database and contentstore.

Re: History nodes should be "Orphean" but are not

kaynezhang — Wed, 30 Nov 2016 14:35:53 GMT

I did not encounter this problem, for versinalbe node We turn off archive mechnism in type definition to save storage.
In alfresco repository,if we use VersionService to delete(archive) a node ,it will also delete(archive) the node's version history.
Maybe it is a bug of share.