How long does the client last?

[du201]

I haven't found related information either in the doc or in other issues, so I am posting it here.

I am writing a Golang HTTP server which accesses Elasticsearch. When the server starts, I create the client using the elasticsearch.NewClient. Do I need to manually refresh the client periodically to keep the HTTP connection alive? Or is that already handled by the client, and I can just continue using the same client indefinitely? Thank you so much for your time and help in advance.

[MattDevy]

Hi @du201 , sorry for the long wait!

Thanks for the question.

You generally do not need to periodically “refresh” or recreate the Elasticsearch Go client in a long-running HTTP server. go-elasticsearch is designed to be reused: it sits on top of Go’s net/http transport, which manages connection pooling and keep-alives. If an idle connection is closed by the server / load balancer, the next request will transparently open a new connection.

The recommended pattern is:

• Create one client instance on server startup and reuse it across requests (it’s intended to be used concurrently).
• Use per-request contexts/timeouts when calling Elasticsearch.
• On server shutdown, call Close(ctx) to close the underlying transport/pool.

I hope this clears up your question! If not, feel free to comment here if you need any further help

[github-actions]

This issue is stale because it has been open 5 days with no activity. Remove stale label or comment or this will be closed in 2 days.

[github-actions]

This issue was closed because it has been stale for 2 days with no activity.