All Downloads are FREE. Search and download functionalities are using the official Maven repository.

.hazelcast.4.0.1.source-code.hazelcast-client-failover-full-example.yaml Maven / Gradle / Ivy

There is a newer version: 5.5.0
Show newest version
# Copyright (c) 2008-2020, Hazelcast, Inc. All Rights Reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# This is a full example hazelcast-client-failover.yaml that includes all
# the configuration nodes of a Hazelcast client Blue/Green Deployment and
# Disaster Recovery configuration.
#
# To use this, rename it to hazelcast-client-failover.yaml and place it in
# the directory where you start your Hazelcast client.
#
# To learn how to configure Hazelcast clients for Blue/Green Deployment and
# Disaster Recovery, please see the Reference Manual at
# https://hazelcast.org/documentation/

hazelcast-client-failover:
  # 
  # The Hazelcast client can configurations that the client is using to connect to a Hazelcast cluster in the case
  # of a disconnect is listed under the  element. You can list client configurations as many as you want.
  # Each client configuration can be listed via  element nested into the  element.
  #
  clients:
    - your-first-hazelcast-client-configuration.yaml
    - your-second-hazelcast-client-configuration.yaml
  #
  # Each time the client is disconnected from a cluster and it cannot connect back to the same one, the configured
  # client configuration defined under the "clients" element is iterated over. Count of these iterations before the
  # client decides to shut down is provided using the "try-count" configuration element. See the following
  # configuration related sections.
  # 
  try-count: 4




© 2015 - 2024 Weber Informatics LLC | Privacy Policy