module Mongo::Cluster::Topology

Defines behavior for getting servers.

Topologies are associated with their clusters - for example, a ReplicaSet topology contains the replica set name. A topology object therefore cannot be used with multiple cluster objects.

At the same time, topology objects do not know anything about specific servers in a cluster, despite what their constructor may suggest. Which means, in particular, that topology change events require the application to maintain cluster references on its own if it wants to track server changes within a replica set.

@since 2.0.0

Constants

OPTIONS

The various topologies for server selection.

@since 2.0.0

Public Instance Methods

initial(seeds, monitoring, options) click to toggle source

Get the initial cluster topology for the provided options.

@example Get the initial cluster topology.

Topology.initial(topology: :replica_set)

@param [ Array<String> ] seeds The addresses of the configured servers. @param [ Monitoring ] monitoring The monitoring. @param [ Hash ] options The cluster options.

@return [ ReplicaSet, Sharded, Single ] The topology.

@since 2.0.0

# File lib/mongo/cluster/topology.rb, line 60
def initial(seeds, monitoring, options)
  if options.has_key?(:connect)
    OPTIONS.fetch(options[:connect].to_sym).new(options, monitoring, seeds)
  elsif options.has_key?(:replica_set)
    ReplicaSet.new(options, monitoring, seeds)
  else
    Unknown.new(options, monitoring, seeds)
  end
end