Moved from GitHub dgraph/4231
Posted by jm4games:
Dgraph version : v1.1.0
Dgraph SHA-256 : 7d4294a80f74692695467e2cf17f74648c18087ed7057d798f40e1d3a31d2095
Commit SHA-1 : ef7cdb28
Hardware Spec ?
OS: Arch Linux, (running dgraph in docker env)
CPU: AMD 3900x
Steps to reproduce the issue (command/config used to run Dgraph).
schema.txt - graph layout
trait.txt - initial seed data
graph.gz - (full graph)
Update schema through dgraph web UI (copy and paste schema.txt into schema bulk edit)
Then run the following from shell in dir where downloaded trait.txt.gz and graph.gz exist.
$ curl -X POST -H 'Content-Encoding: gzip' -H "Content-Type: application/rdf" localhost:8080/mutate\?commitNow=true --data-binary @trait.txt.gz $ curl -X POST -H 'Content-Encoding: gzip' -H "Content-Type: application/rdf" localhost:8080/mutate\?commitNow=true --data-binary @graph.gz
Expected behaviour and actual result.
Dgraph should process the graph, but instead spins on it and never completes processing.
I know the graph itself is sound as I have processed smaller data sets with the exact layout. It seems once a graph reaches a certain size dgraph can no longer process it. Maybe I have exceed some sort of internal limit. I have also attached log of dgraph server and it looks like a raft consensus is timing out.