Skip to content

Commit 2407a37

Browse files
authored
Update node_pool.md with Elasticsearch PHP client note
Clarified that custom NodePool is not necessary for connecting to Elastic Cloud Hosted or Serverless.
1 parent 83c728c commit 2407a37

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/reference/node_pool.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,10 @@ $transport = TransportBuilder::create()
4747

4848
### Using a custom NodePool, Selector and Resurrect [_using_a_custom_nodepool_selector_and_resurrect]
4949

50+
::::{note}
51+
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.
52+
::::
53+
5054
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)
5155

5256
You can also customize the Selector and the Resurrect components of the node pool. You can use the following interfaces for the implementation:

0 commit comments

Comments
 (0)