Interface to get status of a Lock without getting access to acquire/release lock.
With this interface, the procedure framework provides means to collect following set of metrics per procedure type for all procedures: Count of submitted procedure instances Time histogram for successfully completed procedure instances Count of failed procedure instances Please implement this interface to return appropriate metrics.
Keep track of the runnable procedures
Account of what procedures are running on remote node.
Remote procedure reference.
Inline Chores (executors internal chores).
Locking for mutual exclusion between procedures.
Base Procedure class responsible for Procedure Metadata; e.g.
Basic ProcedureEvent that contains an "object", which can be a description or a reference to the resource to wait on, and a queue for suspended procedures.
Thread Pool that executes the submitted procedures.
Internal cleaner that removes the completed procedure results after a TTL.
Special procedure used as a chore.
Helper to convert to/from ProcedureProtos
A serializer (deserializer) for those Procedures which were serialized before this patch.
A serializer for our Procedures.
|RemoteProcedureDispatcher<TEnv,TRemote extends Comparable<TRemote>>||
A procedure dispatcher that aggregates and sends after elapsed time or after we hit count threshold.
Delayed object that holds a FutureTask.
Data structure with reference to remote operation.
Internal state of the ProcedureExecutor that describes the state of a "Root Procedure".
A SequentialProcedure describes one step in a procedure chain:
Simple scheduler for procedures
Procedure described by a series of steps.
Runs task on a period such as check for stuck workers.
Thrown when a procedure is aborted
A RemoteProcedureException is an exception from another thread or process.
Copyright © 2007–2018 The Apache Software Foundation. All rights reserved.