Stored graph disapears after conexion breaks

[laurasck14]

Hi, I'm using the Jupyter notebook extension for NebulaGraph as a graph store for LlamaIndex using the NebulaPropertyGraphStore. My graph is already constructed so I just created a space using CREATE SPACE IF NOT EXISTS PrimeKG(vid_type=FIXED_STRING(256)) and upserted my nodes and edges into NebulaGraph.

I have had the issue a couple of times already where after using some of the functions from Llamaindex the conexion to NebulaGraph breaks and the graphs in NebulaGraph get deleted. I'm not sure why the conexion breaks but I'm assuming because the operation is very large?

First it will show there graph is still there when running %ngql --address 127.0.0.1 --port 9669 --user root --password nebula but give the error message RuntimeError: Failed to get a valid session, no graph service is available when using a function like VectorContextRetriever (the graph could still be used like with graph_store.get(ids=['35769'])). Then later the graph disapeared altogether.

My questions:

1. Why is this happening? is there something to do with how I created the graph space? how can I avoid this?
2. Is there a way I can generate a copy of my graph so that if this happens I can just restore it?
3. why does my conextion to NebulaGraph keep on breaking after using the graph.