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

Clustering subsystems integration with WildFly Discovery SPI (tracker Jira)

    XMLWordPrintable

Details

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

    Description

      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

      Attachments

        Issue Links

          incorporates

          Feature Request - Feature requests from customers and/or users WFLY-12220 Implement JGroups discovery protocol based on WildFly Discovery SPI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Feature Request - Feature requests from customers and/or users WFLY-12221 Integrate mod_cluster subsystem with WildFly Discovery SPI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Feature Request - Feature requests from customers and/or users WFLY-12223 Configuring remote-cache-container datagrid nodes based on WildFly Discovery SPI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4535 WildFly discovery subsystem registers capabilities using an ambiguous contract

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is documented by

          Sub-task - The sub-task of the issue WFLY-12225 Document missing discovery capabilities

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated: