Yes, I missunderstood you question (re: the crashed). Solr did not crash but
we shutdown the JVM (tomcat) gracefully after we kill all our workers. But
upon restarting, solr just throwing the error.
Regards,
/Renz
2009/8/11 Chris Hostetter
>
> : > 5) are these errors appearing after Solr crashes
: > 5) are these errors appearing after Solr crashes and you restart it?
:
:
: Yep, I can't find the logs but it's something like can't obtain lock for
: .lck Need to delete that fiile in order to start the solr properly
wait ... either you missunderstood my question, or you just explained
wha
Hi Chris,
Sorry for the very late reply. As a work around we sent the locking to
single and we turned-off one of our workers. And to answer your question,
please see below:
2009/7/17 Chris Hostetter
>
> This is relaly odd.
>
> Just to clarify...
> 1) you are running a normal solr installation (
This is relaly odd.
Just to clarify...
1) you are running a normal solr installation (in a servlet
container) and using SolrJ to send updates to Solr from another
application, correct?
2) Do you have any special custom plugins running
3) do you have any other apps that might be attemptin
Is it best way to implement my own Locking mechanism here?
Thanks
/Renz
2009/7/10 Renz Daluz
> Hi all,
> I have 2 workers running (app that's builds the index) and both are
> pointing to the same "Solr" (1.3.0) master instance when updating/committing
> documents. I'm using SolrJ to save the doc
Hi all,
I have 2 workers running (app that's builds the index) and both are pointing
to the same "Solr" (1.3.0) master instance when updating/committing
documents. I'm using SolrJ to save the documents.
Then I have 4 slaves solr instance that gets index from master via rsync.
Now. from time to t
