1.
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????bdbje??????FE????????????????????????????????????????????
2.
??????????????????????????????????????????????????????????????????????Feature????????
3.
??????????????PR??????????????????????????????????????????????????????????????????????????????????????????QPS??????????????????????????????
4. ??????????????????????????????FE
local??????????????????Doris????????????????????????????????
------------------ ???????? ------------------
??????:
"dev"
<wangbo13...@gmail.com>;
????????: 2022??2??18??(??????) ????1:18
??????: "dev"<dev@doris.apache.org>;
????: Re: Re: Doris ??????????????
>>
????qps????????????????????????????????????qps??????????????????????????????????????????????????????????????????????????????????qps??????qps??????????????????????????????????????????
????????????????
??kv????????????????qps??????????????????????????????????????sql??????????????????kv??????????????????????????
????sql??????????????qps????????????????????????????????????????????????????????????????bug??????????????????????sql??????????????????????????????????????????????
????????????????????????????????????????????qps??????????????
????????????????????????????????????????????????????????????????????????????????
????????????????????????????????????????????????????????????????????????????????????????????
>> First of all, qps is a performance indicator. In quite a few scenarios,
high qps may indicate that the latency of the query is very low, rather
than a sign that the cluster bottleneck may be reached
Very valuable suggestion.
Different from the kv database, qps cannot fully feedback the load of the
system, because the writing method of different sql is very different, and
the request of the kv system is relatively simple and similar.
For the SQL database to protect the system by restricting qps, I personally
understand that it may only be suitable for extreme scenarios, such as user
code bugs that lead to unlimited submission of SQL to the database, as far
as our internal scenarios are concerned, it may not be used in most
scenarios;
In short, system protection is a relatively comprehensive large-scale
system engineering, and qps is only one aspect.
What I agree with is that if you decide to do it, it is best not to affect
the original logic, including performance and code complexity.
???? Wang Bo
?????? <caiconghui2...@163.com> ??2022??2??18?????? 12:54??????
>
>
??????????????????feature??????????????????????????????????qps????????????????????????????????????qps??????????????????????????????????????????????????????????????????????????????????qps??????qps????????????????????????????????????????????
>
> ??????????????????????????????sql??????????????????????????????
>
>
>
????????????????????????????C++??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
>
>
>
????????????????????????????????????????????????????????????????????????????????????????????
> Thanks Tian Hui for this feature, but there are two points I want to
> discuss.
> First of all, qps is a performance indicator. In quite a few scenarios,
> high qps may indicate that the latency of the query is very low, rather
> than a sign that the cluster bottleneck may be reached. For example, there
> are hundreds of qps and thousands of qps in our business. The number of
> connections is not high, mainly low-latency queries.
> In addition, can it be considered that it is better to use the sql running
> at the same time not to exceed a certain amount?
>
>
> Second, I think the principle of restriction is similar to that of C++. We
> need to try to achieve zero overhead: You don??t need to pay for things you
> don??t need. How big is the impact on query or meta management performance.
>
>
>
>
> ?? 2022-02-18 12:39:31??"????" <wangbo13...@gmail.com> ??????
> >??????????????????????????????
>
>????????????????????????????sql????????????doris??????????qps????????????????????????????????????????
> >????????????????????????????
> >1
????????????????????????????????????????????????????????????????????sql??????????????????
> >2
??????????????qps??????????fe????????????????????doris????????????????
> >
>
>????????????????????????????????????????????????????????????????????????????????
> >
> >???? Wang Bo
>
>
>------------------------------------------------------------------------------------------------------------------
> >Hello, Tian Hui, thank you for your suggestion;
> >I understand that you want to protect the Doris cluster by limiting the
> >maximum number of running SQLs. QPS is indeed an aspect of cluster
> >protection, and it is worth doing.
> >However, I still have a few questions to ask:
> >1 I don't quite understand the reason why the current number of queries
> >should be persisted. I think that I only need to save the maximum
number
> of
> >running sqls.
> >2 Secondly, this maximum qps limit can also be placed in fe, you can
refer
> >to the implementation of the maximum number of connections in doris.
> >Finally, it is expected to be able to supplement a relatively complete
> >design document, including the problem background, scheme design and
user
> >manual.
> >
> >???? Wang Bo
> >
> >?? <827677...@qq.com.invalid> ??2022??2??18?????? 12:07??????
> >
> >> ???????????????????????????? Doris
???????????????????????????????????????????????????????????????????? Doris
> >> ?????????????????????????????????????????????????????????? Doris
> >>
>
??????????????????????????????????????????????FE??????????????????????????????????????????????bdbje????????????????????????????????PR??????
> >> https://github.com/apache/incubator-doris/pull/7474
> >>
> >>
> >> ??????PR????????????????????
> >> 1. ????????????bdbje????????????
> >> &nbsp; &nbsp; &nbsp;
> >>
>
????????????FE????????????????????????????????????????????bdbje??????????????????????????????????????????????????????????????????????Doris??????????????????????????????????????????dbdje????????????????????
> >> 2. ??????????????????????????????????
> >> &nbsp; &nbsp; &nbsp;
> >>
??????????????????????????????????????????????????????QPS??????????????MySQL??????????????????????????????????????????Nginx??LVS
> >>
>
????????????QPS??????????????????????????????????SQL??????????????????????????????????SQL????????????????????????????????????????????????
> >>
> >>
> >> ????????????Feature??????????????????????????
>
