Dgraph version : v1.0.11
Commit SHA-1 : b2a09c5b
Commit timestamp : 2018-12-17 09:50:56 -0800
Branch : HEAD
Go version : go1.11.1
We have RDFs near to 500 million and trying to index them to dgraph using dgraph live.
The server crashed few time in between and I had to restart the server and continue indexing. For this purpose I am using -x switch to store the xid to uid mappings too.
Now I see a new error in the logs continuously:
dgraph[3971]: E0220 07:02:39.913535 3971 storage.go:540] i=940703<first=940704, ErrSnapOutOfDate
dgraph[3971]: W0220 07:02:39.913541 3971 draft.go:333] Error while calling CreateSnapshot: requested index is older than the existing snapshot. Retrying…
And the db is not loading at all. Not able to query the already indexed nodes as well.
Looks like the indexes have crashed. Is there a way to rollback to a previous safe state and continue the indexing.
I strongly recommend you to use Bulk Load. As you mention on Slack that you’re using Live Load. It is much safer and faster and less resources needed to use Bulk Load for that kind of situation.
I increased the RAM to 32GB and started indexing (altered schema in Ratel). I see the below log even when I restart dgraph service. And its stuck there since long.
dgraph[3755]: I0221 08:00:17.710171 3755 index.go:33] Deleting index for title
dgraph[3755]: I0221 08:00:17.831886 3755 index.go:38] Rebuilding index for title
I cant query on other indexes too when this update is happening. Is this an expected behaviour?
We see no much I/O activities as well. (used iotop)
How long will the indexing take?
Is there a way to cancel the index creation once triggered?