--
View this message in context:
http://www.nabble.com/http%3A--beerpla.net-2009-09-21-solr-how-to-fix-java-io-ioexception-directory-foo-exists-and-is-a-directory-but-cannot-be-listed-list-returned-null--tp25530499p25530499.html
Sent from the Solr - User mailing list archive at Nabble.com.
I recently hit the problem described in the topic and posted a quick blog
post on how to fix it. Here it is, in case someone will ever encounter it.
http://beerpla.net/2009/09/21/solr-how-to-fix-java-io-ioexception-directory-foo-exists-and-is-a-directory-but-cannot-be-listed-list-returned-null/
Yeah, I'm using single core (solrconfig.xml).
Noble Paul നോബിള് नोब्ळ्-2 wrote:
ideally you should be able to us the variable
${solr.core.instanceDir}
but as I checked the code that is not being set for a single core
deployment. are you using single core?
On Fri, Sep 4, 2009 at
I saw it being used in the default solrconfig.xml in this phrase:
If you wish to hide files under ${solr.home}/conf, explicitly register the
ShowFileRequestHandler using...
It was only natural to assume it would work for something as trivial as
dataDir.
So, there's no way to refer to the
OK, so I can't access it by ${solr.home}, but is there a way to access it?
After all, it's a variable defined in JNDI, shouldn't there be a way to
refer to it?
Also, what about the INFO message that says it can't find /solr/home, while
the instructions refer to solr/home ?
Noble Paul നോബിള്
Here's my problem.
I'm trying to follow a multi Solr setup, straight from the Solr wiki -
http://wiki.apache.org/solr/SolrTomcat#head-024d7e11209030f1dbcac9974e55106abae837ac.
Here's the relevant code:
lt;Context docBase=/some/path/solr.war debug=0 crossContext=true gt;
lt;Environment
I have a fairly simple need to do a conditional update in Solr, which is
easily accomplished in MySQL.
For example,
* I have 100 documents with a unique field called id
* I am POSTing 10 documents, some of which may be duplicate ids, in
which case Solr would update the existing records
I am facing scalability issues designing a new Solr cluster and I need to
master to be able to handle a relatively high rate of updates with almost no
reads - they can be done via slaves.
My existing Solr instance is occupying a huge amount of RAM, in fact it
started swapping at only 4.5mil
It seems like this would require some sort of Java implementation?
Unfortunately I'm not a Java developer but I am in charge of implementing
Solr. Any more detailed/straightforward instructions are very much
appreciated.
Thank you.
Jason Rutherglen-2 wrote:
You could implement optimistic
