Summary:
Solr not working after FileCloud 23.232 upgrade
Question/Issue Description:
Solr is not working after FileCloud 23.232 upgrade, even after installing OpenJDK 11, the old solr core is not loaded.
Environment Details:
Product - FileCloud Server
Version - FileCloud 23.232 or higher
Platform - OnPremise
Resolution/Workaround:
FileCloud 23.232 or higher versions come with Solr 9.4 or higher, while old versions use Solr 8.11. The upgrade script should automatically handle this migration to Solr 9.4 or higher, but in some cases, it may fail.
The below steps can fix the issue:
1. Verify OpenJDK 11 is installed
2. Stop Solr service (On Windows using the control panel, in Linux service solr stop)
3. Verify the old cores are present inside the solr home data folder:
Windows: xampp\solr\server\solr
Linux: /opt/solrfcdata/var/solr/data
4. If the old cores are not present in Windows, copy the old cores from the renamed "xampp" folder "xampp_date_of_upgrade\solr\server\solr\fccore" created during the upgrade process to xampp\solr\server\solr.
For Linux, the home data directory /opt/solrfcdata/var/solr/data should be the same.
5. Once your core folder is in place, copy the solrconfig.xml file from the web root directory to the core config directory after renaming the existing solrconfig.xml file.
The existing solrconfig.xml from Solr 8.11 will be a 55 KB file, rename this file located at:
Windows: xampp\solr\server\solr\fccore\conf\solrconfig.xml
Linux: /opt/solrfcdata/var/solr/data/fccore/conf/solrconfig.xml
Copy the new solrconfig.xml (18 KB file) from the source path:
Windows: xampp\htdocs\thirdparty\overrides\solarium\Solarium\fcskel\conf\solrconfig.xml
Linux: /var/www/html/thirdparty/overrides/solarium/Solarium/fcskel/conf/solrconfig.xml
To destination Folder:
Windows: xampp\solr\server\solr\fccore\conf\
Linux: /opt/solrfcdata/var/solr/data/fccore/conf/
6. Restart the Solr service (On Windows using the control panel and in Linux by running service solr start)
7. Verify the Solr configuration from FileCloud Admin Portal>Settings>Solr.
If the issue is seen with the tenant site, the solr core name should be changed in reference to the tenant site, ie any reference to fccore to fccore_sitename etc.