I've just configures Umbraco and Examine to work on my NLB servers with a central file system. This all works well except for the FullTextSearch. Every time I publish, I get the exception: Cannot index queue items, the index is currently locked.
What settings am I missing? I image it has something to with the ExamineSettings.config. I did have to update the examine providers to work with NLB, but didn't know what to do with the entry for FullTextSearch.
There are some folders/files that can't be shared in a load balanced setup. There are other considerations as well. Have a look at this detailed guide on how to properly do LBE with umbraco
I followed that document pretty closely and except for FullTextSearch, managed to get the setup working well on our NLB. This includes the Examine/Lucene section that recommends adding the UmbracoExamine.TempStorage DLLs and configurations.
Is there anything I could do to the FullTextSearch settings to get it to work with local storage (a la the TempStorage package)?
I'm guessing it is not aware of the "different" way the index locations are handled in the TempStorage library you have. As you probably guessed, the FullTextSearch folks are better to answer this (I was just pointing out the LBE specific stuff, but you've already got that nailed).
One suggestion, you could try creating each web server's /temp/examineindexes/ folder at a unique location on the fileshare, then set up a virtual directory to point to the unique location, and update the examine config accordingly. It's not as elegant a solution as the TempStorage approach, but it's how we suggested the config until TempStorage was an option.
Load Balanced Network - File Locks
I've just configures Umbraco and Examine to work on my NLB servers with a central file system. This all works well except for the FullTextSearch. Every time I publish, I get the exception: Cannot index queue items, the index is currently locked.
What settings am I missing? I image it has something to with the ExamineSettings.config. I did have to update the examine providers to work with NLB, but didn't know what to do with the entry for FullTextSearch.
@Matthew
There are some folders/files that can't be shared in a load balanced setup. There are other considerations as well. Have a look at this detailed guide on how to properly do LBE with umbraco
https://our.umbraco.org/documentation/Installation/load-balancing
Hi, @Paul.
Thanks for the swift reply.
I followed that document pretty closely and except for FullTextSearch, managed to get the setup working well on our NLB. This includes the Examine/Lucene section that recommends adding the UmbracoExamine.TempStorage DLLs and configurations.
Is there anything I could do to the FullTextSearch settings to get it to work with local storage (a la the TempStorage package)?
@Matthew -
I'm guessing it is not aware of the "different" way the index locations are handled in the TempStorage library you have. As you probably guessed, the FullTextSearch folks are better to answer this (I was just pointing out the LBE specific stuff, but you've already got that nailed).
One suggestion, you could try creating each web server's /temp/examineindexes/ folder at a unique location on the fileshare, then set up a virtual directory to point to the unique location, and update the examine config accordingly. It's not as elegant a solution as the TempStorage approach, but it's how we suggested the config until TempStorage was an option.
is working on a reply...