I found a minor glitch.

In solr-exporter, the default config solr-exporter-config.xml still uses 
solr_metrics_core_replication_master as key for the 
REPLICATION./replication.isLeader metric.

In 8.x the metrics was named REPLICATION./replication.isMaster and 
REPLICATION./replication.isSlave, but renamed to isLeader / isFollower in 9.0.
The prometheus key for follower is correctly renamed as 
solr_metrics_core_replication_follower already.
I think the master -> leader should also have been done.

However I cannot see it being referenced in Grafana dashboard or elsewhere, so 
probably not worth a respin, we can do it in 9.1.

Jan

> 30. mar. 2022 kl. 20:53 skrev Jan Høydahl <[email protected]>:
> 
> Please vote for release candidate 2 for Solr 9.0.0
> 
> The artifacts can be downloaded from:
> https://dist.apache.org/repos/dist/dev/solr/solr-9.0.0-RC2-rev-e7a6447013008a70a4f40fcfd793fe3e2dcf37c2
> 
> You can run the smoke tester directly with this command:
> 
> python3 -u dev-tools/scripts/smokeTestRelease.py \
> https://dist.apache.org/repos/dist/dev/solr/solr-9.0.0-RC2-rev-e7a6447013008a70a4f40fcfd793fe3e2dcf37c2
> 
> You are encouraged to do an extra thorough test and manual inspection beyond
> running the smoketester, since this is a major release.
> 
> You can build a release-candidate of the official docker image using the 
> following command:
> 
> DIST_BASE=https://dist.apache.org/repos/dist/dev/solr && \
>  RC_FOLDER=solr-9.0.0-RC2-rev-e7a6447013008a70a4f40fcfd793fe3e2dcf37c2 && \
>  docker build $DIST_BASE/$RC_FOLDER/solr/docker/Dockerfile.official \
>  --build-arg SOLR_DOWNLOAD_URL=$DIST_BASE/$RC_FOLDER/solr/solr-9.0.0.tgz \
>  -t solr-rc:9.0.0-2
> 
> The vote will be open for at least 72 hours i.e. until 2022-04-02 19:00 UTC.
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Here is my +1
> 
> SUCCESS! [0:53:16.741542]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to