All Classes and Interfaces

Class
Description
 
Launcher of applications: base class
 
Always restart policy allows for restarts for long live components which never terminate.
Artifact of an service component.
Artifact Type.
The system is in a bad state
 
An exception to raise on a bad configuration
 
build a classpath -allows for entries to be injected in front of YARN classpath as well as behind, adds appropriate separators, extraction of local classpath, etc.
 
 
 
 
Generic code to get the URLs for clients via the registry
Build a single command line to include in the container commands; Special support for JVM command buildup.
Some general comparators
Little template class to reverse any comparitor
 
 
One or more components of the service.
 
Policy of restart component.
Status of upgrade.
Containers of a component.
 
 
Monitors the health of containers of a specific component at a regular interval.
 
 
 
 
 
Interface for Component Restart policies.
 
 
A config file that needs to be created and made available as a volume in an service component container.
Config Type.
 
Methods to aid in config, both in the Configuration class and with other parts of setting up Slider-initated processes.
Set of configuration properties that can be injected into the service components via envs, files and custom pluggable helper docker containers.
 
An instance of a running service container.
 
Launch context of a component.
The current state of the container of an application.
 
These are constants unique to the Slider AM
 
A probe that checks whether the AM has retrieved an IP for a container.
 
 
 
 
 
 
A duration in milliseconds.
 
 
Get the exit code of an exception.
 
A probe that checks whether a successful HTTP response code can be obtained from a container.
Http connection utilities.
Command line builder purely for the Java CLI.
Support for marshalling objects to and from JSON.
The kerberos principal of the service.
 
The status of localization.
Build up log entries for ease of splunk
Config keys for monitoring
Various utils to work with the monitor
Policy for components with instances that do not require/support a restart.
Policy for components that require restarts for instances on failure.
Utility class to validate strings against a predefined pattern.
Placement constraint details.
Advanced placement policy of the components of a service.
The scope of placement for the containers of a component.
The type of placement - affinity/anti-affinity/affinity-with-cardinality with containers of another component or containers of the same component (self).
A probe that checks whether a container has a specified port open.
a scanner which can take an input string for a range or scan the lot.
Base class of all probes.
Status message of a probe.
Base class for factories.
 
This holds any information that is resolved during building the launch context for a container.
This is a factoring out of methods handy for providers.
JSON-serializable description of a published key-val configuration.
Output a published configuration
 
 
 
 
 
 
A custom command or a pluggable helper container to determine the readiness of a container of a component.
Type.
Resource determines the amount of resources (vcores, memory, network, etc.)
ResourceInformation determines unit/name/value of resource types in addition to memory and vcores.
 
 
Serialized form of an service report which can be persisted and then parsed.
An Service resource has the following attributes.
This class defines constants that can be used in input spec for variable substitutions
 
 
A service launch exception that includes an exit code; when caught by the ServiceLauncher, it will convert that into a process exit code.
Write the metrics to a ATSv2.
 
 
The current state of an service.
The current status of a submitted service, returned as a response to the GET API.
Slider entities that are published to ATS.
Events that are used to store in ATS.
Constants which are stored as key in ATS
A single service that publishes all the Timeline Entities.
These are slider-specific Util methods
Process termination handler - exist with specified exit code after waiting a while for ATS state to be in sync.
 
 
Extends Core Filesystem with operations to manipulate ClusterDescription persistent state
 
 
 
Used to raise a usage exception ... this has the exit code LauncherExitCodes.EXIT_USAGE
Registry view for providers.