Sitecore Stack Exchange is a question and answer site for developers and end users of the Sitecore CMS and multichannel marketing software. It only takes a minute to sign up.
Sign up to join this community
We are planning on changing from Lucene to Solr due to number of items and because we have more than one CM server.
What are the steps needed to migrate default lucene indexes to Solr? Is it just a matter of enabling all .Solr.config files or will we need to do much more than that?
We also have one custom lucene index we use on the site to query items. Is it a massive job to migrate this?
Using Sitecore 8.1
As others have said here there are a number of steps to do this:
This official Sitecore documentation covers most of this fairly well: https://doc.sitecore.net/sitecore_experience_platform/80/setting_up__maintaining/search_and_indexing/walkthrough_setting_up_solr
However I'm going to pick up on the more complex/time consuming ones of these and break them down for you.
There are some other ways to do this such as using bitnami, but here is the full manual install process using Apache Tomcat.
One of the steps that takes the longest is switching all the configs to use Solr. There is a Powershell script below that will do this for you:
Function Set-SCSearchProvider {
$rootPath = Read-Host "What is the path of your Sitecore instance's website folder?";
$choice = Read-Host "(L)ucene or (S)olr?";
$validInput = $true;
#test that path is valid
If (!(Test-Path -Path $rootPath))
{
Write-Host "The supplied path was invalid or inaccessible." -ForegroundColor Red;
$validInput = $false;
}
#test that choice is valid
ElseIf (($choice -ne "L") -and ($choice -ne "S"))
{
Write-Host "You must choose L or S." -ForegroundColor Red;
$validInput = $false;
}
If ($validInput)
{
If (($choice -eq "L"))
{
Write-Host "Set to Lucene." -ForegroundColor Yellow;
$selectedProvider = "Lucene";
$deselectedProvider = "Solr";
}
ElseIf (($choice -eq "S"))
{
Write-Host "Set to Solr." -ForegroundColor Yellow;
$selectedProvider = "Solr";
$deselectedProvider = "Lucene";
}
#enumerate all config files to be enabled
$filter = "*" + $selectedProvider + "*.config*";
$filesToEnable = Get-ChildItem -Recurse -File -Path $rootPath -Filter $filter;
foreach ($file in $filesToEnable)
{
Write-Host $file.Name;
if (($file.Extension -ne ".config"))
{
$newFileName = [io.path]::GetFileNameWithoutExtension($file.FullName);
$newFile = Rename-Item -Path $file.FullName -NewName $newFileName -PassThru;
Write-Host "-> " $newFile.Name -ForegroundColor Green;
}
}
#enumerate all config files to be disabled
$filter = "*" + $deselectedProvider + "*.config*";
$filesToDisable = Get-ChildItem -Recurse -File -Path $rootPath -Filter $filter;
foreach ($file in $filesToDisable)
{
Write-Host $file.Name;
if ($file.Extension -eq ".config")
{
$newFileName = $file.Name + ".disabled";
$newFile = Rename-Item -Path $file.FullName -NewName $newFileName -PassThru;
Write-Host "-> " $newFile.Name -ForegroundColor Green;
}
}
} }
Set-SCSearchProvider
Originally from here: https://gist.github.com/patrickperrone/59b8745ee8b8ff9045b5
This is a really quick way of renaming your configs. We use this during deployments also from Octopus.
There is a great guide for more info on setting up Solr here: https://sitecore-community.github.io/docs/search/solr/fast-track-solr-for-lazy-developers/
With regard to your custom index. Migrating the index to Solr should work but as mentioned above it depends on the kind of queries you are doing, you may need to refactor some of your code/config after migration. We have 3 or 4 custom Solr indexes and they work fine.
It depends on your solution, but there are some other steps that you might need to take. I recently did the same and, we had to:
Planning on writing a blog on the experience, but didn't find the time yet.
So it might be some more work, but it could go all smoothly.
To enable Solr for Sitecore, you'll need to perform the following steps:
Sitecore now has several documentation articles posted online for Lucene to Solr conversion. There are also lots of other blog posts describing the process. See:
Just wanted to add to this discussion by posting that I wrote a little PowerShell to help you with adding the cores via the API. Makes it a lot easier that adding each one, one by one. You can edit the path to the cores and data files in the script.
AddCores.ps1
function Add-Core([string]$coreName)
{
try {$request = "http://localhost:8983/solr/admin/cores?action=CREATE&name={0}&instanceDir=C:\Bitnami\solr-5.4.1-0\apache-solr\solr\{0}&config=solrconfig.xml&schema=schema.xml&dataDir=data" -f $coreName} catch {}
echo $request
$response = Invoke-RestMethod $request
}
$cores = @(
"bonfire_configs",
"sitecore_analytics_index",
"sitecore_analytics_index_rebuild",
"sitecore_core_index",
"sitecore_core_indexMainAlias",
"sitecore_core_indexMainAlias_rebuild",
"sitecore_core_index_rebuild",
"sitecore_fxm_master_index",
"sitecore_fxm_master_index_rebuild",
"sitecore_fxm_web_index",
"sitecore_fxm_web_index_rebuild",
"sitecore_list_index",
"sitecore_list_index_rebuild",
"sitecore_marketingdefinitions_master",
"sitecore_marketingdefinitions_master_rebuild",
"sitecore_marketingdefinitions_web",
"sitecore_marketingdefinitions_web_rebuild",
"sitecore_marketing_asset_index_master",
"sitecore_marketing_asset_index_master_rebuild",
"sitecore_marketing_asset_index_web",
"sitecore_marketing_asset_index_web_rebuild",
"sitecore_master_index",
"sitecore_master_indexMainAlias",
"sitecore_master_indexMainAlias_rebuild",
"sitecore_master_index_rebuild",
"sitecore_suggested_test_index",
"sitecore_suggested_test_index_rebuild",
"sitecore_testing_index",
"sitecore_testing_index_rebuild",
"sitecore_web_index",
"sitecore_web_indexMainAlias",
"sitecore_web_indexMainAlias_rebuild",
"sitecore_web_index_rebuild",
"social_messages_master",
"social_messages_master_rebuild",
"social_messages_web",
"social_messages_web_rebuild"
)
foreach ($core in $cores) {
Add-Core -coreName $core
}
