Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
1
Description
Following his link to understand FTS behavior with replicas and failover and rebalance ..
It says ..
If multiple nodes run the Search Service, Full Text Indexes are partitioned, and are automatically distributed across those nodes. If a Search Service node is failed over, it stops taking traffic. If no other nodes run the Search Service, all building of Full Text Indexes stops, and searches fail. If at least one other node is running the Search Service, this continues to handle queries and return partial results. |
|
|
When rebalance occurs:
|
|
|
If replica Full Text Indexes have been configured, the Search Service promotes the replicas to active on the remaining nodes of the cluster.
|
|
|
If replica Full Text Indexes have not been configured, the Search Service rebuilds the indexes on the remaining nodes of the cluster, using stored index definitions.
|
|
|
Note that the Search Service is not supported by Delta Recovery.
|
I would reword this as if replicas were enabled and a node were failed-over, the replica(s) would immediately be promoted to primary. Upon rebalance if the cluster can support it, more replicas will be generated.