The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.
it is the frontend fails to make the thrift rpc call. Not the client fails to call frontend's thrift rpc.
Why I'm doing:
2024-11-07 08:10:54.641Z WARN (heartbeat-mgr-pool-1|176) [ThriftRPCRequestExecutor.call():80] Call frontend thrift rpc failed, addr: TNetworkAddress(hostname:127.0.0.1, port:9050), retried: 0
org.apache.thrift.transport.TTransportException: Socket is closed by peer.
at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:177) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:100) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:519) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:387) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:271) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79) ~[libthrift-0.20.0.jar:0.20.0]
at com.starrocks.thrift.HeartbeatService$Client.recv_heartbeat(HeartbeatService.java:64) ~[starrocks-fe.jar:?]
at com.starrocks.thrift.HeartbeatService$Client.heartbeat(HeartbeatService.java:51) ~[starrocks-fe.jar:?]
at com.starrocks.system.HeartbeatMgr$BackendHeartbeatHandler.lambda$call$0(HeartbeatMgr.java:292) ~[starrocks-fe.jar:?]
at com.starrocks.rpc.ThriftRPCRequestExecutor.call(ThriftRPCRequestExecutor.java:67) ~[starrocks-fe.jar:?]
at com.starrocks.rpc.ThriftRPCRequestExecutor.callNoRetry(ThriftRPCRequestExecutor.java:40) ~[starrocks-fe.jar:?]
at com.starrocks.system.HeartbeatMgr$BackendHeartbeatHandler.call(HeartbeatMgr.java:289) ~[starrocks-fe.jar:?]
at com.starrocks.system.HeartbeatMgr$BackendHeartbeatHandler.call(HeartbeatMgr.java:264) ~[starrocks-fe.jar:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
TNetworkAddress(hostname:127.0.0.1, port:9050) is actually the BE thrift service port.
What I'm doing:
Fixes #issue
What type of PR is this:
[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool
Does this PR entail a change in behavior?
[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.
If yes, please specify the type of change:
[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.
Checklist:
[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function
[x] This is a backport pr
Bugfix cherry-pick branch check:
[x] I have checked the version labels which the pr will be auto-backported to the target branch
[x] 3.3
[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5
This is an automatic backport of pull request #52706 done by Mergify.
it is the frontend fails to make the thrift rpc call. Not the client fails to call frontend's thrift rpc.
Why I'm doing:
2024-11-07 08:10:54.641Z WARN (heartbeat-mgr-pool-1|176) [ThriftRPCRequestExecutor.call():80] Call frontend thrift rpc failed, addr: TNetworkAddress(hostname:127.0.0.1, port:9050), retried: 0
org.apache.thrift.transport.TTransportException: Socket is closed by peer.
at org.apache.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:177) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.transport.TTransport.readAll(TTransport.java:100) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:519) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:387) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:271) ~[libthrift-0.20.0.jar:0.20.0]
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:79) ~[libthrift-0.20.0.jar:0.20.0]
at com.starrocks.thrift.HeartbeatService$Client.recv_heartbeat(HeartbeatService.java:64) ~[starrocks-fe.jar:?]
at com.starrocks.thrift.HeartbeatService$Client.heartbeat(HeartbeatService.java:51) ~[starrocks-fe.jar:?]
at com.starrocks.system.HeartbeatMgr$BackendHeartbeatHandler.lambda$call$0(HeartbeatMgr.java:292) ~[starrocks-fe.jar:?]
at com.starrocks.rpc.ThriftRPCRequestExecutor.call(ThriftRPCRequestExecutor.java:67) ~[starrocks-fe.jar:?]
at com.starrocks.rpc.ThriftRPCRequestExecutor.callNoRetry(ThriftRPCRequestExecutor.java:40) ~[starrocks-fe.jar:?]
at com.starrocks.system.HeartbeatMgr$BackendHeartbeatHandler.call(HeartbeatMgr.java:289) ~[starrocks-fe.jar:?]
at com.starrocks.system.HeartbeatMgr$BackendHeartbeatHandler.call(HeartbeatMgr.java:264) ~[starrocks-fe.jar:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
TNetworkAddress(hostname:127.0.0.1, port:9050) is actually the BE thrift service port.
What I'm doing:
Fixes #issue
What type of PR is this:
[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool
Does this PR entail a change in behavior?
[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.
If yes, please specify the type of change:
[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.
Checklist:
[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function
Why I'm doing:
TNetworkAddress(hostname:127.0.0.1, port:9050)
is actually the BE thrift service port.What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check:
This is an automatic backport of pull request #52706 done by Mergify.
Why I'm doing:
TNetworkAddress(hostname:127.0.0.1, port:9050)
is actually the BE thrift service port.What I'm doing:
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: