Did you solve this problem?
I am experiencing (Solr 4.4.0 not clustered) the same behavior when the
files are mounted via sshfs (a requirement) but not when they are mounted
via nfs.
I'm hoping you solved your problem and might have advice on how I can solve
mine.
Thanks,
Grainne
--
View th
I did see that. The file its looking for doesn't exist post slaves have been
updated. I suspect there was segment info file of that name before the
syncing happened and once the file was removed the searcher still looks for
the file. Strange behavior, don't know why should this happen.
--
View t
Did you check here at logs:
*Caused by: java.io.FileNotFoundException:
/opt/solr/myCore/data/index/_2he9.si (No such file or directory)*
2013/10/4 tamanjit.bin...@yahoo.co.in
> Hi,
> We migrated to Solr 4.3 from 3.5 yesterday. We use multicore Master Slave
> architecture and use external scrip
On Jun 26, 2012, at 7:35 AM, stockii wrote:
> Hello again.
>
> this is my Exception.
> with SolrVersion: 4.0.0.2012.04.26.09.00.41
>
> SEVERE: Exception while solr commit.
> java.io.FileNotFoundException: _8l.cfs
> at org.apache.lucene.store.FSDirectory.fileLength(FSDirectory.java:266)
>
In my older version of solr this was possible, but it seems not possible in
this new =(
--
View this message in context:
http://lucene.472066.n3.nabble.com/FileNotFoundException-during-commit-concurrences-process-tp3991384p3991388.html
Sent from the Solr - User mailing list archive at Nabble.com.
On Tue, Sep 29, 2009 at 3:19 AM, Mark Miller wrote:
> Looks like a bug to me. I don't see the commit point being reserved in
> the backup code - which means its likely be removed before its done
> being copied. Gotto reserve it using the delete policy to keep around
> for the full backup duration
Mark Miller wrote:
> Looks like a bug to me. I don't see the commit point being reserved in
> the backup code - which means its likely be removed before its done
> being copied. Gotto reserve it using the delete policy to keep around
> for the full backup duration. I'd file a JIRA issue.
>
>
>
Y
Looks like a bug to me. I don't see the commit point being reserved in
the backup code - which means its likely be removed before its done
being copied. Gotto reserve it using the delete policy to keep around
for the full backup duration. I'd file a JIRA issue.
--
- Mark
http://www.lucidimagina
I think you may be right i've opened SOLR-830
: We may have identified the root cause but wanted to run it by the community.
: We figure there is a bug in the snappuller shell script, line 181:
-Hoss
