Unable to delete a vertex in AWS Neptune even after removing all its 50k+ edges
Hi everyone,
I’m running into a strange issue with AWS Neptune and would appreciate any insights.
I’m trying to delete a vertex that used to have over 50,000 edges. Before attempting the deletion, I made sure to remove all the relationships connected to it (using both bothE().drop() and validations to confirm there are no remaining edges).
When I validate the vertex afterward, it shows 0 relationships, but when I try to delete it with something like:
g.V(vertexId).drop().iterate()
the operation just hangs and never completes — almost as if the vertex were still “locked” or referencing something internally.
Has anyone seen this behavior before on Neptune?
Could it be some kind of internal index or cleanup process that prevents deleting large, previously connected vertices?
Any advice or explanation about this behavior would be really helpful.
Thanks in advance!
— Hugo
I’m running into a strange issue with AWS Neptune and would appreciate any insights.
I’m trying to delete a vertex that used to have over 50,000 edges. Before attempting the deletion, I made sure to remove all the relationships connected to it (using both bothE().drop() and validations to confirm there are no remaining edges).
When I validate the vertex afterward, it shows 0 relationships, but when I try to delete it with something like:
g.V(vertexId).drop().iterate()
the operation just hangs and never completes — almost as if the vertex were still “locked” or referencing something internally.
Has anyone seen this behavior before on Neptune?
Could it be some kind of internal index or cleanup process that prevents deleting large, previously connected vertices?
Any advice or explanation about this behavior would be really helpful.
Thanks in advance!
— Hugo
Apache TinkerPop is an open source graph computing framework and the home of the Gremlin graph query language.
1,376Members
Resources
Similar Threads
Was this page helpful?
