Indexer does not restart after slice failover

• Article Type: General
• Product: Primo
• Product Version: 2

Description:
In an environment with multiple slices, when a slice fails failover takes place the indexer becomes a slice, replacing the failed slice. The failed slice does not get restarted as an indexer, and as a result, an attempt to run indexing will fail.

Resolution:
Until this defect is fixed, in order to fix such a situation the inactive slice must be restarted.

• Article last edited: 10/8/2013