Skip to content

docs(release-notes): v3.12.2 and v3.11.8 corrections - #7961

Merged
jstirnaman merged 2 commits into
pbarnett/release-notes-3.12.2-3.11.8from
pb/release-notes-3.12.2-addendum
Oct 29, 2026
Merged

jstirnaman merged 2 commits into
pbarnett/release-notes-3.12.2-3.11.8from
pb/release-notes-3.12.2-addendum

Conversation

@philjb

@philjb philjb commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Addendum to #7957 for you to evaluate; merge into your branch or cherry-pick what you want.

  • v3.12.2: drop "Shutdown hung while a processing engine plugin was stuck". That is influxdata/influxdb_pro#6827 (1d56d74a85). The v3.12.2 tag is f1972a0ff7: 3.12 at 3aeb9c30 plus 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 of 1d56d74a85.
  • v3.12.2 and v3.11.8: the 429 bullet adds "Some queries still return 500..." Smoke tests of both Core builds with a small --exec-mem-pool-size: a generate_series GROUP 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 inside External. 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.

@github-actions

Copy link
Copy Markdown
Contributor

Vale Style Check Results

Metric Count
Errors 0
Warnings 0

✅ Check passed

@github-actions

Copy link
Copy Markdown
Contributor

Release version check

Product Release notes data/products.yml Status
influxdb3_core (latest_patch) 3.12.2 3.12.2 ✅ in sync
influxdb3_enterprise (latest_patch) 3.12.2 3.12.2 ✅ in sync

💡 Badge new features with the version

Documenting a new feature? Add a version badge in the page frontmatter — the
same mechanism used elsewhere in the docs:

  • metadata: [InfluxDB 3 Core v3.11+] — badge list under the page title
  • updated_in: v3.11 — an "Updated in v3.11" badge
  • introduced: v3.11 — a "‹Product› v3.11+" badge
  • menu.params.state: new — a "NEW" pill on the sidebar nav item

For inline version text, use {{< latest-patch >}} / {{< current-version >}},
which read the value from data/products.yml so it stays correct automatically.

@github-actions

github-actions Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

🔗 Link Check Results — Link Check Bot

✅ All links are valid

Metric Value
Files Checked 2
Total Links 1077
Errors 0
Warnings 2
Success Rate 99.4429%
⚠️ 2 warning(s) (do not fail CI)
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

- **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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this fix wasn't in this point release

@philjb
philjb marked this pull request as ready for review October 29, 2026 20:54
@philjb
philjb requested a review from a team as a code owner October 29, 2026 20:54
@philjb
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 added a commit that referenced this pull request Oct 29, 2026
Revert the file changes from 5bad339.
The reconciled corrections are now on Phil's PR #7961 so they can be
reviewed and merged as his contribution.

Verification:
Restores the exact file content from 43f045f.

@jstirnaman jstirnaman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks @philjb! I'll merge the unique bits into 7957; there's some overlap with my earlier PR.

@github-actions github-actions Bot added product:shared Shared content across products product:v3-monolith InfluxDB 3 Core and Enterprise (single-node / clusterable) labels Oct 29, 2026
…ill return 500

v3.12.2 is tagged at 3aeb9c30 plus #6990, so #6827 (1d56d74a85) is not in it. Smoke tests of both Core builds showed a GROUP BY on a table that exhausts memory during deduplication still returns 500.
@jstirnaman
jstirnaman force-pushed the pb/release-notes-3.12.2-addendum branch from cb8e192 to ad9fb1b Compare October 29, 2026 22:03
@jstirnaman
jstirnaman merged commit 280a3fb into pbarnett/release-notes-3.12.2-3.11.8 Oct 29, 2026
24 checks passed
@jstirnaman
jstirnaman deleted the pb/release-notes-3.12.2-addendum branch October 29, 2026 22:13
jstirnaman added a commit that referenced this pull request Oct 29, 2026
Revert the file changes from 5bad339.
The reconciled corrections are now on Phil's PR #7961 so they can be
reviewed and merged as his contribution.

Verification:
Restores the exact file content from 43f045f.
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:shared Shared content across products product:v3-monolith InfluxDB 3 Core and Enterprise (single-node / clusterable)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants