-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[feat](docker)Modify the init_be and start_be scripts to meet the requirements for rapid Docker startup. #45269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
|
|
run buildall |
|
TeamCity be ut coverage result: |
|
|
|
run buildall |
|
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 40034 ms |
TPC-DS: Total hot run time: 196721 ms |
ClickBench: Total hot run time: 32.77 s |
morningman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
…uirements for rapid Docker startup. (#45269) Related PR: #45267 Problem Summary: To meet the needs of rapid Docker startup, I have made adjustments to two related scripts in the Docker startup process. First, I added a env `SKIP_CHECK_ULIMIT` to the `start_be.sh` script, which will skip the size checks for `swap`, `ulimit`, and `max_map_count`. At the same time, I used `--console` to start the process and print logs. The reason why I did not use the `--daemon` daemon command to execute is that starting with a foreground log printing method in a Docker container is the correct and reliable approach. At the same time, I added a check logic for a `be.conf` configuration item in the `init_be.sh` script: if it is the first time starting, append the export `SKIP_CHECK_ULIMIT=true` to skip the `ulimit` value check in the BE process. In summary, these adjustments can meet the basic requirements for rapid Docker startup usage.
…uirements for rapid Docker startup(Merge 2.1). (#45858) ### What problem does this PR solve? Issue Number: close #xxx Related PR: #45267 Master PR: #45269 Problem Summary: To meet the needs of rapid Docker startup, I have made adjustments to two related scripts in the Docker startup process. First, I added a env `SKIP_CHECK_ULIMIT` to the `start_be.sh` script, which will skip the size checks for `swap`, `ulimit`, and `max_map_count`. At the same time, I used `--console` to start the process and print logs. The reason why I did not use the `--daemon` daemon command to execute is that starting with a foreground log printing method in a Docker container is the correct and reliable approach. At the same time, I added a check logic for a `be.conf` configuration item in the `init_be.sh` script: if it is the first time starting, append the export `SKIP_CHECK_ULIMIT=true` to skip the `ulimit` value check in the BE process. In summary, these adjustments can meet the basic requirements for rapid Docker startup usage.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #45267
Problem Summary:
To meet the needs of rapid Docker startup, I have made adjustments to two related scripts in the Docker startup process. First, I added a env
SKIP_CHECK_ULIMITto thestart_be.shscript, which will skip the size checks forswap,ulimit, andmax_map_count. At the same time, I used--consoleto start the process and print logs. The reason why I did not use the--daemondaemon command to execute is that starting with a foreground log printing method in a Docker container is the correct and reliable approach.At the same time, I added a check logic for a
be.confconfiguration item in theinit_be.shscript: if it is the first time starting, append the exportSKIP_CHECK_ULIMIT=trueto skip theulimitvalue check in the BE process. In summary, these adjustments can meet the basic requirements for rapid Docker startup usage.Release note
None
Check List (For Author)
ulimit,swap, andmax_map_countcheck values on the host machine to values that do not meet the requirements.export SKIP_CHECK_ULIMIT=trueandsh start_be.sh --consoleto start the BE process, which starts up normally.export SKIP_CHECK_ULIMIT=false,then using the--daemonor--consoleoption to start, the BE process fails to start normally.Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)