Thanks, just created SOLR-14581 as an entry point.
And sure, beers sound good! ;-)
On 17/06/2020 23:13, Erick Erickson wrote:
> Please raise a JIRA and attach your patch to that….
>
> Best,
> Erick
>
> P.S. Buy me some beers sometime if we’re even in the same place...
>
>> On Jun 17, 2020, at
Please raise a JIRA and attach your patch to that….
Best,
Erick
P.S. Buy me some beers sometime if we’re even in the same place...
> On Jun 17, 2020, at 5:00 PM, Bram Van Dam wrote:
>
> Thanks for pointing that out. I'm attaching a patch for the ref-guide
> which summarizes what you said. Mayb
Thanks for pointing that out. I'm attaching a patch for the ref-guide
which summarizes what you said. Maybe other people will find this useful
as well?
Oh and Erick, thanks for your ever thoughtful replies. Given all the
hours of your time I've soaked up over the years, you should probably
start i
Each node has its own timer that starts when it receives an update.
So in your situation, 60 seconds after any give replica gets it’s first
update, all documents that have been received in the interval will
be committed.
But note several things:
1> commits will tend to cluster for a given shard.
'morning :-)
I'm wondering how autocommits work in Solr.
Say I have a cluster with many nodes and many colections with many
shards. If each collection's config has a hard autocommit configured
every minute, does that mean that SolrCloud (presumably the leader?)
will dish out commit requests to ea
