FAQ - Search G2 Apache Solr Upgrade
Important Notice - The Solr upgrade was not completed on Feb 17 and has been rescheduled to April 27.
Q1: What is Apache Solr?
A1: Apache Solr, also known as Solr, is the technology behind Search G2.
Q2: What version are we moving from/to?
A2: We are moving from version 6 to version 9 of Solr. Moving to Solr version 9 will add increased stability to the Search G2 platform.
Q3: When will the upgrade take place?
A3: The upgrade will now take place Saturday, April 27, 2024, from 9am to 5pm MDT.
Q4: Has the upgrade process been tested?
A4: Yes, we have extensively tested the upgrade process to ensure its reliability and effectiveness. In addition, a consultative exercise was undertaken to ensure we utilize the most effective and secure steps in the process.
Q5: Can I test myself?
A5: Yes, you can test your site against a static copy on Solr 9. Please see below for testing details.
Q6: What is the process on April 27?
A6: On April 27, we will begin the upgrade process at 9am MDT and aim to complete it by 11am MDT. From 11am MDT to 4pm MDT, we recommend that customers test their search functionality. Note that we recommend testing before the upgrade as well as after. If you experience any issues when testing please reach out to support@crownpeak.com.
Q7: What happens to any items that are published during the upgrade?
A7: Any items published during the upgrade will go into a queue. These updates will be synchronized with Solr 9 at the end of the day once all testing has been completed.
Q8: What if we find some problems during or after the upgrade?
A8: If customers experience issues that cannot be resolved at the time, we may have to cancel the upgrade and revert to Solr 6. This will be done before any updates are processed to ensure minimal disruption.
Q9: Will the changes affect our website on the day?
A9: End users will not see any adverse affects on client sites and will able to search what has been published up to that point. Any items published on the day won't become available until after the maintenance is complete and any queued assets are processed.
Testing Instructions
In order to test correctly you must first determine if your Search G2 queries happen on the front end (non-restricted) or back end (restricted). If you have any difficulty please reach out to your TAM, Customer Success Manager or Support.
Solr 9 Test Endpoints
Unrestricted: https://searchg2-dev.crownpeak.net
Restricted: https://searchg2-restricted-dev.crownpeak.net
- Search queries - Use the same exact URI as production, but with the test endpoints above instead of production e.g.
- Unrestricted
- Prod: https://searchg2.crownpeak.net/my-collection/select?q=*:*
- Test Endpoint: - https://searchg2-dev.crownpeak.net/my-collection/select?q=*:*
- Restricted (use the same cert as prod)
- Prod: https://searchg2-restricted.crownpeak.net/my-collection/select?q=*:*
- Test Endpoint: https://searchg2-restricted-dev.crownpeak.net/my-collection/select?q=*:*
- If testing CORS, please add a local host entry with one of the IPs from the test endpoint:
- Verify current IPs of the test endpoint with nslookup:
nslookup searchg2-dev.crownpeak.net
Server: test-dns-ns01
Address: 10.1.0.1
Non-authoritative answer:
Name: searchg2-dev.crownpeak.net
Addresses: 52.87.22.153
52.2.137.172
- Add your host entry for searchg2.crownpeak.net
52.87.22.153 searchg2.crownpeak.net
- For customers testing document inserts using a custom endpoint, use the same method you normally would, using the test endpoints. Example using cURL:
- Prod:
curl -u single-doc-updater-mycoll:mypass -X POST -H 'Content-Type: application/json' 'https://searchg2.crownpeak.net/mycoll/update' -data-binary '
{
...
}'
- Test Endpoint:
curl -u single-doc-updater-mycoll:mypass -X POST -H 'Content-Type: application/json' 'https://searchg2-dev.crownpeak.net/mycoll/update' -data-binary '
{
...
}'
- To test search queries or document inserts/updates from a custom application, please change the endpoint to use the test endpoint provided above.
