Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade from Solr 7.3.1 to 7.7.2 #6633

Closed
pdurbin opened this issue Feb 10, 2020 · 6 comments · Fixed by #6631
Closed

Upgrade from Solr 7.3.1 to 7.7.2 #6633

pdurbin opened this issue Feb 10, 2020 · 6 comments · Fixed by #6631

Comments

@pdurbin
Copy link
Member

pdurbin commented Feb 10, 2020

We're using Solr 7.3.1 but Solr 7.7.2 is out. We should upgrade.

Here's the changelog: https://lucene.apache.org/solr/7_7_2/changes/Changes.html

@donsizemore
Copy link
Contributor

solr_7.7.2.zip

@poikilotherm
Copy link
Contributor

@donsizemore I don't get it... I don't see any critical things - what am I missing?

@donsizemore
Copy link
Contributor

donsizemore commented Feb 13, 2020

@poikilotherm I thought things looked good!

The only repeated SEVERE I see during the API test suite is

java.lang.IllegalAccessException: Class edu.harvard.iq.dataverse.search.SearchServiceBean can not access a member of class edu.harvard.iq.dataverse.search.SearchFields with modifiers "private static transient"

which showed up 159 times...

@poikilotherm
Copy link
Contributor

poikilotherm commented Feb 13, 2020

So maybe @pdurbin accidentially hit the wrong emoji 🤣
Is this SEVERE thing also popping up with 7.3.1? It looks like a deeper code issue.

Crawling the logs for the exception reveals 159 of em', all pointing to

staticSearchField = (String) fieldObject.get(searchFieldsObject);

The exception is caused by reflection accessing a private field. I am not sure what fields, because there are no private fields in SearchFields.java.

After some more digging: this looks like an issue on its own, unrelated to our change of Solr. This is completely a matter of Java Reflection API usage and needs deeper debugging.

@poikilotherm
Copy link
Contributor

I already created an issue to track the log messages, should I also create a fresh issue for those deprecation warnings from Solr? @pdurbin @kcondon

@pdurbin
Copy link
Member Author

pdurbin commented Feb 14, 2020

@poikilotherm assuming you're talking about the deprecation warnings you mentioned at #6599 (comment) , yes, a fresh focused "small chunk" issue would absolutlely be welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants