Repository navigation
docs(release-notes): v3.12.2 and v3.11.8 corrections - #7961
Merged
jstirnaman merged 2 commits intoOct 29, 2026
Merged
jstirnaman merged 2 commits into
jstirnaman merged 2 commits into
Conversation
Contributor
Vale Style Check Results
✅ Check passed |
Contributor
Release version check
💡 Badge new features with the versionDocumenting a new feature? Add a version badge in the page frontmatter — the
For inline version text, use |
Contributor
🔗 Link Check Results — Link Check Bot✅ All links are valid
|
| Source File | URL | Issue |
|---|---|---|
content/influxdb3/core/release-notes/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
content/influxdb3/enterprise/release-notes/_index.md |
https://support.influxdata.com/ | Network error: SSL certificate not trusted. Use --insecure if site is trusted (e… |
Full details: workflow run summary and artifact. Last updated: 2026-10-29 22:05:09 UTC
philjb
commented
Oct 29, 2026
| - **Queries that exceed memory limits returned `500`**: The HTTP query endpoints now return `429 Too Many Requests` when a query exhausts the DataFusion memory pool. Previously, they returned `500`. For CSV, JSON, and JSON Lines output, this applies when the query fails before it returns any rows. Some queries still return `500`, such as a query on a table that runs out of memory while deduplicating data. Enterprise already returned `429`. | ||
| - **Catalog deadlock when checking a deleted table**: Checking whether a table is deleted now takes the catalog lock once. Previously, a catalog change that arrived between its two reads could deadlock the catalog. | ||
| - **WAL plugins received values under the wrong column names**: Rows passed to a WAL trigger's plugin now use the column names of their own record batch. Previously, when a flush held batches with the same columns in a different order, later batches used the first batch's column names. | ||
| - **Shutdown hung while a processing engine plugin was stuck**: The server now exits within about 2 seconds after shutdown completes, even while a plugin is stuck in a blocking call. Previously, it waited for the plugin's thread forever. Enterprise already exited this way. |
Contributor
Author
There was a problem hiding this comment.
this fix wasn't in this point release
philjb
marked this pull request as ready for review
October 29, 2026 20:54
philjb
requested review from
jstirnaman and
peterbarnett03
and removed request for
a team
October 29, 2026 20:54
jstirnaman
added a commit
that referenced
this pull request
Oct 29, 2026
What changed: Retain Phil's Core memory-error caveats and verified v3.12.2 source. Preserve the newer streaming-response distinctions and precise Enterprise wording from the target branch. Why: Keep the remaining corrections in Phil's contribution, PR #7961. Verification: Compared both PR heads and preserved the target branch content apart from the two Core caveats and the verified release-source comment.
jstirnaman
reviewed
Oct 29, 2026
jstirnaman
left a comment
Contributor
There was a problem hiding this comment.
Thanks @philjb! I'll merge the unique bits into 7957; there's some overlap with my earlier PR.
jstirnaman
force-pushed
the
pb/release-notes-3.12.2-addendum
branch
from
October 29, 2026 22:03
cb8e192 to
ad9fb1b
Compare
jstirnaman
merged commit Oct 29, 2026
280a3fb
into
pbarnett/release-notes-3.12.2-3.11.8
24 checks passed
dhoard
pushed a commit
to dhoard/docs-v2
that referenced
this pull request
Oct 31, 2026
Revert the file changes from 5bad339. The reconciled corrections are now on Phil's PR influxdata#7961 so they can be reviewed and merged as his contribution. Verification: Restores the exact file content from 43f045f.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addendum to #7957 for you to evaluate; merge into your branch or cherry-pick what you want.
1d56d74a85). The v3.12.2 tag isf1972a0ff7: 3.12 at3aeb9c30plus influxdata/influxdb_pro#6990, so Use Cloud Dedicated admin UI to get started #6827 is not in it. It belongs in the next 3.12 patch. The HTML comment now names the tag instead of1d56d74a85.500..." Smoke tests of both Core builds with a small--exec-mem-pool-size: agenerate_seriesGROUP BY returned 429, but a GROUP BY on a table returned 500. The table query's memory error arrives wrapped (External(... 'deduplicate batches' ... ResourcesExhausted)), and the status mapping does not look insideExternal. Details on influxdata/influxdb_pro#6443.Not checked: whether Enterprise 3.12.2 / 3.11.8 return 429 for that table case, so "Enterprise already returned
429" is left as you wrote it.