Igor Lukanin

It looks like this behavior is caused by the `express-graphql` library that is used by Cube to implement the GraphQL API: https://github.com/cube-js/cube/blob/b8de472b054f513732671e2211c4b2df1f811e99/packages/cubejs-api-gateway/src/gateway.ts#L230-L239 Unfortunately, this library is not maintained anymore. Probably,...

As a non-ideal workaround, I may suggest updating `orchestrator_options` (https://cube.dev/docs/reference/configuration/config#orchestrator_options) with a bigger `continueWaitTimeout` or, preferably, using pre-aggregations to speed up queries and eliminate "continue waits" completely.

Hey @ranjeetranjan 👋 Is this still a standing issue? If so, does it reproduce?

After another look at the error/data size/concurrency, I suspect that the issue is that ClickHouse doesn't handle the load well and the error is related to ClickHouse rather than Cube....

@ranjeetranjan What is your `CUBEJS_CONCURRENCY` env var setting? Could you please check what happens if you increase or decrease it.

It looks like this might require a fairly tiny change to this part of code: https://github.com/cube-js/cube/blob/master/packages/cubejs-api-gateway/src/graphql.ts#L378-L398

Hey @josephybh @P-Arnold and everyone 👋 Which version of Cube are you using? Could you please try upgrading to the latest one? I've checked this very source code with Cube...

@codingchili Thanks for contributing this! ❤️ Indeed, it would be nice if anyone could make a PR and bring it over the finish line 😄

@rajatch80 Does this reproduce for you as well? On which version of Cube (if you don't mind sharing)? Indeed, storing pre-aggregations in the original data source is not recommended. Please...

@rajatch80 If you don't want to use Cube Store, you can comment out the pre-aggregations in your data model and have Cube query your upstream data sources directly.