Came back from holiday and fixed https://issues.apache.org/jira/browse/SOLR-14671 Can we include it in 8.6.1?
Jan > 27. jul. 2020 kl. 22:56 skrev Houston Putman <[email protected]>: > > Added upgrade notes for the autoscaling stuff. > > Will begin the release process tomorrow when my GPG Keys will be refreshed in > all of the apache systems. > > - Houston > > On Mon, Jul 27, 2020 at 4:41 PM Gus Heck <[email protected] > <mailto:[email protected]>> wrote: > Doc changes are in. Still having trouble with that one link in 8x but just > fixed it locally and made sure not to push that change. > > On Mon, Jul 27, 2020 at 12:57 PM Gus Heck <[email protected] > <mailto:[email protected]>> wrote: > 8x docs not building smoothly on my laptop... (without changes) > troubleshooting, checking deps listed in README.adoc, etc. > > On Mon, Jul 27, 2020 at 11:50 AM Houston Putman <[email protected] > <mailto:[email protected]>> wrote: > Yeah, push it to branch_8_6. I have to document the upgrade notes for the > autoscaling stuff anyways. > > On Mon, Jul 27, 2020 at 11:27 AM Gus Heck <[email protected] > <mailto:[email protected]>> wrote: > I realized after I went looking for it in the new docs that I didn't actually > push the doc changes for MOVEREPLICA to 8x (had intended to verify that > nothing differed in 8x before pushing). Doing that now, and suspect that we > probably want to include it for 8.6.1 > > On Sat, Jul 25, 2020 at 10:20 PM Varun Thacker <[email protected] > <mailto:[email protected]>> wrote: > > does the default autoscaling policy stay once they have upgraded? > > Looking at > https://github.com/apache/lucene-solr/commit/8e0eae2/#diff-de88ca16848af57d2474e04e26ea462cR90 > > <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] > <mailto:[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] <mailto:[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] > <mailto:[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] > <mailto:[email protected]>> a écrit : > +1, thanks Houston. > > On Wed, Jul 22, 2020 at 10:51 PM Houston Putman <[email protected] > <mailto:[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] > > <mailto:[email protected]>> wrote: > >> > >> Ignore this, I misread your email. > >> > >> On Wed, Jul 22, 2020 at 9:11 PM Atri Sharma <[email protected] > >> <mailto:[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] > >> > <mailto:[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] <mailto:[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] > >> <mailto:[email protected]> > >> For additional commands, e-mail: [email protected] > >> <mailto:[email protected]> > >> > > > -- > Regards, > > Atri > Apache Concerted > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > <mailto:[email protected]> > For additional commands, e-mail: [email protected] > <mailto:[email protected]> > > > > -- > http://www.needhamsoftware.com <http://www.needhamsoftware.com/> (work) > http://www.the111shift.com <http://www.the111shift.com/> (play) > > > -- > http://www.needhamsoftware.com <http://www.needhamsoftware.com/> (work) > http://www.the111shift.com <http://www.the111shift.com/> (play) > > > -- > http://www.needhamsoftware.com <http://www.needhamsoftware.com/> (work) > http://www.the111shift.com <http://www.the111shift.com/> (play)
