> does the default autoscaling policy stay once they have upgraded? Looking at https://github.com/apache/lucene-solr/commit/8e0eae2/#diff-de88ca16848af57d2474e04e26ea462cR90 , it seems like just upgrading to Solr 8.6.1 will be enough.
On Fri, Jul 24, 2020 at 1:51 PM Houston Putman <[email protected]> wrote: > So it looks like we all agree that 8.6.1 should be cut to fix this issue. > > Unless there's any alternatives proposed, early next week I'm going to > push my branch_8_6 that has the offending commits reverted and some > additional documentation on reverting the defaulted autoscaling policy from > 8.6.0. > > Then I'll start the release process for 8.6.1. > > Please speak up if there is any disagreement. > > - Houston > > On Wed, Jul 22, 2020 at 4:40 PM Ishan Chattopadhyaya < > [email protected]> wrote: > >> Absolutely, Ilan! Good idea. I initially hesitated in doing so because >> Andrzej had a workaround in mind for them, so I thought it would be better >> if he did this. But, it makes sense to inform them of the issue right away >> anyway. >> >> On Wed, 22 Jul, 2020, 11:42 pm Ilan Ginzburg, <[email protected]> wrote: >> >>> Shouldn't we add a note right away to 8.6 notifying of the issue? >>> >>> Le mer. 22 juil. 2020 à 20:08, Atri Sharma <[email protected]> a écrit : >>> >>>> +1, thanks Houston. >>>> >>>> On Wed, Jul 22, 2020 at 10:51 PM Houston Putman < >>>> [email protected]> wrote: >>>> > >>>> > If we agree that this warrants a patch release, I volunteer to do the >>>> release. >>>> > >>>> > I do think a patch release is reasonable even if users have to take >>>> an action when upgrading from 8.6.0. I imagine most users haven't upgraded >>>> to 8.6.0 yet, so if we make the patch now we will make life easier for >>>> everyone that upgrades between now and when 8.7 is released. >>>> > >>>> > On Wed, Jul 22, 2020 at 12:50 PM Atri Sharma <[email protected]> wrote: >>>> >> >>>> >> Ignore this, I misread your email. >>>> >> >>>> >> On Wed, Jul 22, 2020 at 9:11 PM Atri Sharma <[email protected]> wrote: >>>> >> > >>>> >> > Should we not revert the change so that users upgrading from 8.6 to >>>> >> > 8.6.1 get the earlier default policy? >>>> >> > >>>> >> > On Wed, Jul 22, 2020 at 9:09 PM Houston Putman < >>>> [email protected]> wrote: >>>> >> > > >>>> >> > > +1 >>>> >> > > >>>> >> > > Question about the change. Since this patch added a default >>>> autoscaling policy, if users upgrade to 8.6 and then 8.6.1, does the >>>> default autoscaling policy stay once they have upgraded? If so we probably >>>> want to include instructions in the release notes on how to fix this issue >>>> once upgrading. >>>> >> > > >>>> >> > > - Houston >>>> >> > > >>>> >> > > On Wed, Jul 22, 2020 at 1:53 AM Ishan Chattopadhyaya < >>>> [email protected]> wrote: >>>> >> > >> >>>> >> > >> Hi, >>>> >> > >> There was a performance regression identified in 8.6.0 release >>>> due to SOLR-12845. I think it is serious enough to warrant an immediate bug >>>> fix release. >>>> >> > >> >>>> >> > >> I propose a 8.6.1 release. Unfortunately, I'll be unable to >>>> volunteer for this release owning to some other commitments, however >>>> Andrzej mentioned in Slack that he might be able to volunteer for this post >>>> 27th. >>>> >> > >> >>>> >> > >> Are there any thoughts/concerns regarding this? >>>> >> > >> Regards, >>>> >> > >> Ishan >>>> >> > >>>> >> > -- >>>> >> > Regards, >>>> >> > >>>> >> > Atri >>>> >> > Apache Concerted >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Regards, >>>> >> >>>> >> Atri >>>> >> Apache Concerted >>>> >> >>>> >> --------------------------------------------------------------------- >>>> >> To unsubscribe, e-mail: [email protected] >>>> >> For additional commands, e-mail: [email protected] >>>> >> >>>> >>>> >>>> -- >>>> Regards, >>>> >>>> Atri >>>> Apache Concerted >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>>
