From 2407a37dbbcbd33bba4325fabb8b8f962a7cb6c7 Mon Sep 17 00:00:00 2001 From: Pius Fung Date: Wed, 17 Sep 2025 22:14:50 -0700 Subject: [PATCH] Update node_pool.md with Elasticsearch PHP client note Clarified that custom NodePool is not necessary for connecting to Elastic Cloud Hosted or Serverless. --- docs/reference/node_pool.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/reference/node_pool.md b/docs/reference/node_pool.md index 7c53b6a1a..b1839871c 100644 --- a/docs/reference/node_pool.md +++ b/docs/reference/node_pool.md @@ -47,6 +47,10 @@ $transport = TransportBuilder::create() ### Using a custom NodePool, Selector and Resurrect [_using_a_custom_nodepool_selector_and_resurrect] +::::{note} +The Elasticsearch PHP client can be used to connect to on-premises, Elastic Cloud, or Serverless deployments. When using Elastic Cloud or Serverless, there is no need to configure a custom NodePool — the default one is sufficient. +:::: + If you want you can implement your custom node pool algorithm. We provided a [NodePoolInterface](https://github.com/elastic/elastic-transport-php/blob/master/src/NodePool/NodePoolInterface.php) You can also customize the Selector and the Resurrect components of the node pool. You can use the following interfaces for the implementation: