Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-12222

Clustering subsystems integration with WildFly Discovery SPI (tracker Jira)

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 17.0.0.Final
    • Clustering, mod_cluster
    • None

      Ultimately, we could employ WildFly Discovery SPI to handle services discovery in a generic way. However, since the subsystem currently only supplies one provider based on static discovery, its usefulness is limited. To untangle the chicken-egg problem, we could first integrate the clustering subsystems with the discovery SPI,

      • JGroups discovery
      • remote-cache-container remote servers
      • mod_cluster

      then supply discovery providers,

      • static list (implemented)
      • multicast-based
      • k8s-based (replacing JGroups' OPENSHIFT_PING, DNS_PING, KUBE_PING, etc)
      • cloud providers specific (replacing S3_PING, NATIVE_S3_PING, AZURE_PING, GOOGLE_PING, etc)

      This requires fixes to the discovery subsystem such as

      • ability to register new providers
      • Adding/removing services from static providers should require server reload, or restart of the service providing the DiscoveryProvider
      • TBD

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: