Uses of Interface
org.apache.storm.daemon.supervisor.ExitCodeCallback
Package
Description
-
Uses of ExitCodeCallback in org.apache.storm.container
Modifier and TypeMethodDescriptionvoid
DefaultResourceIsolationManager.launchWorkerProcess
(String user, String topologyId, Map<String, Object> topoConf, int port, String workerId, List<String> command, Map<String, String> env, String logPrefix, ExitCodeCallback processExitCallback, File targetDir) void
ResourceIsolationInterface.launchWorkerProcess
(String user, String topologyId, Map<String, Object> topoConf, int port, String workerId, List<String> command, Map<String, String> env, String logPrefix, ExitCodeCallback processExitCallback, File targetDir) After reserving resources for the worker (i.e. calling reserveResourcesForWorker), this function can be used to launch worker process. -
Uses of ExitCodeCallback in org.apache.storm.container.cgroup
-
Uses of ExitCodeCallback in org.apache.storm.container.docker
-
Uses of ExitCodeCallback in org.apache.storm.container.oci
-
Uses of ExitCodeCallback in org.apache.storm.daemon.supervisor
Modifier and TypeMethodDescriptionstatic Process
ClientSupervisorUtils.launchProcess
(List<String> command, Map<String, String> environment, String logPrefix, ExitCodeCallback exitCodeCallback, File dir) Launch a new process as perProcessBuilder
with a given callback.static Process
ClientSupervisorUtils.processLauncher
(Map<String, Object> conf, String user, List<String> commandPrefix, List<String> args, Map<String, String> environment, String logPreFix, ExitCodeCallback exitCodeCallback, File dir)