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
Background context to the discussion can be found here - #8 (comment)
For this scope, lets focus on deploying the following on kubernetes :
For the current version :
1 : elasticsearch : to store and retrieve vectors and full text search
2 : rabbitmq : for queues
3 : flask server which expose certain ML features : this can be large (1-2 GBs) in terms of memory depending on the ML model loaded
4 : nodejs server : basic REST api, nothing special here.
The text was updated successfully, but these errors were encountered:
Some investigations need to be done on what are the best practices to run elasticsearch on kubernetes. Although elasticsearch requires running 3 nodes in production, I'd like to know if it can be run on a single node to begin with and scale the replica count up later as and when needed.
Background context to the discussion can be found here - #8 (comment)
For this scope, lets focus on deploying the following on kubernetes :
For the current version :
1 : elasticsearch : to store and retrieve vectors and full text search
2 : rabbitmq : for queues
3 : flask server which expose certain ML features : this can be large (1-2 GBs) in terms of memory depending on the ML model loaded
4 : nodejs server : basic REST api, nothing special here.
The text was updated successfully, but these errors were encountered: