From 8074f65d1ae0486d1417f6a3955ae8ecf4d200b2 Mon Sep 17 00:00:00 2001
From: Toby Sutor <55087308+toby-sutor@users.noreply.github.com>
Date: Tue, 1 Feb 2022 10:52:47 +0100
Subject: [PATCH] Recommend simpleConnectionPool for Cloud

As per https://github.com/elastic/elasticsearch-php/issues/918#issuecomment-511337920 and https://elastic.slack.com/archives/CH37CF39S/p1643707941052409 we recommend using the `simpleConnectionPool` when there is a proxy or load balancer in place. This applies to Elasticsearch Service and ECE (Cloud). Hence the comments need to be updated.
---
 docs/connection-pool.asciidoc | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/connection-pool.asciidoc b/docs/connection-pool.asciidoc
index 962e56738..1dd1ef1eb 100644
--- a/docs/connection-pool.asciidoc
+++ b/docs/connection-pool.asciidoc
@@ -78,8 +78,10 @@ The `SimpleConnectionPool` returns the next node as specified by the selector;
 it does not track node conditions. It returns nodes either they are dead or 
 alive. It is a simple pool of static hosts.
 
-The `SimpleConnectionPool` is not recommended for routine use but it may be a 
-useful debugging tool.
+The `SimpleConnectionPool` is recommended where the Elasticsearch deployment
+is located behnd a (reverse-) proxy or load balancer, where the individual
+Elasticsearch nodes are not visible to the client. This should be used when
+running Elasticsearch deployments on Cloud.
 
 To use the `SimpleConnectionPool`: