Package

com.twitter.finagle

loadbalancer

Permalink

package loadbalancer

Visibility
  1. Public
  2. All

Type Members

  1. class HeapBalancer[Req, Rep] extends ServiceFactory[Req, Rep] with OnReady

    Permalink

    An efficient load balancer that operates on Activity[Set[ServiceFactory[Req, Rep]]].

  2. abstract class LoadBalancerFactory extends AnyRef

    Permalink

    A thin interface around a Balancer's constructor that allows Finagle to pass in context from the stack to the balancers at construction time.

    A thin interface around a Balancer's constructor that allows Finagle to pass in context from the stack to the balancers at construction time.

    See also

    Balancers for a collection of available balancers.

Value Members

  1. object Aperture

    Permalink
  2. object Balancers

    Permalink

    Constructor methods for various load balancers.

    Constructor methods for various load balancers. The methods take balancer specific parameters and return a LoadBalancerFactory that allows you to easily inject a balancer into the Finagle stack via client configuration.

  3. object ConcurrentLoadBalancerFactory

    Permalink

    A load balancer that balances among multiple connections, useful for managing concurrency in pipelining protocols.

    A load balancer that balances among multiple connections, useful for managing concurrency in pipelining protocols.

    Each endpoint can open multiple connections. For N endpoints, each opens M connections, load balancer balances among N*M options. Thus, it increases concurrency of each endpoint.

  4. object DefaultBalancerFactory extends LoadBalancerFactory

    Permalink
  5. object HeapBalancer

    Permalink
  6. object LoadBalancerFactory

    Permalink
  7. package exp

    Permalink
  8. object perHostStats extends GlobalFlag[Boolean]

    Permalink

Deprecated Value Members

  1. object defaultBalancer extends GlobalFlag[String]

    Permalink

    We expose the ability to configure balancers per-process via flags.

    We expose the ability to configure balancers per-process via flags. However, this is generally not a good idea as Finagle processes usually contain many clients. This will likely go away in the future or be no-op and, therfore, should not be depended on. Instead, configure your balancers via the configured method on clients:

    {{ val balancer = Balancers.aperture(...) Protocol.configured(LoadBalancerFactory.Param(balancer)) }}

    Annotations
    @deprecated
    Deprecated

    (Since version 2015-06-15) Use com.twitter.finagle.loadbalancer.Balancers per-client.

Ungrouped