Task #3061
Updated by Skye Roseboom about 12 years ago
In order to change and modify the schema for the CN search index backed by solr, an upgrade procedure is needed.
Solr's CoreAdminHandler provides many features to help with this - including dynamic core creation, reloading, removal and swapping of cores. This should allow us to create our 'next' index while the current search index remains live. Once the new index is rebuilt, solr's core admin SWAP command will atomically swap the 'current live' core with the 'next' core without interruption of service.
http://wiki.apache.org/solr/CoreAdmin
Need to provide tooling/scripting for automating this process:
1. Delete old core by name if exists.
2. Create new core (based on live template?) Deploy new index schema.xml
3. Reload 'next' core to effect schema.xml update.
4. Index 'next' core using index build tool pointed to new core.
5. Use solr core admin "SWAP" to switch cores - 'next' with 'current/live'
6. After new core is verified - Eventually delete/remove old core.
Also need to test to ensure that the SWAP over does not interfere with index-processing as it runs (it really shouldn't).
Solr's CoreAdminHandler provides many features to help with this - including dynamic core creation, reloading, removal and swapping of cores. This should allow us to create our 'next' index while the current search index remains live. Once the new index is rebuilt, solr's core admin SWAP command will atomically swap the 'current live' core with the 'next' core without interruption of service.
http://wiki.apache.org/solr/CoreAdmin
Need to provide tooling/scripting for automating this process:
1. Delete old core by name if exists.
2. Create new core (based on live template?) Deploy new index schema.xml
3. Reload 'next' core to effect schema.xml update.
4. Index 'next' core using index build tool pointed to new core.
5. Use solr core admin "SWAP" to switch cores - 'next' with 'current/live'
6. After new core is verified - Eventually delete/remove old core.
Also need to test to ensure that the SWAP over does not interfere with index-processing as it runs (it really shouldn't).
