worker_tracker v0.3.0 WorkerTracker

Link to this section Summary

Link to this section Functions

Link to this function

build_name(instance)

See WorkerTracker.Instance.Client.build_name/1.

Link to this function

create_instance(instance)

Link to this function

create_instances(instances)

Link to this function

execute_command(instance, command)

Link to this function

get_instance(instance_name)

Link to this function

get_instances()

See WorkerServer.get_instances/0.

Link to this function

instance_exists?(instance)

See WorkerTracker.Instance.Client.instance_exists?/1.

Link to this function

refresh_instance(instance)

See WorkerTracker.WorkerInstance.Server.refresh_instance/1.

Link to this function

start(type, args)

Called when an application is started.

This function is called when an application is started using Application.start/2 (and functions on top of that, such as Application.ensure_started/2). This function should start the top-level process of the application (which should be the top supervisor of the application's supervision tree if the application follows the OTP design principles around supervision).

start_type defines how the application is started:

  • :normal - used if the startup is a normal startup or if the application is distributed and is started on the current node because of a failover from another node and the application specification key :start_phases is :undefined.
  • {:takeover, node} - used if the application is distributed and is started on the current node because of a failover on the node node.
  • {:failover, node} - used if the application is distributed and is started on the current node because of a failover on node node, and the application specification key :start_phases is not :undefined.

start_args are the arguments passed to the application in the :mod specification key (e.g., mod: {MyApp, [:my_args]}).

This function should either return {:ok, pid} or {:ok, pid, state} if startup is successful. pid should be the PID of the top supervisor. state can be an arbitrary term, and if omitted will default to []; if the application is later stopped, state is passed to the stop/1 callback (see the documentation for the c:stop/1 callback for more information).

use Application provides no default implementation for the start/2 callback.

Callback implementation for Application.start/2.

Link to this function

terminate_instance_process(instance, process_id, payload \\ %{})

See WorkerTracker.WorkerInstance.Server.terminate_instance_process/3.