Use proxy instead of list of container endpoints in FeedClientBuilder

[mohsin36]

We are currently using FeedClientBuilder.setEndpointUrl(List endpoints)
https://javadoc.io/doc/com.yahoo.vespa/vespa-feed-client-api/8.26.15/ai/vespa/feed/client/FeedClientBuilder.html#setEndpointUris(java.util.List)

However this causes connection issue during container host reboots or downtime even on a single node.

Can we use a reverse proxy instead of explicit list of containers? Reverse proxy would take care of forwarding requests only to healthy container nodes.

[bjorncs]

Hi @mohsin36

Can we use a reverse proxy instead of explicit list of containers? Reverse proxy would take care of forwarding requests only to healthy container nodes.

Yes, that is common practice.

However this causes connection issue during container host reboots or downtime even on a single node.

Connection failures should be handled seamlessly. What can of failures do you observe? FYI the javadoc refers to 8.26.15, which is quite an old version. If that's the version used, we highly recommend upgrading as more recent versions contains a few connection related fixes.