## Uses of Interface
org.apache.storm.messaging.IContext

- Packages that use IContext
  Package | Description
  --- | ---
  org.apache.storm.daemon.supervisor |
  org.apache.storm.daemon.worker |
  org.apache.storm.messaging |
  org.apache.storm.messaging.netty |

- - ### Uses of IContext in org.apache.storm.daemon.supervisor

    Methods in org.apache.storm.daemon.supervisor with parameters of type IContext
    Modifier and Type | Method and Description
    --- | ---
    `static ContainerLauncher` | ContainerLauncher.`make(Map<String,Object> conf, String supervisorId, int supervisorPort, IContext sharedContext, StormMetricsRegistry metricsRegistry, ContainerMemoryTracker containerMemoryTracker, Supervisor.Iface localSupervisor)` Factory to create the right container launcher for the config and the environment.

    Constructors in org.apache.storm.daemon.supervisor with parameters of type IContext
    Constructor and Description
    `LocalContainer(Map<String,Object> conf, String supervisorId, int supervisorPort, int port, LocalAssignment assignment, IContext sharedContext, StormMetricsRegistry metricsRegistry, ContainerMemoryTracker containerMemoryTracker, Supervisor.Iface localSupervisor)`
    `LocalContainerLauncher(Map<String,Object> conf, String supervisorId, int supervisorPort, IContext sharedContext, StormMetricsRegistry metricsRegistry, ContainerMemoryTracker containerMemoryTracker, Supervisor.Iface localSupervisor)`
    `Supervisor(Map<String,Object> conf, IContext sharedContext, ISupervisor iSupervisor, StormMetricsRegistry metricsRegistry)` Constructor for supervisor daemon.

  - ### Uses of IContext in org.apache.storm.daemon.worker

    Constructors in org.apache.storm.daemon.worker with parameters of type IContext
    Constructor and Description
    `Worker(Map<String,Object> conf, IContext context, String topologyId, String assignmentId, int supervisorPort, int port, String workerId)`
    `Worker(Map<String,Object> conf, IContext context, String topologyId, String assignmentId, int supervisorPort, int port, String workerId, Supplier<SupervisorIfaceFactory> supervisorIfaceSupplier)` TODO: should worker even take the topologyId as input? this should be deducible from cluster state (by searching through assignments) what about if there’s inconsistency in assignments? -> but nimbus should guarantee this consistency.
    `WorkerState(Map<String,Object> conf, IContext mqContext, String topologyId, String assignmentId, Supplier<SupervisorIfaceFactory> supervisorIfaceSupplier, int port, String workerId, Map<String,Object> topologyConf, IStateStorage stateStorage, IStormClusterState stormClusterState, Collection<IAutoCredentials> autoCredentials, StormMetricRegistry metricRegistry, Credentials initialCredentials)`

  - ### Uses of IContext in org.apache.storm.messaging

    Methods in org.apache.storm.messaging that return IContext
    Modifier and Type | Method and Description
    --- | ---
    `static IContext` | TransportFactory.`makeContext(Map<String,Object> topoConf, StormMetricRegistry metricRegistry)`

  - ### Uses of IContext in org.apache.storm.messaging.netty

    Classes in org.apache.storm.messaging.netty that implement IContext
    Modifier and Type | Class and Description
    --- | ---
    `class` | `Context`

Copyright © 2021 The Apache Software Foundation. All rights reserved.