Skip to content

[fix](doc) clarify computation BE role behavior across storage modes#3758

Merged
morningman merged 2 commits into
apache:masterfrom
morningman:mix_node
May 25, 2026
Merged

[fix](doc) clarify computation BE role behavior across storage modes#3758
morningman merged 2 commits into
apache:masterfrom
morningman:mix_node

Conversation

@morningman
Copy link
Copy Markdown
Contributor

Summary

  • A computation-type BE node only serves data lake (external table) queries — it never serves internal table queries. If every BE in the cluster is computation, internal-table queries fail with has no queryable replicas.
  • The existing doc claimed compute nodes only apply to the storage-compute integrated mode and were "no longer needed" in the storage-compute separation mode. That is wrong: they work in both modes, with the same external-only restriction. The wording is corrected to describe the two modes side by side and call out the workload-isolation use case.
  • Added a :::caution admonition warning about:
    • the has no queryable replicas failure when all BEs are computation
    • SHOW BACKENDS always showing NodeRole = mix in storage-compute separation mode regardless of be_node_role (a real-world user got confused by this and changed their config the wrong way)
  • Added two FAQ entries covering the same two pitfalls.

Updates the four file copies that contain this section: zh-CN current + zh-CN version-4.x, English current (docs/) + English version-4.x (versioned_docs/).

Test plan

  • Spot-check the rendered Chinese page in the local Docusaurus build
  • Spot-check the rendered English page in the local Docusaurus build
  • Verify the :::caution admonition renders correctly in both languages

A computation-type BE node only serves data lake (external table)
queries; querying internal tables on a cluster where all BEs are
computation fails with "has no queryable replicas". The previous
doc claimed the role was for storage-compute integrated mode only,
which is wrong — it works in both modes, but with the same
external-only restriction. Also document that SHOW BACKENDS always
shows NodeRole=mix in storage-compute separation mode, regardless
of the be_node_role config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Under WSL2 the per-distribution loopback prevents FE and BE from
reaching each other via 127.0.0.1, so the default
priority_networks=127.0.0.1/32 leaves BE unable to join the cluster.
Add a FAQ entry in the quick-start guide (zh-CN / en, current / 4.x)
explaining the cause and pointing users to set priority_networks to
their WSL interface subnet.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@morningman morningman merged commit b00e750 into apache:master May 25, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant