I haven't seen any activity regarding this in Jira, just curious if it
would be looked into anytime soon...
On Thu, Oct 2, 2014 at 10:11 AM, Phil Black-Knight <
pblackkni...@globalgiving.org> wrote:
> see the ticket here:
> https://issues.apache.org/jira/browse/SOLR-6579
>
> including a patch to
see the ticket here:
https://issues.apache.org/jira/browse/SOLR-6579
including a patch to fix it.
On Thu, Oct 2, 2014 at 9:44 AM, Shawn Heisey wrote:
> On 10/2/2014 7:25 AM, Phil Black-Knight wrote:
> > I was helping to look into this with Nick & I think we may have figured
> out
> > the core o
On 10/2/2014 7:25 AM, Phil Black-Knight wrote:
> I was helping to look into this with Nick & I think we may have figured out
> the core of the problem...
>
> The problem is easily reproducible by starting replication on the slave and
> then sending a shutdown command to tomcat (e.g. catalina.sh st
I was helping to look into this with Nick & I think we may have figured out
the core of the problem...
The problem is easily reproducible by starting replication on the slave and
then sending a shutdown command to tomcat (e.g. catalina.sh stop).
With a debugger attached, it looks like the fsyncSe
Hello,
I have solr 4.10 running on tomcat 7. I'm doing replication from one master
to about 10 slaves, with standard configuration:
${enable.master:false}
commit
startup
schema.xml,stopwords.txt
