JDBC_PING as default discovery protocol

[pruivo]

Description

The default discovery protocol provided by Infinispan uses IP multicast (MPING) to find its peers in the network. Although it is perfectly fine for an environment with IP multicast available, JDBC_PING seems a better fit as a default discovery protocol for Keycloak.

The JDBC_PING protocol uses a database to keep track of the peer's IP addresses (and ports) and, we can use the Keycloak database as a registry.

The following work is required:

• Create a custom stack, replacing MPING with JDBC_PING
• Infinispan 15.0.3.Final allows injecting a data source into JDBC_PING for Infinispan Server (see https://issues.redhat.com/browse/ISPN-15961). The same code can be used by Keycloak to inject the Quarkus data source into JGroups.
• (UX improvement) Somehow detect the database dialect to configure the JDBC_PING queries (select, delete, insert). The goal is to achieve zero-config for users.
• Set values for remaining options based on user feedback and/or issues found.

JDBC_PING documentation is available here: http://jgroups.org/manual5/index.html#_jdbc_ping

Discussion

#29205

Issues

No response

Motivation

To simplify Keycloak usage and configuration.