StrikeW
StrikeW
> Good job! > > * I wonder if we support multiple mongodb addresses? It'd be common to have multiple mongodb nodes in real cases. I think we do. The...
@fuyufjh @hzxa21 @tabVersion PTAL again, I‘d like to get the basic functionality merge first.
> need to add a check for the integrity of base CDC table besides the check for the result of query q4, so we can know if the problem lies...
Update: revert #14899 also reproduce the problem, investigating other PRs in the list.
I found that the stream query in the [passed job](https://grafana.test.risingwave-cloud.xyz/d/EpkBw5W4k/risingwave-dev-dashboard?from=1706727600000&orgId=1&to=1706731199000&var-component=All&var-datasource=P2453400D1763B4D9&var-instance=benchmark-risingwave&var-namespace=ch-benchmark-pg-cdc-daily-20240131&var-pod=All&var-table=All) generated much less data compared with failed jobs. And there is join amplification in the failed jobs: I suspect the...
> Hit again with nightly-20240207 > > https://buildkite.com/risingwave-test/ch-benchmark-pg-cdc/builds/205#018d8597-b39f-48ed-bbea-9f1b27b911c8 > > https://grafana.test.risingwave-cloud.xyz/d/EpkBw5W4k/risingwave-dev-dashboard?orgId=1&var-datasource=ebec273b-0774-4ccd-90a9-c2a22144d623&var-namespace=ch-benchmark-pg-cdc-daily-20240207&var-instance=benchmark-risingwave&var-pod=All&var-component=All&var-table=All&from=1707342785684&to=1707348581400 The symptom is same as the conclusion in https://github.com/risingwavelabs/risingwave/issues/14943#issuecomment-1925692637: - Join amplification - Many L0 files which causes barrier...
> > > but if the slowness/freeze is caused by query, then it does not matter. > > It's caused by ch-benchmark q3 in this case. > > @StrikeW Shall...
> The issue still exists with nightly-20240507. Which issue covered this right now? @StrikeW https://buildkite.com/risingwave-test/ch-benchmark-pg-cdc-shared-source/builds/41#018f5655-3749-4029-a4b8-cc0c321eb18a There is no new issue for the performance problem. The source is backpressured and could...
I think this should be a performance issue instead of functionality bug, so I suggest you can create a new issue for it and post to perf working group.
> > IIUC, env should always be passthrough as `shell -> cargo-make -> risedev -> tmux -> risingwave`. For example, I test the distributed tracing with `RW_TRACING_ENDPOINT=... ./risedev d` every...