Hi Team, I am encountering an issue where data disappears after a certain period on our Nebula cluster, which is running on a Kubernetes environment. The database and schema remain intact, but the nodes and edges data go missing. Could you provide any insights into what might be causing this data loss or reset?

Hi friend, could you provide us with detailed reproduction steps and error logs?

@Dinah - Thank you for responding. I inserted the data into a specific space. It is running in K8s cluster, problem is schema exists, but data is getting flushed out occasionally. Where can i download the logs here? Thank you

If you enable the log volume, you can access logs from '/usr/local/nebula/logs' inside the nebula container. Alternatively, if you configure logs to be output to stdout, you can retrieve them using the cmd 'kubectl logs $pod -n $namespace'.

@kevin.qiao - ttl_duration = 0

https://github.com/vesoft-inc/nebula/blob/1f3c6b2c2287cf5c4ba6b8d4c057a2a045326c4b/src/storage/mutate/DeleteEdgesProcessor.cpp#L95 https://github.com/vesoft-inc/nebula/blob/1f3c6b2c2287cf5c4ba6b8d4c057a2a045326c4b/src/storage/mutate/DeleteVerticesProcessor.cpp#L84C7-L84C28 https://github.com/vesoft-inc/nebula-operator/blob/master/doc/user/security_context.md https://github.com/vesoft-inc/nebula-stats-exporter/releases/tag/v3.8.0 You can deploy the nebula-stats-exporter to monitor metrics. Additionally, if you are familiar with C++, you can enable the security context to facilitate debugging the Nebula process inside the container.