Repository navigation
Supported internal cluster-token rotation for an existing 4.1.3 single-FE/single-BE cluster #68705
Unanswered
sga-jerrylin
asked this question in
A - General / Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Version: Apache Doris 4.1.3 (4.1.3-rc02); planned target 4.1.4.1.
Topology: one FE and one BE, coupled deployment.
Is there an officially supported administrative procedure for rotating the persisted internal cluster authentication token on an existing cluster? Please point to version-matched documentation and specify the maintenance sequence, FE/BE consistency requirements, old-token invalidation verification, and failure rollback.
Does setting auth_token apply only to initial provisioning rather than rotate an existing stored token? We need a supported approach that does not rely on manually editing VERSION, deleting metadata, or disabling authentication checks.
All reactions