deardeng opened a new pull request, #70392: URL: https://github.com/apache/doris/pull/70392
FE uses the Doris JE fork for replicated metadata storage. The JE version is managed centrally in the FE parent POM. Related PR: apache/doris-thirdparty#432 (companion JE fix) https://github.com/apache/doris-thirdparty/pull/432 Problem Summary: Membership discovery can keep retrying a stale or unresolved helper address after DNS recovers. Use the JE artifact that rebuilds helper addresses on each discovery retry. ### Details - **Versions:** 18.3.18-doris-SNAPSHOT to 18.3.19-doris-SNAPSHOT. - **Upstream changes:** Refresh the helper set used by master and restore-supplier queries on each retry. - **Compatibility:** No public API or storage-format changes in the companion JE patch. - **Rollback:** Restore je.version to 18.3.18-doris-SNAPSHOT. - **Behavior change:** A discovery retry can use updated hostname resolution without restarting FE. ### Testing JE Maven install passed. FE parent and fe-core effective POMs resolve JE 18.3.19-doris-SNAPSHOT; offline dependency:get passed. The installed JAR matches the built JAR, and all class files match the fixed JAR tested with stale-address and unresolved-hostname fault scenarios. FE parent validate with Maven 3.9.12 passed with zero Checkstyle violations. Full FE build and Kubernetes integration tests were not run. ### Notes for Reviewers The new artifact is installed locally only; publish the companion JE artifact to the shared Maven repository before merging this dependency update. ### Release note FE membership discovery can recover after helper hostname resolution changes without a process restart. ### Check List (For Author) - Behavior changed: Yes (see Details) - Does this need documentation: No - Pre-submission status: Not ready: shared artifact publication and FE integration verification are pending. ### AI Disclosure - Tool: OpenAI Codex - Generated: Dependency version update and this description. - Human review: Pending. ### Background <!-- How the feature or module this PR touches works today, in two to four plain sentences, for a reviewer who doesn't know it. Link the user doc if there is one. Leave the problem and the fix to Problem Summary. --> ### What problem does this PR solve? <!-- Issue Number: "close #N" if this PR resolves the issue, "#N" if it only relates to it, "None" if there is none. A Feature needs an issue. --> <!-- Related PR: "#N (relation)" for each PR a reviewer should know about, such as "#123 (introduced the bug)", separated by commas. Write "None" if no related PR is known. --> <!-- PR Type: Bugfix, Performance, Feature, Enhancement, Refactor, Test, Build/CI/Chore, Revert, Release/Dependency, or Other. --> Issue Number: Related PR: PR Type: Problem Summary: <!-- Two to five sentences: the problem or need and who is affected; the approach in one sentence; when the diff is larger than that suggests, what else it had to handle, or that most of it is tests; and what existing users see after an upgrade. --> ### Details <!-- For a diff of more than about 300 changed lines, start with "- **Change map:**": how many lines are production code, tests, generated files, and docs, then the code in parts, each with the problem it handles and its size. Then answer each field of your PR type on its own line, as "- **Field:** answer", in this order: Bugfix: Frequency, Root cause, Why existing tests missed it, Fix, Other paths and branches Performance: Why it was slow, Optimization, Results, Applicability and cost Feature: Scope, Design, Usage, Default behavior, Compatibility Enhancement: Before and after, Configs and defaults, Impact on existing users Refactor: Moves vs. logic changes, Behavior change, Compatibility, Performance impact, Rollback Test, adding tests: Scenarios, What existing tests miss, Fails when broken Test, fixing a test: Failure, Cause, Stability evidence Build/CI/Chore: Affected, Developer and release impact, License and third-party, Rollback Revert: Why not fix forward, Original author notified, Follow-up Release/Dependency: Versions, Upstream changes, Compatibility, Rollback Other: Why Other "None" is a valid answer when it is true. Don't restate the diff. --> ### Testing <!-- The tests, suites, or commands that ran, what each shows, and where it ran (locally or in CI). For a fix, the test that fails before it and passes after. --> ### Notes for Reviewers <!-- Optional; delete this section if there is nothing to say. Why each non-obvious edit was made, what you are unsure about, and where to start reading if Details has no Change map. --> ### Release note <!-- One paragraph on what users will notice, or None. --> ### Check List (For Author) <!-- Behavior changed: "No", or "Yes (see Details)" with a Behavior change field in Details. --> <!-- Does this need documentation: "No", or "Yes" with the apache/doris-website PR or the plan. --> <!-- Pre-submission status: "Ready"; "Partially verified: " and what is not verified; or "Not ready: " and why, for a Draft PR. --> - Behavior changed: - Does this need documentation: - Pre-submission status: ### AI Disclosure <!-- Tool: the agent and model, or None. Generated: the parts it wrote (code, tests, this description), or None. Human review: what you reviewed of the generated parts, or "Not applicable" without AI tools. You may add "- Prompts:" to summarize how you directed the agent. --> - Tool: - Generated: - Human review: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
