createOutputThread()
, if one is not already created. It then calls the loader()
method to load Voice-specific data, which include utterance processors.
deallocated
state.
@throws IllegalStateException if the recognizer is not in the DEALLOCATED
state
additional
sequence value objects in short order. There is no externally visible behavior of this method. It is used to potentially improve the efficiency of the algorithm of obtaining additional sequence value objects.
@param additional the number of additional values to allocate
service()
method called. If the servlet class does not implement SingleThreadModel
, the (only) initialized instance may be returned immediately. If the servlet class implements SingleThreadModel
, the Wrapper implementation must ensure that this instance is not allocated again until it is deallocated by a call to deallocate()
.
@exception ServletException if the servlet init() method threwan exception
@exception ServletException if a loading error occurs
@param bytes The number of bytes which the server should allocate. @return True if successfully completed, false if not. @exception FTPConnectionClosedException If the FTP server prematurely closes the connection as a result of the client being idle or some other reason causing the server to send FTP reply code 421. This exception may be caught either as an IOException or independently as itself. @exception IOException If an I/O error occurs while either sending acommand to the server or receiving a reply from the server.
The main interface between an ApplicationMaster
and the ResourceManager
.
The ApplicationMaster
uses this interface to provide a list of {@link ResourceRequest} and returns unused {@link Container} allocated to it via {@link AllocateRequest}.
This also doubles up as a heartbeat to let the ResourceManager
know that the ApplicationMaster
is alive. Thus, applications should periodically make this call to be kept alive. The frequency depends on ??
The ResourceManager
responds with list of allocated {@link Container}, status of completed containers and headroom information for the application.
The ApplicationMaster
can use the available headroom (resources) to decide how to utilized allocated resources and make informed decisions about future resource requests.
The main interface between an ApplicationMaster
and the ResourceManager
.
The ApplicationMaster
uses this interface to provide a list of {@link ResourceRequest} and returns unused {@link Container} allocated toit via {@link AllocateRequest}. Optionally, the ApplicationMaster
can also blacklist resources which it doesn't want to use.
This also doubles up as a heartbeat to let the ResourceManager
know that the ApplicationMaster
is alive. Thus, applications should periodically make this call to be kept alive. The frequency depends on {@link YarnConfiguration#RM_AM_EXPIRY_INTERVAL_MS} which defaults to{@link YarnConfiguration#DEFAULT_RM_AM_EXPIRY_INTERVAL_MS}.
The ResourceManager
responds with list of allocated {@link Container}, status of completed containers and headroom information for the application.
The ApplicationMaster
can use the available headroom (resources) to decide how to utilized allocated resources and make informed decisions about future resource requests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|