+1 (binding)
SUCCESS! [1:04:04.738835]

Tested with a sample app, basic indexing, search, and went through the UI.
Looks good.

Thanks for the effort, Tim!



On Tue, Feb 16, 2021 at 6:42 PM Timothy Potter <[email protected]>
wrote:

> Please vote for release candidate 2 for Lucene/Solr 8.8.1
>
> The artifacts can be downloaded from:
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.8.1-RC2-rev64f3b496bfee762a9d2dbff40700f457f4464dfe
>
> You can run the smoke tester directly with this command:
> python3 -u dev-tools/scripts/smokeTestRelease.py
>
> https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.8.1-RC2-rev64f3b496bfee762a9d2dbff40700f457f4464dfe
>
> The vote will be open for at least 72 hours i.e. until 2021-02-20 03:00
> UTC.
>
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1 SUCCESS! [0:50:07.947952]
>
> Also, as with RC1, in addition to the smoke test, I built a Docker
> image from the RC locally and verified:
>
> a. A rolling upgrade of a 3-node 8.7.0 cluster to the 8.8.1 RC
> completes successfully w/o any NPEs or weirdness with leader election
> / recoveries.
> b. The base_url property is stored in replica state after the upgrade
> c. A basic client application built with SolrJ 8.7.0 can load cluster
> state info directly from ZK and query the 8.8.1 RC2 servers.
> d. Same client app built with SolrJ 8.8.0 works as well.
>
> As this bug-fix release is primarily needed to address a SolrJ
> back-compat break (SOLR-15145) and unfortunately our smoke tester
> framework does not test for backcompat of older SolrJ against the RC,
> I ask others to please test rolling upgrades of servers (ideally
> multi-node clusters) running pre-8.8.0 to this RC if possible. Also,
> please try client applications that are using an older SolrJ, esp.
> those that load cluster state directly from ZK.
>
> Best regards,
> Tim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

-- 
Anshum Gupta

Reply via email to