You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
At present, when some rpc errors occur, the client cannot obtain the error information well.
And this CL change the RPC error returned to client like this:
ERROR 1064 (HY000): errCode = 2, detailMessage = there is no scanNode Backend. [10002: in black list(A error occurred: errorCode=2001 errorMessage:Channel inactive error!)]
ERROR 1064 (HY000): failed to send brpc batch, error=The server is overcrowded, error_text=[E1011]The server is overcrowded @xx.xx.xx.xx:8060 [R1][E1011]The server is overcrowded @xx.xx.xx.xx:8060 [R2][E1011]The server is overcrowded @xx.xx.xx.xx:8060 [R3][E1011]The server is overcrowded @xx.xx.xx.xx:8060, client: yy.yy.yy.yy
Types of changes
Code refactor (Modify the code structure, format the code, etc...)
2021-08-24 17:18:24,477 WARN (doris-mysql-nio-pool-32867|95614) [StmtExecutor.execute():406] execute Exception. {} org.apache.doris.common.UserException: errCode = 2, detailMessage = there is no scanNode Backend. [409768988: in black list(Waited 10000 microseconds (plus 55 microseconds delay) for io.grpc.stub.ClientCalls$GrpcFuture@4b59b6d0[status=PENDING, info=[GrpcFuture{clientCall=ClientCallImpl{method=MethodDescriptor{fullMethodName=doris.PBackendService/update_cache, type=UNARY, idempotent=false, safe=false, sampledToLocalTracing=true, requestMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@509b75a2, responseMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@6bb04bd8, schemaDescriptor=org.apache.doris.proto.PBackendServiceGrpc$PBackendServiceMethodDescriptorSupplier@428ecf20}}}]])] at org.apache.doris.qe.SimpleScheduler.getLocation(SimpleScheduler.java:123) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.selectBackendsByRoundRobin(Coordinator.java:1378) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.computeScanRangeAssignmentByScheduler(Coordinator.java:1395) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.computeScanRangeAssignment(Coordinator.java:1316) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.exec(Coordinator.java:422) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.handleCacheStmt(StmtExecutor.java:782) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.handleQueryStmt(StmtExecutor.java:846) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:343) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:288) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.ConnectProcessor.handleQuery(ConnectProcessor.java:206) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.ConnectProcessor.dispatch(ConnectProcessor.java:344) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.ConnectProcessor.processOnce(ConnectProcessor.java:545) ~[palo-fe.jar:3.4.0] at org.apache.doris.mysql.nio.ReadListener.lambda$handleEvent$0(ReadListener.java:50) ~[palo-fe.jar:3.4.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
there is the similar problem in v0.14
this be node is not crashed but fe.warn has this messge
query is also failed
2021-08-24 17:18:24,477 WARN (doris-mysql-nio-pool-32867|95614) [StmtExecutor.execute():406] execute Exception. {} org.apache.doris.common.UserException: errCode = 2, detailMessage = there is no scanNode Backend. [409768988: in black list(Waited 10000 microseconds (plus 55 microseconds delay) for io.grpc.stub.ClientCalls$GrpcFuture@4b59b6d0[status=PENDING, info=[GrpcFuture{clientCall=ClientCallImpl{method=MethodDescriptor{fullMethodName=doris.PBackendService/update_cache, type=UNARY, idempotent=false, safe=false, sampledToLocalTracing=true, requestMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@509b75a2, responseMarshaller=io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller@6bb04bd8, schemaDescriptor=org.apache.doris.proto.PBackendServiceGrpc$PBackendServiceMethodDescriptorSupplier@428ecf20}}}]])] at org.apache.doris.qe.SimpleScheduler.getLocation(SimpleScheduler.java:123) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.selectBackendsByRoundRobin(Coordinator.java:1378) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.computeScanRangeAssignmentByScheduler(Coordinator.java:1395) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.computeScanRangeAssignment(Coordinator.java:1316) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.Coordinator.exec(Coordinator.java:422) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.handleCacheStmt(StmtExecutor.java:782) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.handleQueryStmt(StmtExecutor.java:846) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:343) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.StmtExecutor.execute(StmtExecutor.java:288) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.ConnectProcessor.handleQuery(ConnectProcessor.java:206) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.ConnectProcessor.dispatch(ConnectProcessor.java:344) ~[palo-fe.jar:3.4.0] at org.apache.doris.qe.ConnectProcessor.processOnce(ConnectProcessor.java:545) ~[palo-fe.jar:3.4.0] at org.apache.doris.mysql.nio.ReadListener.lambda$handleEvent$0(ReadListener.java:50) ~[palo-fe.jar:3.4.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
there is the similar problem in v0.14
this be node is not crashed but fe.warn has this messge
query is also failed
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
morningman
force-pushed
the
send_batch_error
branch
from
Proposed changes
At present, when some rpc errors occur, the client cannot obtain the error information well.
And this CL change the RPC error returned to client like this:
Types of changes
Checklist