On Fri, Jan 22, 2010 at 4:24 AM, Trey wrote:
> Unfortunately, when I went back to look at the logs this morning, the log
> file had been blown away... that puts a major damper on my debugging
> capabilities - so sorry about that. As a double whammy, we optimize
> nightly, so the old index files h
I did not have good luck with super-high-speed polling. You probably
need to adjust the various parameters on both sides of the
replication.
Some sites (LinkedIn for example with Zoie) do not use replication.
They have all query servers do their own indexing, so that new content
will be available
Unfortunately, when I went back to look at the logs this morning, the log
file had been blown away... that puts a major damper on my debugging
capabilities - so sorry about that. As a double whammy, we optimize
nightly, so the old index files have completely changed at this point.
I do not rememb
is it a one off case? do you observerve this frequently?
On Thu, Jan 21, 2010 at 11:26 AM, Otis Gospodnetic
wrote:
> It's hard to tell without poking around, but one of the first things I'd do
> would be to look for /home/solr/cores/core8/index.20100119103919/_6qv.fnm -
> does this file/dir rea
It's hard to tell without poking around, but one of the first things I'd do
would be to look for /home/solr/cores/core8/index.20100119103919/_6qv.fnm -
does this file/dir really exist? Or, rather, did it exist when the error
happened.
I'm not looking at the source code now, but is that really
