Hmmmmmmm, my _systemUmbracoIndexDontDelete is something stupid like 10GB, on a site with a few hundred nodes. I'm also getting a LOT of lucene errors in the audit trail for each of the documents in the page. A quick search of the forum yields that I can fix this by killing the contents of the folder and re-indexing.
Does anyone know of a way around this, or what causes it? I'm on 4.0.4.2, but once the site has gone live and settled in, I'll be looking to upgrade it to 4.5.1.
I've not had a huge size like that, but certainly had my share of Lucene problem.
But you're correct, just delete the content of the folder (not the folder itself) and run yoursite.com/umbraco/reindex.aspx to create a clean index.
I'm not sure what has caused this, but with a fresh index, I don't think it will start running up to that size any time soon any more, but be sure to keep monitoring it.
It might have something to do with wonky permissions, so that files get generated but never deleted?
We've had lot's of Lucene problems, especially with a site with lot's of nodes.
Reindex helped, for some time... After a while the index was growing again.
Only real solution is upgrading to 4.5.1 as far as I know, because 4.5.1 has two different folders; index and queue. This ensures that there won't be 'file is in use' problems and I think that's the problem.
@kipusoep Good one, I recall that I had some strange errors after removing the DLL, so I put it back and cancelled the indexing event.. But whichever works!
I think that's your best shot indeed :-) Didn't know there is a BeforeAddToIndex handler. Is this handler executed always? Also when Index get's updated? If not the indexer still isn't fully disabled.
Maaaahooosive _systemUmbracoIndexDontDelete folder
Hmmmmmmm, my _systemUmbracoIndexDontDelete is something stupid like 10GB, on a site with a few hundred nodes. I'm also getting a LOT of lucene errors in the audit trail for each of the documents in the page. A quick search of the forum yields that I can fix this by killing the contents of the folder and re-indexing.
Does anyone know of a way around this, or what causes it? I'm on 4.0.4.2, but once the site has gone live and settled in, I'll be looking to upgrade it to 4.5.1.
I've not had a huge size like that, but certainly had my share of Lucene problem.
But you're correct, just delete the content of the folder (not the folder itself) and run yoursite.com/umbraco/reindex.aspx to create a clean index.
I'm not sure what has caused this, but with a fresh index, I don't think it will start running up to that size any time soon any more, but be sure to keep monitoring it.
It might have something to do with wonky permissions, so that files get generated but never deleted?
We've had lot's of Lucene problems, especially with a site with lot's of nodes.
Reindex helped, for some time... After a while the index was growing again.
Only real solution is upgrading to 4.5.1 as far as I know, because 4.5.1 has two different folders; index and queue.
This ensures that there won't be 'file is in use' problems and I think that's the problem.
Is the Lucene index used for anything other than the search in the back end? Is it possible to disable it entirely?
Nope, it's only used for the back-end search. You can remove the Lucene assembly which I have done earlier too.
It's only used for the backend search, you can use this eventhandler to stop the indexing:
using umbraco.BusinessLogic; using umbraco.cms.businesslogic; using umbraco.cms.businesslogic.web; namespace Your.Namespace public class CancelLuceneIndexer : ApplicationBase { public CancelLuceneIndexer() { Document.BeforeAddToIndex += CancelIndexer; } private static void CancelIndexer(Document sender, AddToIndexEventArgs e) { e.Cancel = true; } } }@kipusoep Good one, I recall that I had some strange errors after removing the DLL, so I put it back and cancelled the indexing event.. But whichever works!
Thanks guys, I'm going to keep an eye on it, and if it hapens regularly, I'll probably use the event handler!
@Tim
I think that's your best shot indeed :-) Didn't know there is a BeforeAddToIndex handler.
Is this handler executed always? Also when Index get's updated?
If not the indexer still isn't fully disabled.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.