2.5. Advanced Configuration


Features such as server discovery, load balancing, failover, retry, and retry delay, may be customized if the default policy is not appropriate. Refer to the org.teiid.net.socket.ServerDiscovery interface and default implementation org.teiid.net.socket.UrlServerDiscovery for more information on customization.
The UrlServerDiscovery implementation provides the following features:
  • discovery of servers from URL hosts (including the data source server and alternative servers)
  • random selection for load balancing and failover
  • one connection attempt per host
  • no biasing
  • black listing
Typically you'll want to extend the UrlServerDiscovery so that it can be used as the fall-back strategy and to only implement the necessary changed methods. It is important to consider that one ServerDiscovery instance will be created for each connection. Any sharing of information between instances should be done through static state or some other shared lookup.
Your customized server discovery class must be referenced by the discoveryStrategy connection/DataSource property using its full class name.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat