Recursive nesting of indexbackup_temp directories

[hbf]

I've upgraded to Alfresco 2.9b and have just realised that my alf_data directory contains

audit.contentstore
contentstore
contentstore.deleted
lucene-indexes
  archive
  indexbackup_temp  (*)
    archive
    indexbackup_temp
      <story goes on recursively in here to some extent>
    locks
    system
  locks
  system
  user
  workspace‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Can I safely remove the directory indexbackup_temp (marked with a star above)?

Should I reindex afterwards?

Thanks,
Kaspar

P.S. This seems to be JIRA issue AR-2175.

[hbf]

Anybody?

I'd be quite glad to know what to do. I am reluctant to delete files in alf_data for obvious reasons 

[torsten_e]

I have the same problem. Is there a solution ?

Torsten

[ajaywazir]

We are trying Alfreso 2.9.0 C Dev 816 Schema 124
We are still facing this problem.
Is there anyway we can hack the problem away?
Ajay Wazir

[hbf]

Same problem here. Apparently, the problem has been fixed, but I suppose the fix has not yet made it into the public SVN?

It would be great if the fix were included in the v2.9 Community Final release.

[jmilliere]

Obviously it has been corrected in the Enterprise version, since build 151 (http://issues.alfresco.com/browse/AR-1694)
But on the community side, it is not corrected on 2.9C dev (build 816).

I think we need to separate clearly the issues on 2 jiras: In the current situation, the case AR-1694 is solved for enterprise, but not for community… leading us to a lot of misunderstandings…

[steve]

Hi,

All the 2.2 Enterprise fixes should now be in the 2.9 svn code.

Steve

[jmilliere]

Maybe, but it's not in 2.9C… Anyway, it could be convenient to have a table with the corresponding between the enterprise builds and the community builds (or svn releases).

All would be clearer if we were knowing the community svn release corresponding to enterprise build 151…

[jmilliere]

I've just tried with Community edition rev 1914 in SVN, and it seems that the problem is not yet solved…

Someone can confirm ?

Is it scheduled to be solved soon ?

[jmilliere]

As a workaround, is it possible to disable lucene index backup ? how ?