Skip to content

Conversation

@mnocon
Copy link
Contributor

@mnocon mnocon commented Jan 13, 2026

@mnocon mnocon marked this pull request as ready for review January 14, 2026 08:16
@mnocon mnocon requested review from barw4 and micszo January 14, 2026 08:23
Copy link
Contributor

@micszo micszo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for covering the alternative!

@mnocon mnocon requested a review from a team January 15, 2026 09:06
@ibexa-workflow-automation-1 ibexa-workflow-automation-1 bot requested review from adriendupuis, dabrt and julitafalcondusza and removed request for a team January 15, 2026 09:06
@mnocon mnocon added the Wait with merge PRs that shouldn't be merged instantly label Jan 15, 2026
```

For more information and a list of available choices, see [Connection pool](https://www.elastic.co/guide/en/elasticsearch/client/php-api/7.x/connection_pool.html).
For more information and a list of available choices, see [Node pool](https://www.elastic.co/docs/reference/elasticsearch/clients/php/node_pool).
Copy link
Contributor

@barw4 barw4 Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we put the link to 7x and 8x clients here?

Copy link
Contributor

@julitafalcondusza julitafalcondusza left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please check my comments.

Co-authored-by: julitafalcondusza <117284672+julitafalcondusza@users.noreply.github.com>
The node pool manages the list of active nodes, which can change over time due to connectivity issues, host malfunction, or when you add new nodes to the cluster to increase performance.

You can change the default setting with the following key:
By default, Elasticsearch 8 uses `SimpleNodePool` with `RoundRobin` selector and `NoResurrect` strategy.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd put it differently, because users can opt for either of the supported versions. Something along the lines of:
"In installations running Elasticsearch 8.18+, the default configuration uses SimpleNodePool with a RoundRobin selector and a NoResurrect strategy."

At the same time, I wouldn't remove information that discusses 7.16.2+ configuration, but have both.

Unless of course we want to adamantly say "you must use elastic 8" or at least "Ibexa strongly recommends that you use elastic 8" in all those places where two versions are mentioned, followed by "for 7.16.2+ configuration, refer to our documentation for the v.4.6.x release" (in requirements and a note in install elasticsearch)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Even if you decide to use Elasticsearch 7 (which we won't recommend anymore), you cannot use the existing configuration - please see the update instructions, the old configuration is deprecated and does nothing.

Regardless of Elasticsearch version, you have to use the "node pool" settings - even when staying on Elasticsearch 7

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's all clear now

@mnocon mnocon changed the base branch from 5.0 to release-5.0.5 January 15, 2026 10:56
…ch.md

Co-authored-by: Tomasz Dąbrowski <64841871+dabrt@users.noreply.github.com>
@mnocon mnocon requested a review from dabrt January 15, 2026 11:10
@mnocon mnocon merged commit fcddb06 into release-5.0.5 Jan 15, 2026
7 checks passed
@mnocon mnocon deleted the elasticsearch-8 branch January 15, 2026 11:23
@mnocon mnocon mentioned this pull request Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs DOC review Wait with merge PRs that shouldn't be merged instantly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants