Re: Underlying file changed by an external force

On 5/11/2017 3:49 PM, Oakley, Craig (NIH/NLM/NCBI) [C] wrote: > FWIW, we now have a hypothetical suspect. We are getting these errors on > three CentOS7 hosts, each of which recently had antivirus software installed. Lucene index files tend to be large binary files where almost any combination

RE: Underlying file changed by an external force

-user@lucene.apache.org Subject: RE: Underlying file changed by an external force None of them have dataDir properties: they just use the "data" subdirectory in the same directory as the core.properties -Original Message- From: Erick Erickson [mailto:erickerick...@gmail.

RE: Underlying file changed by an external force

> Subject: Re: Underlying file changed by an external force bq: All the core.properties files are each in their own directory with no overlap Not quite what I was asking. By definition, all core.properties are in their own directory. In fact Solr stops looking down the tree when it finds the

Re: Underlying file changed by an external force

manifest itself at some > time other than startup > > The Solr version is 5.4.1, in case that is relevant. > > > -Original Message- > From: Erick Erickson [mailto:erickerick...@gmail.com] > Sent: Thursday, May 04, 2017 3:20 PM > To: solr-user <solr-user@lucene.apach

RE: Underlying file changed by an external force

[mailto:erickerick...@gmail.com] Sent: Thursday, May 04, 2017 3:20 PM To: solr-user <solr-user@lucene.apache.org> Subject: Re: Underlying file changed by an external force You need to look at all of your core.properties files and see if any of them point to the same data directory. Second: if yo

Re: Underlying file changed by an external force

You need to look at all of your core.properties files and see if any of them point to the same data directory. Second: if you issue a "kill -9" you can leave write locks lingering. Best, Erick On Thu, May 4, 2017 at 11:00 AM, Oakley, Craig (NIH/NLM/NCBI) [C] wrote: > We