Question

Indexing Queue 4.9 million documents taking 1/3-1/2 year to finish. Repository search shows only 390 documents as not indexed.

Laserfiche

Updated January 29, 2020

asked on July 23, 2019 • Show version history

Sometime in the last month and possibly after updating from 10.2 to 10.4 our full text indexing service has been chewing away at about 50% of the available CPU and memory.

The Queue is currently at 4.9 million documents and its processing about 30-50 documents a minute. Its going to take 3-5 months to complete.

I did a repository search for {LF:Indexed="N"} and it only found 390 documents that were not indexed. So it appears that nearly all of our ~5million documents are already indexed.

Anyone know what might have happened? How can we resolve it?

Could we have accidentally triggered a re-indexing? If so and we "clear the queue" will that stop the re-index?

0 0

Replies

replied on December 12, 2019

We upgraded from 10.3.1 to 10.4.1 last week and are seeing this same phenomena. What was your solution?

Our queue is growing and LFFTTS is using 27% of total CPU.

0 0

replied on December 13, 2019

You may want to look into using the QuickReindex utility.

0 0

View 1 previous reply

replied on December 13, 2019 • Show version history

I received that message just yesterday. I updated the driver without any issues and was able to run the utility.

0 0

replied on January 7, 2020 • Show version history

If you have an existing queue of 2 million + docs being indexed, can you still kick off the Quick Reindexing utility or do you need to stop the existing indexing service first?

0 0

replied on January 7, 2020

I would review the help documentation before you run the utility. You will notice when reviewing it that it states, "Note: If you choose to perform the quick reindex in place by specifying your current search catalog directory, you will need to stop your Laserfiche Search service before proceeding. If you choose another directory, full-text searches can continue to be run on your repository while the reindex process occurs. However, in the latter case, when the reindex is done you will need to stop the Laserfiche Search service, swap the existing index files for the new index files, and then restart the service.".

2 0

replied on December 13, 2019

We recently had a similar issue where a reindex job was going to take half a year to complete. Ask your VAR about LFFTS hotfix FTSKernel.dll 10.4.0.306. Our full reindex finished two days later.

0 0

replied on January 29, 2020

The Quick ReIndex utility fixed my issue.

0 0

You are not allowed to follow up in this post.

Question

Question

Indexing Queue 4.9 million documents taking 1/3-1/2 year to finish. Repository search shows only 390 documents as not indexed.

Replies

Sign in to reply to this post.