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
{{ message }}
Repository navigation
[fe bug] query information_schema.tables cost 7s, even more #4824
after some check, it's known to us how this happened. how to exec the sql between fe and be
we user --------> fe --------------> be --------------------------------------------------------> fe
sql sql plan rpc call to get information_schema data from fe
when socket between FE and BE for rpc call timeout and BE calling fe, FE would send TCP RST command to BE, BE would retry ( after 1s in default, can be configed for thrift_client_retry_interval_ms ).
Activity
francisoliverlee commentedon Oct 30, 2020
after some check, it's known to us how this happened. how to exec the sql between fe and be
when socket between FE and BE for rpc call timeout and BE calling fe, FE would send TCP RST command to BE, BE would retry ( after 1s in default, can be configed for thrift_client_retry_interval_ms ).
the retry is the COST.
caiconghui commentedon Oct 30, 2020
@francisoliverlee but I am stiil confused that even thrift client retry why cost so much time about 7s?
francisoliverlee commentedon Nov 1, 2020
so do i. until now i can point out it is the RPC-CALL-FROM-BE-2-FE cost more than 1s. there are 2 prof
prof 1:
prof 2
there are 2 possibilities
[fix](outfile) fix small file output with bz2 compression (apache#56368…