based one?
--
Regards,
Shalin Shekhar Mangar.
--
View this message in context:
http://www.nabble.com/commit---new-searcher-delay--tp22342916p23036207.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Fri, Mar 6, 2009 at 8:47 AM, Steve Conover scono...@gmail.com wrote:
That's exactly what I'm doing, but I'm explicitly replicating, and
committing. Even under these circumstances, what could explain the
delay after commit before the new index becomes available?
How are you explicitly
Yep, I notice the default is true/true, but I explicitly specified
both those things too and there's no difference in behavior.
On Wed, Mar 4, 2009 at 7:39 PM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
On Thu, Mar 5, 2009 at 6:06 AM, Steve Conover scono...@gmail.com wrote:
I'm doing
On Thu, Mar 5, 2009 at 10:30 PM, Steve Conover scono...@gmail.com wrote:
Yep, I notice the default is true/true, but I explicitly specified
both those things too and there's no difference in behavior.
Perhaps you are indexing on the master and then searching on the slaves? It
may be the delay
That's exactly what I'm doing, but I'm explicitly replicating, and
committing. Even under these circumstances, what could explain the
delay after commit before the new index becomes available?
On Thu, Mar 5, 2009 at 10:55 AM, Shalin Shekhar Mangar
shalinman...@gmail.com wrote:
On Thu, Mar 5,
: I suspect this has something to do with waiting for the searcher to
: warm and switch over (?). Though, I'm confused because when I print
: out /solr/admin/registry.jsp, the hashcode of the Searcher changes
: immediately (as the commit docs say, the commit operation blocks by
: default until a
I'm doing some testing of a solr master/slave config and find that,
after syncing my slave, I need to sleep for about 400ms after commit
to see the new index state. i.e. if I don't sleep, and I execute a
query, I get results that reflect the prior state of the index.
I suspect this has something
On Thu, Mar 5, 2009 at 6:06 AM, Steve Conover scono...@gmail.com wrote:
I'm doing some testing of a solr master/slave config and find that,
after syncing my slave, I need to sleep for about 400ms after commit
to see the new index state. i.e. if I don't sleep, and I execute a
query, I get
