Hi,
I run dgraph in a single Centos7.2 using docker-compose.
Recent days, I want to use bulk load. So I do something as follows:
- create zero.yml
version: "3.2"
services:
zero:
image: dgraph/dgraph:v1.0.10
volumes:
- /data-disk:/dgraph
ports:
- 5080:5080
- 6080:6080
restart: on-failure
command: dgraph zero --my=zero:5080
volumes:
dgraph:
Then I run:
$ docker-compose -f zero.yml up -d
after get the container id of zero_container
I run:
$ docker exec -it 1cfcd66adbaa dgraph bulk -r dgraph.rdf.gz -s dgraph.schema --map_shards=1 --reduce_shards=1 --http localhost:8000 --zero=localhost:5080
and, I can get the out folder.
then I run:
$ docker-compose -f server.yml up -d
The server.yml:
version: "3.2"
services:
server:
image: dgraph/dgraph:v1.0.9
volumes:
- /data-disk:/dgraph
ports:
- 8080:8080
- 9080:9080
restart: on-failure
command: dgraph server --my=server:7080 --lru_mb=2048 --zero=zero:5080 -p out/0/p
ratel:
image: dgraph/dgraph:v1.0.9
volumes:
- /data-disk:/dgraph
ports:
- 8000:8000
command: dgraph-ratel
volumes:
dgraph:
And the dgraph is started. I can see the Schema in ratel(:8000), but when I query something in the Console page, the connect to dgraph is dead. So I look the server logs.I got this:
(only sub-log of the entire logs)
server_1_ecec24be00aa | 2018/11/15 08:59:44 node.go:301: INFO: raft.node: 1 elected leader 1 at term 14
server_1_ecec24be00aa | 2018/11/15 08:59:45 proto: wrong wireType = 0 for field Uid
server_1_ecec24be00aa | github.com/dgraph-io/dgraph/x.Wrap
server_1_ecec24be00aa | /ext-go/1/src/github.com/dgraph-io/dgraph/x/error.go:76
server_1_ecec24be00aa | github.com/dgraph-io/dgraph/x.Check
server_1_ecec24be00aa | /ext-go/1/src/github.com/dgraph-io/dgraph/x/error.go:32
This happened if I Query something.
How can I do to solve this problem.Thanks.