public interface ClusterConfig extends Config<ClusterConfig>
The cluster configuration is used by Vertigo to determine how the
components of a network should be deployed. When a network is deployed
in a Vert.x clustered instance, the network can be deployed across the
cluster in what is known as the CLUSTER scope. Users
can specify in the cluster configuration how a network should be
deployed.
| Modifier and Type | Field and Description |
|---|---|
static String |
CLUSTER_ADDRESS
address is the cluster event bus address. |
static String |
CLUSTER_SCOPE
scope is the cluster scope. |
| Modifier and Type | Method and Description |
|---|---|
String |
getAddress()
Returns the cluster address.
|
ClusterScope |
getScope()
Returns the network scope.
|
ClusterConfig |
setAddress(String address)
Sets the cluster address.
|
ClusterConfig |
setScope(ClusterScope scope)
Sets the network scope.
|
static final String CLUSTER_ADDRESS
address is the cluster event bus address.static final String CLUSTER_SCOPE
scope is the cluster scope.ClusterConfig setAddress(String address)
The cluster address is used by Vertigo to deploy components and work
with cluster-wide data structures when the network is clustered. If
the network is deployed in LOCAL scope then the cluster
address does not need to be set up.
address - The cluster address.String getAddress()
ClusterConfig setScope(ClusterScope scope)
Setting the network's scope to CLUSTER will result in the
network's components being deployed across the cluster when Vert.x is
a clustered instance. If the cluster scope is being used you must provide
an event bus address to the cluster manager. This is the default scope.
If the scope is set to LOCAL then the network will always
be deployed in the local Vert.x instance regardless of the Vert.x cluster
state.
scope - The network scope.ClusterScope getScope()
CLUSTERCopyright © 2013-2014. All Rights Reserved.