-
Notifications
You must be signed in to change notification settings - Fork 69
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
Kubernetes Install issue #56
Comments
Just ran into this too. you can set |
in addition to @si-rob
Also:
|
So the configured probes in helm are causing that Now Next error:
|
@jalberto I have same error, but wtihout Kubernetes set up. What kind of database we are talking about here? Is some config key is missing? @colethienes Also validated and got same result by using standalone pip package. Anybody have an idea what's wrong with it? |
It's elasticsearch, I still was not able to make this work
El lun., 13 abr. 2020 13:51, Konstantin Perikov <[email protected]>
escribió:
… @jalberto <https://github.com/jalberto> I have same error, but wtihout
Kubernetes set up. What kind of database we are talking about here? Is some
config key is missing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYMV64NRZQ2WS6FUUSUZDRML3SFANCNFSM4LFEB5EA>
.
|
@jalberto I doubt, error message is saying sqlite3.OperationalError: unable to open database file which is have to do with sqlite, not Elastic itself. Also I managed to make it working on 0.3.3 which means, that it's potentially a bug introduced |
Most likely the same bug as #61 |
Hi,
I'm trying to install nboost in Kubernetes cluster using below command,
helm install nboost --set replicaCount=3 --set service.type=ClusterIP --set args.uhost=elasticsearch-elasticsearch-coordinating-only nboost/nboost
Its crashing,
Can you please help.
The text was updated successfully, but these errors were encountered: