Sorry hit send too fast. The shards were listed as active. Also the solr
instances were still running but the file system they wrote to had become
read only. I thought that would make replication fail and when the issue
was fixed and solr restarted replication would then succeed. Am I hitting
some
I have not tried to reproduce as of yet but hope to do so Monday. The
machine that had the issue was a vm out of my control so I'm not certain
how it was restored. I am using a fairly recent nightly build within the
last few weeks
On Friday, May 11, 2012, Mark Miller wrote:
> So it's easy to repr
So it's easy to reproduce? What do you mean restored from a prior state?
What snapshot are you on these days for future ref?
You have double checked to make sure that shard is listed as ACTIVE right?
On May 11, 2012, at 4:55 PM, Jamie Johnson wrote:
> I've had a few instances where a machine ha