On 10/14/2018 10:39 PM, Shalin Shekhar Mangar wrote:
The responses are collected by node so subsequent responses from the same
node overwrite previous responses. Definitely a bug. Please open an issue.
Done.
https://issues.apache.org/jira/browse/SOLR-12867
Thanks,
Shawn
The responses are collected by node so subsequent responses from the same
node overwrite previous responses. Definitely a bug. Please open an issue.
On Mon, Oct 15, 2018 at 6:24 AM Shawn Heisey wrote:
> On 10/14/2018 6:25 PM, dami...@gmail.com wrote:
> > I had an issue with async backup on solr
On 10/14/2018 6:25 PM, dami...@gmail.com wrote:
I had an issue with async backup on solr 6.5.1 reporting that the backup
was complete when clearly it was not. I was using 12 shards across 6 nodes.
I only noticed this issue when one shard was much larger than the others.
There were no answers here
Hi Shawn,
I had an issue with async backup on solr 6.5.1 reporting that the backup
was complete when clearly it was not. I was using 12 shards across 6 nodes.
I only noticed this issue when one shard was much larger than the others.
There were no answers here
http://lucene.472066.n3.nabble.com/asy
I'm working on reproducing a problem reported via the IRC channel.
Started a test cloud with 7.5.0. Initially with two nodes, then again
with 3 nodes. Did this on Windows 10.
Command to create a collection:
bin\solr create -c test2 -shards 30 -replicationFactor 2
For these URLs, I dropped t
