On Tue, Feb 2, 2010 at 11:32, Niu, Xuetao <[email protected]> wrote: > Hello, > > I delete my versionable root node /rtde:data as well as the homeDir > everytime the application starts. But I see the Multi-Index logs growing > each time. > > INFO MultiIndex - indexing... > /jcr:system/jcr:versionStorage/b3/35/8e/b3358ed8-a1f5-4d42-8451-8522deee > 8548/jcr:rootVersion (4500) > INFO MultiIndex - indexing... > /jcr:system/jcr:versionStorage/3e/7a/98/3e7a985d-6868-4d5c-b06b-5743c640 > 2434/jcr:versionLabels (4600) > INFO MultiIndex - indexing... > /jcr:system/jcr:versionStorage/b5/88/c4/b588c475-f744-402d-ad52-fd03a845 > 1c64/1.0/jcr:frozenNode/tenant:_100/env:_env (4700) > INFO MultiIndex - indexing... /jcr:system/jcr:versionStorage/55/cc/ec > (4800) > INFO MultiIndex - indexing... > /jcr:system/jcr:versionStorage/b7/69/ee/b769ee98-aef4-4f3a-8656-adcc0d70 > a34e/1.1/jcr:frozenNode/tenant:_100 (4900) > INFO MultiIndex - indexing... /jcr:system/jcr:versionStorage/93/74/43 > (5000) > INFO LRUNodeIdCache - num=0/10240 hits=0 miss=80000 > > Why is this? It supposes to be an empty workspace each time. > > Can I disable multi-indexing? And what would be the consequence be?
The "MultiIndex" you see in the logs is the lucene index used for the JCR query implementation. It will not grow endlessly, if nodes get removed, it will get smaller (not necessarily immediatly, afaik, because it might do that on a later merge). But in your case you have versions left over in the version tree, which is normal. If you delete a node, it's versions are not deleted automatically. That's the purpose of keeping old versions ;-) To explicitly get rid of the version tree, see http://markmail.org/message/4iflkzjxusrpj4ks and http://issues.apache.org/jira/browse/JCR-134 for some hints. Regards, Alex -- Alexander Klimetschek [email protected]
