Why does Aura just go offline?

Neo4j Graph Platform Aura & Cloud
1

I have two Aura instances. One of them is 2GB memory / 4GB storage.

It has gone offline and has been offline for about 15 minutes. This happens when I delete a good chunk of nodes (several thousands). In the instance console, the query will often time out.

But following that, the instance will go down.

In what world is this acceptable? I don't know of any other database that responds in this way to deleting a large number of rows, or nodes. I am not really sure how long it takes to come back up, but I may as well go to bed and check in the morning.

This happens frequently.

Anyone else experience this? What is the solution? It is really the only thing causing me to dither about moving this to production. The other option would be MongoDB, but I have become accustomed to Cypher, although I am not really exploiting the graph idea too much.

2

Turns out, it's still offline 14 hours later.

3

What is the SLA on the instances you are using?

4

How would I know that?

5

Details here Cloud & Self-Hosted Graph Database Platform Pricing | Neo4j

image
image1197×993 68.9 KB

6

Many use Pro for lower environments and then Business Critical or Virtual Dedicated for production.

7

But if your instance has been crashing/offline I would also reach out to support, it does not sound normal.

8

There are also some knowledge base articles on deleting data:

  1. Wipe entire db from aura console: Neo4j Customer Service Portal
  2. Deleting in smaller batches using cypher: Neo4j Customer Service Portal

Deleting can be a heavy operation, so make sure to smooth it out so it does not impact other concurrent users in a negative way.