I guess the {"errors":[{"code":"rpc error: code = Unknown desc = Assigning IDs is only allowed on leader.","message":"Export failed."}]} error is related to the
zero_1 | 2018/12/14 09:31:51 zero.go:540: Error while applying proposal in update stream While proposing error: context deadline exceeded
zero_1 | 2018/12/14 09:31:53 raft.go:1070: INFO: 1 no leader at term 3; dropping index reading msg
errors, which sounds like need to be fixed through version update.
I’m curious what steps you would recommend to take in the future to prevent/reduce the chance of data loss? I thought
volumes:
- ./_dgraphdata:/dgraph
Where the folder could then be synced with other servers was the perfect solution, but it seemed I misunderstood/overestimated the value of this folder. How would you do it (assuming you just want to run on one server)? A cron job that did a curl admin/export every X hours? And if so, what method would you recommend to backup this exported data afterwards?
Edit: by the way, I can confirm that the raft.go:1070: INFO: 1 no leader at term 3; dropping index reading msg error is relevant up until v1.0.9
In v1.0.10 the error is replaced with Error: unknown command "server" for "dgraph". There doesn’t appear to be any errors with ratel but the server shows the following errors repeated in different colors.
server_1 exited with code 1
server_1 | Error: unknown command “server” for “dgraph”
server_1 | Run ‘dgraph --help’ for usage.
server_1 | unknown command “server” for “dgraph”
server_1 | Error: unknown command “server” for “dgraph”
server_1 | Run ‘dgraph --help’ for usage.
server_1 | unknown command “server” for “dgraph”
server_1 | Error: unknown command “server” for “dgraph”
server_1 | Run ‘dgraph --help’ for usage.
server_1 | unknown command “server” for “dgraph”
zero_1 | E1214 09:25:31.431993 1 oracle.go:425] No healthy connection found to leader of group 1
In v1.0.11-rc4 both the old and new errors seem to appear:
server_1 | Error: unknown command “server” for “dgraph”
server_1 | Run ‘dgraph --help’ for usage.
server_1 | unknown command “server” for “dgraph”
server_1 | Error: unknown command “server” for “dgraph”
server_1 | Run ‘dgraph --help’ for usage.
server_1 | unknown command “server” for “dgraph”
zero_1 | W1214 09:22:39.602250 1 node.go:550] [1] Read index context timed out
zero_1 | I1214 09:22:39.602324 1 node.go:83] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 09:22:42.602629 1 node.go:550] [1] Read index context timed out
zero_1 | I1214 09:22:42.602716 1 node.go:83] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 09:22:45.603044 1 node.go:550] [1] Read index context timed out
zero_1 | I1214 09:22:45.603139 1 node.go:83] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 09:22:48.603306 1 node.go:550] [1] Read index context timed out
zero_1 | I1214 09:22:48.603395 1 node.go:83] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 09:22:51.603600 1 node.go:550] [1] Read index context timed out
zero_1 | I1214 09:22:51.603695 1 node.go:83] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 09:22:54.603858 1 node.go:550] [1] Read index context timed out
zero_1 | I1214 09:22:54.603968 1 node.go:83] 1 no leader at term 3; dropping index reading msg