com.bigdata.jini.start.config
Interface ServicesManagerConfiguration.Options
- All Superinterfaces:
- BigdataServiceConfiguration.Options, JavaServiceConfiguration.Options, JiniClientConfig.Options, JiniServiceConfiguration.Options, ServiceConfiguration.Options
- Enclosing class:
- ServicesManagerConfiguration
public static interface ServicesManagerConfiguration.Options
- extends BigdataServiceConfiguration.Options
Configuration options.
- Version:
- $Id$
- Author:
- Bryan Thompson
SERVICES
static final String SERVICES
- An array of the names of the service configurations that will be
started by the
ServicesManagerServer. For each value declared
in this array, there must be a corresponding component defined within
the Configuration.
There are four basic kinds of entries for this array:
- jini
- This value is recognized as the jini core services and an
instance of
JiniCoreServicesConfiguration is created from the
corresponding configuration component.
QuorumPeerMain
- This value is recognized as the zookeeper server and an instance
of a
ZookeeperServerConfiguration is created from the
corresponding configuration component.
-
Any of
DataServer, ClientServer,
TransactionServer, LoadBalancer,
MetadataServer.
- These are the known bigdata server classes. An instance of the
corresponding
BigdataServiceConfiguration is created from the
corresponding component. For example, DataServerConfiguration
is created if the component name is DataServer.
- other
-
Any other value is interpreted as a java service configuration. The
name of the component is understood as the name of the main class to
execute unless the
JavaServiceConfiguration.Options.CLASS_NAME property is
explicitly specified. This makes it possible to create more than one
configuration of the same component. However, this only works for
generic java services. The
org.apache.log4j.net.SimpleSocketServer can be started in
this manner. You can also use this to run the ServiceStarter
and specify the NonActivatableServiceDescriptor in the
component configuration.
- See Also:
ServicesManagerConfiguration.getServiceConfigurations(Configuration),
Constant Field Values
ZOOKEEPER_DISCOVERY_TIMEOUT_NANOS
static final String ZOOKEEPER_DISCOVERY_TIMEOUT_NANOS
- The time in nanoseconds that the
ServicesManagerServer will
wait the discovery of the zookeeper ensemble before throwing a fatal
exception (default
).
The default is relatively long (a few minutes) so service managers
will normally wait around long enough for zookeeper to start. However,
zookeeper discovery is event driven so the services manager will only
wait as long as necessary.
- See Also:
- Constant Field Values
DEFAULT_ZOOKEEPER_DISCOVERY_TIMEOUT_NANOS
static final long DEFAULT_ZOOKEEPER_DISCOVERY_TIMEOUT_NANOS
Copyright © 2006-2011 SYSTAP, LLC. All Rights Reserved.