Skip to content

ES|QL: implement watchdog timeout for GROK - #152851

Merged
luigidellaquila merged 4 commits into
elastic:mainfrom
luigidellaquila:esql/grok_watchdog_take_2
Jul 3, 2026
Merged

luigidellaquila merged 4 commits into
elastic:mainfrom
luigidellaquila:esql/grok_watchdog_take_2

Conversation

@luigidellaquila

Copy link
Copy Markdown
Member

After revert of #152170, and following off-line discussions, let's re-introduce the watchdog without changes to the transport protocol. This will make backports easier

@luigidellaquila luigidellaquila added >enhancement auto-backport Automatically create backport pull requests when merged :Analytics/ES|QL AKA ESQL branch:8.19 branch:9.3 branch:9.4 labels Jul 3, 2026
@elasticsearchmachine elasticsearchmachine added v9.5.0 Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v9.4.4 v9.3.8 v8.19.19 labels Jul 3, 2026
@elasticsearchmachine

Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine

Copy link
Copy Markdown
Collaborator

Hi @luigidellaquila, I've created a changelog YAML for you.

@github-actions

github-actions Bot commented Jul 3, 2026 •

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

⏳ Building and deploying preview... View progress

This comment will be updated with preview links when the build is complete.

@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

@luigidellaquila
luigidellaquila enabled auto-merge (squash) July 3, 2026 09:44
@luigidellaquila
luigidellaquila merged commit 46b1002 into elastic:main Jul 3, 2026
42 checks passed
@elasticsearchmachine

Copy link
Copy Markdown
Collaborator

💔 Backport failed

Status Branch Result
❌ 9.4 Commit could not be cherrypicked due to conflicts
❌ 9.3 Commit could not be cherrypicked due to conflicts
❌ 8.19 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 152851

elasticsearchmachine pushed a commit that referenced this pull request Jul 6, 2026
* ES|QL: implement watchdog timeout for GROK (#152851) (#152944)

* [CI] Auto commit changes from spotless

---------

Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
elasticsearchmachine pushed a commit that referenced this pull request Jul 6, 2026
…) (#152960)

* ES|QL: implement watchdog timeout for GROK (#152851) (#152944)

* [CI] Auto commit changes from spotless

---------

Co-authored-by: elasticsearchmachine <infra-root+elasticsearchmachine@elastic.co>
@luigidellaquila

Copy link
Copy Markdown
Member Author

Backports:
#152944
#152949
#152960

burqen pushed a commit to burqen/elasticsearch that referenced this pull request Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-backport Automatically create backport pull requests when merged >enhancement Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.19.19 v9.3.8 v9.4.4 v9.5.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants