-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Support running querier #16
base: main
Are you sure you want to change the base?
Conversation
We added experimental support to our helm chart to run stateless querier. via `values.experimental.querier.enabled=true` Signed-off-by: Kaviraj <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge. |
Signed-off-by: Kaviraj <[email protected]>
Signed-off-by: Kaviraj <[email protected]>
I've started a cluster with the queier which was supposed to have a single node and it started 3 replicas for the querier, you will have to override the experimental.querier.replicas values in local-k8s.sh so that both match:
|
Signed-off-by: Kaviraj <[email protected]>
We added experimental support to our helm chart to run stateless querier. via
values.experimental.querier.enabled=true
If you are using the helm chart that supports querier, you can run this local cluster using
QUERIER=true
flag.To use it:
overrides/querier.yaml
tovalues-overrides.yaml
to the root of the repoQUERIER=true
flag