Hi Eric
No its not NFS. It is ext4.
Our solr is going again and again into OOM error. I am really not sure will
it be because of this exception. But what I observed was Whenever we will
increase polling interval, heap memory will grow at slower rate as compared
to lesser polling interval.
But we
Are you using NFS or other shared file system? I have some details
from Uwe Schindler on issues with NFS resulting from the fact that NFS
is not POSIX compliant.
Best,
Erick
On Thu, Sep 28, 2017 at 9:32 AM, rubi.hali wrote:
> Hi Nawaz
>
> No we are not doing any upgradation.
>
> We hardly have 3
Hi Nawaz
No we are not doing any upgradation.
We hardly have 3 documents so we dont feel the need of having a cloud
configuration
Regarding d exception we analyzed before this error comes We always see
Cahching Directory Factory closing the core
Plus we tried Solr 6.2 version and the same e
Hi
Are you upgrading from an earlier version? If not, I am curious why not try
SolrCloud instead of Master/Slave.
Is there any other error before this error in the logs? Did the core close
after a crash?
Regards
Nawab
On Thu, Sep 28, 2017 at 2:57 AM, rubi.hali wrote:
> Hi
>
> we are using So
Hi
we are using Solr 6.1.0 version. We have done a Master/Slave Setup where in
Slaves we have enabled replication polling after 300 seconds
But after every replication poll, we are getting an error : Index Fetch
Failed: opening NewSearcher called on closed core.
We have enabled softcommit after
Hi
We are using solr6.1 version and have a master slave setup.
We have one master and two slaves .
We have enabled replication poll on slaves at an interval of 300s which
results into an error
and says *Index Fetch Failed : Open NewSearcher Called on closed core*
And our commit strategy involve
