As I had pointed out in my first reply to this thread, you had a directory
named temp-snapshot.20070816120113
in your data directory on the slave. Snapinstaller was mistakenly treating
that as the lastest snapshot and was installing that every time it was
called. Snapinstaller didn't trigger a co
Well, I've been playing around with it (removed all the snapshots,
restarted tomcat) and it seems like it works now.. maybe.
I was noticing that search2 and search3, the slaves, had searchers
that had been opened several days ago - when we do several 100
commits and 2 optimizes on search1,
On 9/6/07, Matthew Runo <[EMAIL PROTECTED]> wrote:
> The thing is that a new searcher is not opened if I look in the
> stats.jsp page. The index version never changes.
The index version is read from the index... hence if the lucene index
doesn't change (even if a ew snapshot was taken), the versio
The thing is that a new searcher is not opened if I look in the
stats.jsp page. The index version never changes.
When I run..
sudo /opt/solr/bin/commit -V -u tomcat5
..I get a new searcher opened, but even though it (in theory)
installed the new index, I see no docs in there. During the
s
The snapinstaller script opens a new searcher by calling commit. From the
attached debug output it looks like that actually worked:
+ /opt/solr/bin/commit
+ [[ 0 != 0 ]]
+ logExit ended 0
Try running the /opt/solr/bin/commit directly with the -V option.
Bill
On 9/5/07, Matthew Runo <[EMAIL PRO
If it helps anyone, this index is around a gig in size.
++
| Matthew Runo
| Zappos Development
| [EMAIL PROTECTED]
| 702-943-7833
++
On Sep 5, 2007, at 3:14 PM, Matthew Runo wrote
It seems that the scripts cannot open new searchers at the end of the
process, for some reason. Here's a message from cron, but I'm not
sure what to make of it... It looks like the files properly copied
over, but failed the install. I removed the temp* directory, but
still SOLR could not la
> latest snapshot /opt/solr/data/temp-snapshot.20070816120113 already
> installed
It looks like you have a directory named temp-snapshot.20070816120113
in your data directory. You should remove it. One of the other
script might have left that behind somehow.
I will update the snapinstaller scri
Hello!
On a somewhat related note, our replication seems very much broken.
I've added -v to all my cron jobs, and I think I've seen the error
(below).
As you can see, it's rsyncing an updated index, but then doesn't seem
to know to install it. I'm not sure why though.. no errors are
rep
