-
Notifications
You must be signed in to change notification settings - Fork 71
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
Data Persistence #16
Comments
Hi @radford1. I'm try this way too. Actually the data is not missing, try to use this filter:
I think the problem is with Solr, i'm try to set SOLR_DATA_HOME, but without success until now. |
Hey there. I solved this problem, if you looking for yet. It's a problem with Solr really. Setting the SOLR_DATA_HOME should work, but core.properties file, from each index is created at default folder, without considerer the env SOLR_DATA_HOME. This should resolve the problem:
(/mnt/atlas-2.1.0 is the mountPath of volumeMounts of the k8s) This steps resolve the problem and the Atlas Pod can be restarted without problems. |
Probably need to add this to the README. Thanks! |
@rodrigoassumpcao Can you share your OpenShift/Kubernetes templates? |
@rodrigoassumpcao - Thanks for the step-by-step instructions on how to persist the Atlas data. Is there a version for Windows env? Much appreciated.Thanks! |
Hi @TuncTaylan, i will looking for the template and post here. Hi @krrgithub00, I just try using k8s, with linux image. |
Thanks, Rodrigo!
Raghu Kundurthi/sent from my i-phone
PS-Pardon the inadvertent typos!
… On Apr 27, 2021, at 12:35, rodrigoassumpcao ***@***.***> wrote:
Hi @TuncTaylan, i will looking for the template and post here.
Hi @krrgithub00, I just try using k8s, with linux image.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi, the right config maybe:
|
Is there a way to persist data even after the container is removed and then re-deployed. I am able to successfully mount the data directory from your instructions and the data persists when I stop and start the container, but when I remove and re-deploy the container the existing entities do not appear in the Atlas UI.
The text was updated successfully, but these errors were encountered: