Uh oh!
There was an error while loading. Please reload this page.
[improvement](fe) Set default profile level to 2 - #64378
Conversation
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: The default query profile level is 1, which only collects merged profile counters. This change sets the FE session default profile_level to 2 so detailed query profile information is collected by default. ### Release note Set the default query profile level to 2. ### Check List (For Author) - Test: No need to test (only changes the default value of a session variable). - Behavior changed: Yes. The default profile_level is changed from 1 to 2. - Does this need documentation: No
hello-stephen
commented
Jun 10, 2026
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
BiteTheDDDDt
commented
Jun 10, 2026
run buildall |
hello-stephen
commented
Jun 10, 2026
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Jun 10, 2026
TPC-H: Total hot run time: 29290 ms |
hello-stephen
commented
Jun 10, 2026
TPC-DS: Total hot run time: 169600 ms |
hello-stephen
commented
Jun 10, 2026
FE Regression Coverage ReportIncrement line coverage |
BiteTheDDDDt
commented
Jun 11, 2026
/review |
There was a problem hiding this comment.
I found one blocking issue: the new default only applies to fresh FE metadata, while upgraded clusters keep the persisted old global session default.
Critical checkpoint conclusions:
- Goal/test: fresh clusters would get
profile_level=2, but upgraded clusters continue to clone the old persisteddefaultSessionVariablevalue, so the PR does not fully accomplish the stated default-change goal. No test covers this upgrade/persistence path. - Scope: the code change is small and focused, but incomplete because this session default is persisted.
- Concurrency/lifecycle: no new concurrency or lock-order risk; the relevant lifecycle concern is FE image/edit-log loading of
VariableMgr.defaultSessionVariable. - Config/dynamic behavior: this is an existing session variable, not a new config item; global session defaults are persistent and need explicit migration when the intended default changes.
- Compatibility/persistence: missing migration is the main problem.
VariableMgr.read()restores the old value from image before new sessions are created. - Parallel paths: BE fallback/query-option defaults already use level 2 in several paths, but the FE session default remains the source for ordinary new sessions after upgrade.
- Tests: a
VariableMgrserialization/upgrade-style test would catch this. I did not run the full FE test suite in this review runner. - Observability/performance/data correctness/security: no additional issues found in this one-line diff.
- User focus: no additional user-provided review focus was present.
Uh oh!
There was an error while loading. Please reload this page.
hello-stephen
commented
Jun 11, 2026
FE Regression Coverage ReportIncrement line coverage |
Uh oh!
There was an error while loading. Please reload this page.
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: The default query profile level is 1, which only collects merged profile counters. This change sets the FE session default profile_level to 2 so detailed query profile information is collected by default. ### Release note Set the default query profile level to 2. ### Check List (For Author) - Test: No need to test (only changes the default value of a session variable). - Behavior changed: Yes. The default profile_level is changed from 1 to 2. - Does this need documentation: No
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: The default query profile level is 1, which only collects merged profile counters. This change sets the FE session default profile_level to 2 so detailed query profile information is collected by default. ### Release note Set the default query profile level to 2. ### Check List (For Author) - Test: No need to test (only changes the default value of a session variable). - Behavior changed: Yes. The default profile_level is changed from 1 to 2. - Does this need documentation: No
### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: The default query profile level is 1, which only collects merged profile counters. This change sets the FE session default profile_level to 2 so detailed query profile information is collected by default. ### Release note Set the default query profile level to 2. ### Check List (For Author) - Test: No need to test (only changes the default value of a session variable). - Behavior changed: Yes. The default profile_level is changed from 1 to 2. - Does this need documentation: No
What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: The default query profile level is 1, which only collects merged profile counters. This change sets the FE session default profile_level to 2 so detailed query profile information is collected by default.
Release note
Set the default query profile level to 2.
Check List (For Author)