Data Persistence
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.
Hi @radford1. I'm try this way too.
Actually the data is not missing, try to use this filter:
- Type:_ALL_ENTITY_TYPES
- Classification:_NOT_CLASSIFIED
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:
- Create the volume and volumeMount as normal in the k8s yaml
- Do not set SOLR_DATA_HOME
- Create this three folders inside the file system (that one is the k8s volume):
-
- vertex_index_shard1_replica_n1
-
- fulltext_index_shard1_replica_n1
-
- edge_index_shard1_replica_n1
- In the Atlas Dockerfile create symbolic links to this folders:
RUN ln -sf /mnt/atlas-2.1.0/solr/vertex_index_shard1_replica_n1 $ATLAS_HOME_DIR/solr/server/solr/vertex_index_shard1_replica_n1 && \
ln -sf /mnt/atlas-2.1.0/solr/fulltext_index_shard1_replica_n1 $ATLAS_HOME_DIR/solr/server/solr/fulltext_index_shard1_replica_n1 && \
ln -sf /mnt/atlas-2.1.0/solr/edge_index_shard1_replica_n1 $ATLAS_HOME_DIR/solr/server/solr/edge_index_shard1_replica_n1
(/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:
docker run -d \
-v /opt/atlas_docker/data:/opt/apache-atlas-2.1.0/data \
-v /opt/atlas_docker/logs:/opt/apache-atlas-2.1.0/logs \
-v /opt/atlas_docker/conf:/opt/apache-atlas-2.1.0/conf \
-v /opt/atlas_docker/data/solr/edge_index_shard1_replica_n1:/opt/apache-atlas-2.1.0/solr/server/solr/edge_index_shard1_replica_n1 \
-v /opt/atlas_docker/data/solr/fulltext_index_shard1_replica_n1:/opt/apache-atlas-2.1.0/solr/server/solr/fulltext_index_shard1_replica_n1 \
-v /opt/atlas_docker/data/solr/vertex_index_shard1_replica_n1:/opt/apache-atlas-2.1.0/solr/server/solr/vertex_index_shard1_replica_n1 \
--network=host \
-p 21001:21000 \
--name atlas \
sburn/apache-atlas \
/opt/apache-atlas-2.1.0/bin/atlas_start.py