Though, isn't there a recent patch to allow multiple indices under a single Solr instance in JIRA?
Otis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Simpy -- http://www.simpy.com/ - Tag - Search - Share ----- Original Message ---- From: Yonik Seeley <[EMAIL PROTECTED]> To: solr-user@lucene.apache.org Sent: Wednesday, May 9, 2007 6:32:33 PM Subject: Re: Index Concurrency On 5/9/07, joestelmach <[EMAIL PROTECTED]> wrote: > My first intuition is to give each user their own index. My thinking here is > that querying would be faster (since each user's index would be much smaller > than one big index,) and, more importantly, that I would dodge any > concurrency issues stemming from multiple threads trying to update the same > index simultaneously. I realize that Lucene implements a locking mechanism > to protect against concurrent access, but I seem to hit the lock access > timeout quite easily with only a couple threads. > > After looking at solr, I would really like to take advantage of the many > features it adds to Lucene, but it doesn't look like I'll be able to achieve > multiple indexes. No, not currently. Start your implementation with just a single index... unless it is very large, it will likely be fast enough. Solr also handles all the concurrency issues, and you should never hit "lock access timeout" when updating from multiple threads. -Yonik
