Skip to content
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

K8S pod sync #2

Open
nazzour opened this issue Dec 13, 2021 · 1 comment
Open

K8S pod sync #2

nazzour opened this issue Dec 13, 2021 · 1 comment

Comments

@nazzour
Copy link

nazzour commented Dec 13, 2021

Hello,
first of all thank you for your work, it is really very simple to use and very helpful. I just have an issue with deploying to k8s. If we deploy with more than one replica, each pod will have its own index and thus if we make a search we will have different results depending on the pod. I know that there are some projects that are trying to solve this issue like milvus but do you see any simple solution for this issue ? Thanks in advance

@louiezzang
Copy link
Owner

louiezzang commented Dec 29, 2021

Hey @nazzour ,
Sorry for late reply. Updated my reply again.

CASE 1: If the two faiss-servers have the same embedding dimension but different vector content, you can deploy to K8S with StatefulSet mode. And you can access the specific POD with different host name in the explicit way. I think this could be your use case.
Please see the StatefulSet K8S yaml file example https://github.com/louiezzang/faiss-server/blob/master/faiss-server-k8s-example-stateful.yaml

CASE 2: If you want to deploy two different faiss-servers(which have different embedding dimension), you have to deploy each to K8S with the different K8S yaml files for each purpose. In the specific faiss-server(K8S yaml file), you can create replicas(eg. 2 PODs) which will have the exact same embeddings.

Hope this would help you.
Please let me know if you have any question or issue.
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants