Originally posted by Jeff Lebowski
View Post
* The indexer is chokes on some specific content in a post. Yeah, buggy indexer. But if it's always the same post every time you could try and delete it and see if the indexer gets past it.
* The indexer runs out of memory (either runs the host out of memory or reaches some defined process-memory limit) after doing a specific amount of posts. Is it possible to break the indexing work out into multiple chunks by, say, specifying a range of posts on the command line, or must it run on the whole corpus of posts in one fell swoop?
* The indexer runs out of disk space after doing a specific amount of posts. What working directory does the indexer use? I assume it's some user-allocated disk space to your hosting account. When the indexer barfs, is the disk full at that time?
Those would be my best guesses.
Comment