Re: [Phishing Risk] [External] Re: High concurrency scenarios IndexReader‘s registerParentReader method takes a lot of CPU time

Using elastic search index stats apihttps://www.elastic.co/guide/en/elasticsearch/reference/current/indices-stats.html#indices-stats > 2020年4月17日 下午11:49，Bruno Roustant 写道： > > Hi, > > Next tim

Re: [DISCUSS] 8.5.2 Release?

+1. Thanks Mike On Thu, May 7, 2020 at 2:55 PM Adrien Grand wrote: > +1 > > Le jeu. 7 mai 2020 à 19:13, Mike Drob a écrit : > >> Devs, >> >> I know that we had 8.5.1 only a few weeks ago, but with the fix for >> LUCENE-9350 I think we should consider another bug-fix. I know that without >> it I

Re: [DISCUSS] 8.5.2 Release?

+1 Le jeu. 7 mai 2020 à 19:13, Mike Drob a écrit : > Devs, > > I know that we had 8.5.1 only a few weeks ago, but with the fix for > LUCENE-9350 I think we should consider another bug-fix. I know that without > it I will be explicitly recommending several users to stay off of 8.5.x on > their up

Re: [DISCUSS] 8.5.2 Release?

+1 On Fri, 8 May, 2020, 12:01 am Alan Woodward, wrote: > +1, thanks for volunteering Mike > > On 7 May 2020, at 19:03, Anshum Gupta wrote: > > Thanks for doing this, Mike. > +1 to the 8.5.2 release. > > On Thu, May 7, 2020 at 10:13 AM Mike Drob wrote: > >> Devs, >> >> I know that we had 8.5.1

Re: [DISCUSS] 8.5.2 Release?

+1, thanks for volunteering Mike > On 7 May 2020, at 19:03, Anshum Gupta > wrote: > > Thanks for doing this, Mike. > +1 to the 8.5.2 release. > > On Thu, May 7, 2020 at 10:13 AM Mike Drob > wrote: > Devs, > > I know that we had 8.5.1 o

Re: [DISCUSS] 8.5.2 Release?

Thanks for doing this, Mike. +1 to the 8.5.2 release. On Thu, May 7, 2020 at 10:13 AM Mike Drob wrote: > Devs, > > I know that we had 8.5.1 only a few weeks ago, but with the fix for > LUCENE-9350 I think we should consider another bug-fix. I know that without > it I will be explicitly recommend

[DISCUSS] 8.5.2 Release?

Devs, I know that we had 8.5.1 only a few weeks ago, but with the fix for LUCENE-9350 I think we should consider another bug-fix. I know that without it I will be explicitly recommending several users to stay off of 8.5.x on their upgrade plans. There are some pretty scary looking charts on SOL

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

> The big question is this: “Is this the right time to split Solr and > Lucene into two independent projects?”. Sounds like there are quite a few tasks to complete to get this done. Splitting the build and codebase. Presumably a bunch of administration within Apache/the PMC. Setting up infrastruct

Re: Fwd: [ANNOUNCE] Apache Lucene 7.7.3 released

Thanks all, for making this release, much appreciated! On 04/05/2020 15:16, Noble Paul wrote: > > > -- Forwarded message - > From: *Noble Paul* mailto:no...@apache.org>> > Date: Tue, Apr 28, 2020, 4:51 PM > Subject: [ANNOUNCE] Apache Lucene 7.7.3 released > To: mailto:annou...@apac

Re: [DISCUSS] Lucene-Solr split (Solr promoted to TLP)

There are definitely pros and cons of splitting vs. being a single project. The bigger pains for me until now have been the following ones: Digging Solr failures The theory is that Solr failures can help find Lucene bugs that Lucene bugs wouldn't catch, and while this occurred a couple times, I f