fix: stop query planning compute jobs when parent task cancelled

[rohan-b99]

---

Checklist

Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.

• PR description explains the motivation for the change and relevant context for reviewing
• PR description links appropriate GitHub/Jira tickets (creating when necessary)
• Changeset is included for user-facing changes
• Changes are compatible¹
• Documentation² completed
• Performance impact assessed and acceptable
• Metrics and logs are added³ and documented
• Tests added and passing⁴
  • Unit tests
  • Integration tests
  • Manual tests, as necessary

To test locally, run a query that currently causes OOM with this in the config:

supergraph:
  listen: 0.0.0.0:4000
  introspection: true
  early_cancel: true
  query_planning:
    experimental_cooperative_cancellation:
      mode: enforce
      timeout: 1s

Check the memory usage of the router process, it should not continue to increase after the request/query planning is cancelled

Exceptions

Note any exceptions here

Notes

Footnotes

1. It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩

2. Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩

3. A lot of (if not most) features benefit from built-in observability and debug-level logs. Please read this guidance on metrics best-practices. ↩

4. Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩

[apollo-librarian]

✅ Docs preview has no changes

The preview was not built because there were no changes.

Build ID: ad1d178a8faaf73a42992c1f
Build Logs: View logs

[aaronArinder]

lgtm! I haven't tested it locally, but if you'd like me to, let me know; looks pretty safe overall, so didn't feel the need to hunt down an oom query for validation

[rohan-b99]

lgtm! I haven't tested it locally, but if you'd like me to, let me know; looks pretty safe overall, so didn't feel the need to hunt down an oom query for validation

I think it should be pretty safe as it requires experimental config, I've been testing a bunch more locally with the memory limit branch as well so confident it works