Upgrade Solr version to 9.5.0 #56
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The main addition for deployment is that `SOLR_*` environment variables will now be resolved by Solr to set the corresponding system properties, it makes using `environment` in Docker Compose files even more powerful. References: * https://solr.apache.org/guide/solr/9_5/upgrade-notes/major-changes-in-solr-9.html#solr-9-5 * https://solr.apache.org/guide/solr/9_5/deployment-guide/solr-in-docker.html#solr-in-sh-configuration * https://github.com/metabrainz/musicbrainz-docker/tree/v-2024-02-16?tab=readme-ov-file#advanced-configuration
|
Starting from version 9.5.0, Solr has warnings about not finding the class It isn’t related to the changes in It seems to be related to our However, there is no error and I have had no issue with indexing places and searching for places locally. I wonder whether there is something wrong in our code or it might just be resolved in the future with SOLR-17069? Logs
|
|
@yvanzo the |
Thank you for this workaround. I’m not too sure if we are doing something wrong or if it is a regression from Solr 9.5.0 which resolves SOLR-17089. I’m trying to reach Solr users about it, and will report it upstream if confirmed as a regression. We are also working on SolrCloud deployment with Ansible, so this isn’t the only issue to address for production release.
Neither for me. |
Starting from Solr 9.5.0, the following innocuous but annoying warning
started to show up on server startup and when loading each core:
java.lang.NoClassDefFoundError: jakarta/activation/DataSource
It hasn’t been determined exactly why, but it is likely related to the
changes made to resolve https://issues.apache.org/jira/browse/SOLR-17089
|
I previously tested adding Jakarta Activation API and/or its Angus implementation to the Project Object Model as follows: <dependency>
<groupId>jakarta.activation</groupId>
<artifactId>jakarta.activation-api</artifactId>
<version>2.1.3</version>
</dependency> <dependency>
<groupId>org.eclipse.angus</groupId>
<artifactId>angus-activation</artifactId>
<version>2.0.2</version>
<scope>runtime</scope>
</dependency>All tries have been unsuccessful, as the classes were just added into the mb-solr JAR which is apparently not loaded by Solr when it needs these. So for now I just added the commit e27f341 to follow the above suggestion and it works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While we were testing Solr 9.4.0 for SEARCH-685, Solr 9.5.0 has been released.
It’s still time to upgrade to it before switching to Solr 9 in production.
Reference: https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html#solr-9-5