You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the query-frontend can run with and without query-scheduler. Query-scheduler is a better solution because it allows to indefinitely scale the query-frontend. To simplify deployment options and converge towards a unique model, we could remove the support to run query-frontend without query-scheduler.
The text was updated successfully, but these errors were encountered:
@pracucci -- Clearly we're not going to do this in time for the GEM 2.0 launch, but I am just curious for if/when we would do this, does this mean that now the 'query-scheduler' would be a required component for a microservices deployment and would have to become a component in the monolithic deployment (meaning that the 'query-scheduler' would now need to be included when target=all?).
and would have to become a component in the monolithic deployment (meaning that the 'query-scheduler' would now need to be included when target=all?).
It's tricky because the query-scheduler can become a component of -target=all but it wouldn't work fine with any large number of replicas, for the same reason why it doesn't work fine the query-frontend (number of query-scheduler replicas should be <= queriers).
Currently the query-frontend can run with and without query-scheduler. Query-scheduler is a better solution because it allows to indefinitely scale the query-frontend. To simplify deployment options and converge towards a unique model, we could remove the support to run query-frontend without query-scheduler.
The text was updated successfully, but these errors were encountered: