Umbraco Examine Indexing Large Sites ThreadAbort Timeout Error Workaround
System: Umbraco Version - 4.7.1 ,Windows Server 2008 ﾖ 8gb memory ﾖ 4 Zeon 2.27Ghz processors service pack 1 ﾖ 64 bit OS , IIS version 7.5.7600.16385, SQL Server 2008 R2, Stacktrace - N/A. Size of Content is 35 mb, defined as a large site.
We are affected by the problem detailed below which is a known Umbraco bug w/4.71. We would like to know how you to implement the following solution shown in bold:
The current solution is to split the Lucene .add files into folders with 500 in each, which improves the IO performance.
"This relates to a problem with Umbraco Examine indexing very large Umbraco sites. The issue is being looked at by the core Examine team, however if like us you can’t wait – the below describes a workaround we used:
As part of an Umbraco 4.7 (which ended up being a 4.7.1 upgrade for other reasons) we had an issue with the UmbracoExamine indexing timing out when initially creating the internal indexes for Members and Content respectively.
This initial indexing action happens on the application start as the UmbracoEventManager constructor calls EnsureIndexesExist().
The item is logged in the work item here: http://examine.codeplex.com/workitem/10324 – and the good people at the Farm have already started working on a solution.
The current solution is to split the Lucene .add files into folders with 500 in each, which improves the IO performance. Another very welcome addition is a new RebuildOnAppStart configuration setting in the ExamineSettings.config file:
Umbraco Examine Indexing Large Sites ThreadAbort Timeout Error Workaround
System: Umbraco Version - 4.7.1 ,Windows Server 2008 ﾖ 8gb memory ﾖ 4 Zeon 2.27Ghz processors service pack 1 ﾖ 64 bit OS , IIS version 7.5.7600.16385, SQL Server 2008 R2, Stacktrace - N/A. Size of Content is 35 mb, defined as a large site.
We are affected by the problem detailed below which is a known Umbraco bug w/4.71. We would like to know how you to implement the following solution shown in bold:
The current solution is to split the Lucene .add files into folders with 500 in each, which improves the IO performance.
"This relates to a problem with Umbraco Examine indexing very large Umbraco sites. The issue is being looked at by the core Examine team, however if like us you can’t wait – the below describes a workaround we used: As part of an Umbraco 4.7 (which ended up being a 4.7.1 upgrade for other reasons) we had an issue with the UmbracoExamine indexing timing out when initially creating the internal indexes for Members and Content respectively.
This initial indexing action happens on the application start as the UmbracoEventManager constructor calls EnsureIndexesExist(). The item is logged in the work item here: http://examine.codeplex.com/workitem/10324 – and the good people at the Farm have already started working on a solution.
The current solution is to split the Lucene .add files into folders with 500 in each, which improves the IO performance. Another very welcome addition is a new RebuildOnAppStart configuration setting in the ExamineSettings.config file:
is working on a reply...