Package com.yahoo.vespa.config.content.core

Class StorDistributormanagerConfig.Minimum_replica_counting_mode

java.lang.Object
com.yahoo.config.Node
com.yahoo.config.LeafNode<ENUM>
com.yahoo.config.EnumNode<StorDistributormanagerConfig.Minimum_replica_counting_mode.Enum>
com.yahoo.vespa.config.content.core.StorDistributormanagerConfig.Minimum_replica_counting_mode
All Implemented Interfaces:
Cloneable
Enclosing class:
StorDistributormanagerConfig
public static final class StorDistributormanagerConfig.Minimum_replica_counting_mode extends com.yahoo.config.EnumNode<StorDistributormanagerConfig.Minimum_replica_counting_mode.Enum>
This class represents stor-distributormanager.minimum_replica_counting_mode For each available node, the distributor will report back to the cluster controller a value which indicates the minimum replication factor for any bucket contained on said node. This config exposes a way to alter how this replication factor is computed. Valid enum values and their semantics: TRUSTED - only trusted replicas are counted. ANY - any replica present is counted. This may return an overly optimistic view of the system. E.g. if there are 3 replicas, 1 having 1000 docs and 2 having 1 doc, all being out of sync, counting with ANY will still treat this as a minimum replication factor of 3. Conversely, with TRUSTED such a bucket would most likely have a factor of 0 (or 1 iff the trusted status for the replica with 1000 docs is known).