/* * CDDL HEADER START * * The contents of this file are subject to the terms of the * Common Development and Distribution License, Version 1.0 only * (the "License"). You may not use this file except in compliance * with the License. * * You can obtain a copy of the license at * trunk/opends/resource/legal-notices/OpenDS.LICENSE * or https://OpenDS.dev.java.net/OpenDS.LICENSE. * See the License for the specific language governing permissions * and limitations under the License. * * When distributing Covered Code, include this CDDL HEADER in each * file and include the License file at * trunk/opends/resource/legal-notices/OpenDS.LICENSE. If applicable, * add the following below this CDDL HEADER, with the fields enclosed * by brackets "[]" replaced with your own identifying information: * Portions Copyright [yyyy] [name of copyright owner] * * CDDL HEADER END * * * Copyright 2010 Sun Microsystems, Inc. */ package org.opends.sdk; import java.util.Collection; import java.util.concurrent.ScheduledExecutorService; import java.util.concurrent.TimeUnit; /** * A fail-over load balancing algorithm provides fault tolerance across multiple * underlying connection factories. *
* This algorithm is typically used for load-balancing between data * centers, where there is preference to always always forward connection * requests to the closest available data center. This algorithm * contrasts with the {@link RoundRobinLoadBalancingAlgorithm} which is used for * load-balancing within a data center. *
* This algorithm selects connection factories based on the order in which they * were provided during construction. More specifically, an attempt to obtain a * connection factory will always return the first operational connection * factory in the list. Applications should, therefore, organize the connection * factories such that the preferred (usually the closest) connection * factories appear before those which are less preferred. *
* If a problem occurs that temporarily prevents connections from being obtained * for one of the connection factories, then this algorithm automatically * "fails over" to the next operational connection factory in the list. If none * of the connection factories are operational then a * {@code ConnectionException} is returned to the client. *
* The implementation periodically attempts to connect to failed connection
* factories in order to determine if they have become available again.
*
* @see RoundRobinLoadBalancingAlgorithm
* @see Connections#newLoadBalancer(LoadBalancingAlgorithm)
*/
public final class FailoverLoadBalancingAlgorithm extends
AbstractLoadBalancingAlgorithm
{
/**
* Creates a new fail-over load balancing algorithm which will monitor offline
* connection factories every 1 second using the default scheduler.
*
* @param factories
* The ordered collection of connection factories.
*/
public FailoverLoadBalancingAlgorithm(
final Collection