This is a bit confused. There will be only one timer that starts at time T when
the first doc comes in. At T+ 15 seconds, all docs that have been received since
time T will be committed. The first doc to hit Solr _after_ T+15 seconds starts
a single new timer and the process repeats.
Best,
rick
>
Shawn,
So if the autoCommit interval is 15 seconds, and one update request arrives
at t=0 and another at t=10 seconds, then will there be two timers one
expiring at t=15 and another at t=25 seconds, but this would amount to ONLY
ONE commit at t=15 since that one would include changes from both upda
Thank you very much both Eric and Shawn
Sent from my iPhone
> On Oct 7, 2020, at 10:41 PM, Shawn Heisey wrote:
>
> On 10/7/2020 4:40 PM, yaswanth kumar wrote:
>> I have the below in my solrconfig.xml
>>
>>
>> ${solr.Data.dir:}
>>
>>
>> ${solr.autoCommit.maxTime:6000
On 10/7/2020 4:40 PM, yaswanth kumar wrote:
I have the below in my solrconfig.xml
${solr.Data.dir:}
${solr.autoCommit.maxTime:6}
false
${solr.autoSoftCommit.maxTime:5000}
Does this mean even though we are always sending da
Yes.
> On Oct 7, 2020, at 6:40 PM, yaswanth kumar wrote:
>
> I have the below in my solrconfig.xml
>
>
>
> ${solr.Data.dir:}
>
>
> ${solr.autoCommit.maxTime:6}
> false
>
>
> ${solr.autoSoftCommit.maxTime:5000}
>
>
>
> Does this mean even thoug
I have the below in my solrconfig.xml
${solr.Data.dir:}
${solr.autoCommit.maxTime:6}
false
${solr.autoSoftCommit.maxTime:5000}
Does this mean even though we are always sending data with commit=false on
update solr api, the above should
