Uh oh!
There was an error while loading. Please reload this page.
[fix](metric) fix issue that the counter of rejected transactions does not cover some failed situations for load - #23363
Conversation
caiconghui
commented
Aug 23, 2023
run buildall |
hello-stephen
commented
Aug 23, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
caiconghui
commented
Aug 23, 2023
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
yiguolei
commented
Aug 24, 2023
run buildall |
…s not cover some failed situations for load
caiconghui
commented
Aug 24, 2023
run buildall |
hello-stephen
commented
Aug 24, 2023
(From new machine)TeamCity pipeline, clickbench performance test result: |
morningman
commented
Aug 25, 2023
Could you explain more in detail? |
caiconghui
commented
Aug 25, 2023
done |
…s not cover some failed situations for load (apache#23363) Co-authored-by: caiconghui1 <caiconghui1@jd.com> [enhancement](thirdparty) upgrade thirdparty libs - again (apache#23414) submit again apache#23290 (not upgrade brpc, because bthread local has error) protobuf 3.15.0 -> 21.11 glog 0.4.0 -> 0.6.0 lz4 1.9.3 -> 1.9.4 curl 7.79.0 -> 8.2.1 zstd 1.5.2 -> 1.5.5 arrow 7.0.0 -> 13.0.0 abseil 20220623.1 -> 2023012.3 orc 1.7.2 -> 1.9.0 jemalloc for arrow 5.2.1 -> 5.3.0 xsimd 7.0.0 -> 13.0.0 opentelemetry-proto 0.19.0 -> 1.0.0 opentelemetry 1.8.3 -> 1.10.0 new: c-ares -> 1.19.1 grpc -> 1.54.3
…s not cover some failed situations for load (#23363) Co-authored-by: caiconghui1 <caiconghui1@jd.com>
…s not cover some failed situations for load (#23363) Co-authored-by: caiconghui1 <caiconghui1@jd.com>
…s not cover some failed situations for load (apache#23363) Co-authored-by: caiconghui1 <caiconghui1@jd.com>
Proposed changes
For now,when data exceed database data quota or set invalid timeout, the transaction will be reject without count in metric of rejected transactions,the user may be confused while all transactions metric is ok,but the load task still failed
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...