When restarting my node, I get the following error in the logs continuously.
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
cluster0-node0_1 | 2018/08/28 02:25:18 node.go:400: WARN: A tick missed to fire. Node blocks too long!
This will be fixed in the next release. You can try out the release candidate v1.0.8-rc1 which has the fix. It’s available on Docker Hub as dgraph/dgraph:v1.0.8-rc1.