-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](meta) fix follower sync image timeout after checkpoint. #26003
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
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
dataroaring
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. |
|
PR approved by anyone and no changes requested. |
yiguolei
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
…#26003) The image file of our cluster reaches 2.3G. After the checkpoint, Followers synchronize the image timeout, resulting in the continuous increase of the bdb directory. related pr: apache#25768
…#26003) The image file of our cluster reaches 2.3G. After the checkpoint, Followers synchronize the image timeout, resulting in the continuous increase of the bdb directory. related pr: apache#25768
Related PR: #26003 Problem Summary: > If image file is very huge, it maybe occurs http Read timed out when pulling image from FE Master ```java java.io.IOException: java.net.SocketTimeoutException: Read timed out at org.apache.doris.catalog.Env.getNewImage(Env.java:1664) at org.apache.doris.catalog.Env.getClusterIdAndRole(Env.java:1126) at org.apache.doris.catalog.Env.initialize(Env.java:884) at org.apache.doris.DorisFE.start(DorisFE.java:163) at org.apache.doris.DorisFE.main(DorisFE.java:83) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun. reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1952) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1947) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.iava:1946) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1516) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1500) at org.apache.doris.master.MetaHelper.getResponse(MetaHelper.java:130) at org.apache.doris.master.MetaHelper.getRemoteFile(MetaHelper.java:98) at org.apache.doris.catalog.Env.getNewImage(Env.java:1657) ... 4 more ```
Related PR: #26003 Problem Summary: > If image file is very huge, it maybe occurs http Read timed out when pulling image from FE Master ```java java.io.IOException: java.net.SocketTimeoutException: Read timed out at org.apache.doris.catalog.Env.getNewImage(Env.java:1664) at org.apache.doris.catalog.Env.getClusterIdAndRole(Env.java:1126) at org.apache.doris.catalog.Env.initialize(Env.java:884) at org.apache.doris.DorisFE.start(DorisFE.java:163) at org.apache.doris.DorisFE.main(DorisFE.java:83) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun. reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1952) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1947) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.iava:1946) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1516) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1500) at org.apache.doris.master.MetaHelper.getResponse(MetaHelper.java:130) at org.apache.doris.master.MetaHelper.getRemoteFile(MetaHelper.java:98) at org.apache.doris.catalog.Env.getNewImage(Env.java:1657) ... 4 more ```
Related PR: #26003 Problem Summary: > If image file is very huge, it maybe occurs http Read timed out when pulling image from FE Master ```java java.io.IOException: java.net.SocketTimeoutException: Read timed out at org.apache.doris.catalog.Env.getNewImage(Env.java:1664) at org.apache.doris.catalog.Env.getClusterIdAndRole(Env.java:1126) at org.apache.doris.catalog.Env.initialize(Env.java:884) at org.apache.doris.DorisFE.start(DorisFE.java:163) at org.apache.doris.DorisFE.main(DorisFE.java:83) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun. reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1952) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1947) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.iava:1946) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1516) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1500) at org.apache.doris.master.MetaHelper.getResponse(MetaHelper.java:130) at org.apache.doris.master.MetaHelper.getRemoteFile(MetaHelper.java:98) at org.apache.doris.catalog.Env.getNewImage(Env.java:1657) ... 4 more ```
…51120) Related PR: apache#26003 Problem Summary: > If image file is very huge, it maybe occurs http Read timed out when pulling image from FE Master ```java java.io.IOException: java.net.SocketTimeoutException: Read timed out at org.apache.doris.catalog.Env.getNewImage(Env.java:1664) at org.apache.doris.catalog.Env.getClusterIdAndRole(Env.java:1126) at org.apache.doris.catalog.Env.initialize(Env.java:884) at org.apache.doris.DorisFE.start(DorisFE.java:163) at org.apache.doris.DorisFE.main(DorisFE.java:83) Caused by: java.net.SocketTimeoutException: Read timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun. reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1952) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1947) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.iava:1946) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1516) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1500) at org.apache.doris.master.MetaHelper.getResponse(MetaHelper.java:130) at org.apache.doris.master.MetaHelper.getRemoteFile(MetaHelper.java:98) at org.apache.doris.catalog.Env.getNewImage(Env.java:1657) ... 4 more ```
Proposed changes
The image file of our cluster reaches 2.3G. After the checkpoint, Followers synchronize the image timeout, resulting in the continuous increase of the bdb directory.
related pr: #25768
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...