August 8, 2019 at 8:00 am
Hi All,
We have situation where we have a document DB with a Full-Text Index storing approx. 6 million rows and a document was uploaded, but, was not indexed. On further examination we noticed a number of errors in the FT log, so, after trying to address the errors without success, we dropped the index and created a new one with population set to Automatic and now the FT Log is showing 1000's upon 1000's of errors, to the point where the log grows to beyond 1gb within 3 or 4 days.
So, we restored a copy of the docs database in a test environment and tried changing the ft_timeout to 1200000, "max full-text crawl range" to 24 (Same as the number of logical cores on the test server), dropped the existing full-text index and catalog and created them on a separate, fast disk array, made sure there was plenty of memory available for full-text service, all without success. All any of this did was decrease the time it took to produce the same result.
We then disabled population on the test database and created another empty database, with the same structure as the disabled database and imported "batch's" of rows from the populated database to the empty database and after quite a bit of testing it became apparent that once we inserted more than 100 rows into the empty database, the log reflected that all of the rows failed, with the following log entry "Error '0x80043630: The filter daemon process MSFTEFD timed out for an unknown reason.", but after 3 or 4 retires, it successfully indexed them. if we inserted 100 or less they were all indexed without an issue the very first time and the 100 rows are were part of the failed rows that needed 3 or 4 retries to succeed.
Initially we tested on an instance of 2008 R2, but, then we tried on an instance of 2016 and we're seeing the same results. We're trying to understand how Full and Auto population works under the covers, so, we can try and figure out how to get this situation resolved, as, at the moment, we don't see this index ever finishing population due to the number of rows.
August 9, 2019 at 8:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply