Duplicate Dedicated Content Indexer Names Can Propagate to the Same Workspace (283983)

MORE INFORMATION

In some situations, it is useful to create a configuration where multiple dedicated content indexers overwrite each other's catalogs. For example, if you have a dedicated content indexer workspace that is crawling a very large document corpus, and it takes three days to finish indexing this source, the catalog on the destination server gets updated only every three days when a new catalog is propagated. Therefore, users who are searching against the catalog may not find documents that are indexed in the last two days. When you configure an additional dedicated content indexer that has the same name, and the exact same set of content sources for it, if you start its index update at a different time, you can refresh the index on the destination workspace more frequently. For example, if the original dedicated content indexer starts its first index update on Monday, and it propagates its catalog on Wednesday, and then again on Saturday, if an additional dedicated content indexer starts an index update on Tuesday, it would propagate an updated catalog on Thursday, and then again on Sunday. In this scenario, you are refreshing the catalog more often than every three days. You can have up to four dedicated content indexer workspaces propagating to a single destination workspace; if you add an additional dedicated content indexer, you can have even more frequent updates.