Annotation Interface EnableClusterAware


@Target(TYPE) @Retention(RUNTIME) @Inherited @Documented @Import(ClusterAwareConfiguration.class) public @interface EnableClusterAware
The EnableClusterAware annotation helps Spring Boot applications using Apache Geode decide whether it needs to operate in local-only mode or in a client/server topology.
Since:
1.2.0
See Also:
  • Optional Element Summary

    Optional Elements
    Modifier and Type
    Optional Element
    Description
    boolean
    Determines whether the matching algorithm is strict.
  • Element Details

    • strictMatch

      boolean strictMatch
      Determines whether the matching algorithm is strict. This means that at least 1 connection to a cluster of servers (1 or more) must be established before the cluster aware logic considers that a cluster actually exists. Previously, in cloud-managed environments (e.g. VMware Tanzu Application Service (TAS) for VMs, formerly known as Pivotal Platform or Pivotal CloudFoundry (PCF), or Kubernetes, known as VMware Tanzu Application Platform for K8S) it was assumed that a cluster would be provisioned and available, and that the Spring Boot, Apache Geode ClientCache application would connect to the cluster on deployment (push). However, is entirely possible that users may push Spring Boot, Apache Geode ClientCache applications to a cloud-managed environment where no cluster was provisioned and is available, and users simply want their apps to run in local-only mode. The strict match configuration setting absolutely requires at least 1 connection must be established. Use of this configuration setting also promotes a fail-fast protocol, or at least early detection (when log levels are adjusted accordingly) that a cluster is not available. Use spring.boot.data.gemfire.cluster.condition.match.strict in Spring Boot application.properties. Defaults to false.
      Returns:
      a boolean value indicating whether strict matching mode is enabled.
      Default:
      false