You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Please note that the feature described in #3499 is required reading for this issue.)
The mirroring split policy builds on the remoting split policy, treating each sub-index as a mirror of the super-index (upon which the split writer is built). The motivation for this policy is to allow a given index to be available on multiple nodes (that define a cluster), which helps to load-balance search requests across the nodes in that cluster, not to mention implement fail-over for index searchers.
Unlike other mirroring solutions for Lucene, this approach gives users the ability to (a) pick and choose the types of directories underlying the mirror, and (b) add/remove mirrors on the fly. However, note that the latter capability has not yet been implemented, although it will be soon.
(Please note that the feature described in #3499 is required reading for this issue.)
The mirroring split policy builds on the remoting split policy, treating each sub-index as a mirror of the super-index (upon which the split writer is built). The motivation for this policy is to allow a given index to be available on multiple nodes (that define a cluster), which helps to load-balance search requests across the nodes in that cluster, not to mention implement fail-over for index searchers.
Unlike other mirroring solutions for Lucene, this approach gives users the ability to (a) pick and choose the types of directories underlying the mirror, and (b) add/remove mirrors on the fly. However, note that the latter capability has not yet been implemented, although it will be soon.
Migrated from LUCENE-2434 by Karthick Sankarachary
Attachments: LUCENE-2434.patch
Linked issues:
The text was updated successfully, but these errors were encountered: