Gozde

Yes I mean StorageCloudMergeTree object in the worker. I understand loading different parts, but recreating table every time creates an interesting error on retry or fallback when a timeout or...

We are actually running the latest master and still observe the same error sometimes. When it happens, I also observe this error from server: 2024.03.04 06:34:41.053854 [ 370177 ] {}...

Any number of possible errors return table already exists :)

@dmthuc How should we configure Prometheus monitor? I tried with ``` apiVersion: monitoring.coreos.com/v1 kind: PodMonitor metadata: labels: app: byconity-server-pod-monitor # release needs to match prometheus-operator release name # helm ls...

A more specific point would be how can I get system wide parts count per table from these metrics? Or cpu usage per worker?

for example running explain analyze tells me: └─ TableScan ed_mt.ed_log -- Est. ? rows, cost 0.000000e+00 Act. Output: 288.3K rows (439.6 MB), Wait Time: 180.9 ms, Wall Time: 107.5 s...

Hey @wuwenw and @superhail, I ran a query that should utilize a tokenbf_v1 index and query_log profile section is this: ``` { "CatalogTime": 14, "CnchDiskCacheNodeUnLocalityParts": 3766, "CnchSendResourceElapsedMilliseconds": 17857, "CnchSendResourceRpcCallElapsedMilliseconds": 33,...

You can see from the profile event i shared above that those information is not available for a typical select query @superhail and @smmsmm1988 . I dont know thats a...

Its from server, but I believe they should be propagated to server logs too because accessing worker logs takes > 3 minutes every time i try to hit query log...