You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like both GelfUDPSender and GelfTCPSender caches the hostnames of the graylog server for the duration of the process, which makes it unnecessary hard to fail-over / replace the server without restarting all the clients so they can resolve the hostname again.
Please correct me if I've read the source code wrong.
Is there any reason why this cannot be done upon every reconnect on the GelfTCPSender and periodically (i.e default every 10 min, configurable via a new setting) for the GelfUDPSender?
The text was updated successfully, but these errors were encountered:
@t0xa "Resolving hostname every send might be very time consuming." why? most of the time is going to be fetched from cache (depends on the ttl value) and if you don't set the networkaddress.cache.ttl in the java.security file is always going to be fetched from cache (default setting in the JVM)
It looks like both
GelfUDPSender
andGelfTCPSender
caches the hostnames of the graylog server for the duration of the process, which makes it unnecessary hard to fail-over / replace the server without restarting all the clients so they can resolve the hostname again.Please correct me if I've read the source code wrong.
Is there any reason why this cannot be done upon every reconnect on the
GelfTCPSender
and periodically (i.e default every 10 min, configurable via a new setting) for theGelfUDPSender
?The text was updated successfully, but these errors were encountered: