I'm running into the "WARN | Compass Scheduled Optimizer | AdaptiveOptimizer | ne.optimizer.AdaptiveOptimizer 104 | Failed to obtain lock on sub-index [book], will do it next time." messages more frequently, most likely due to the lucene index getting enormous. The adaptive optimizer is scheduled to run every 10 seconds. My application seems to be crashing (due to stalling for waiting on the lock via the optimizer).
Are there any best practices on the optimizer for very large indexes? Otherwise is there a better way to manage the lucene indexes such that as it grows, the optimizer's optimization time doesn't grow with it? Thanks in advance! -los -- View this message in context: http://www.nabble.com/issues-with-optimizer-tf3879377.html#a10993751 Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
