Not sure what’s causing it but getting these errors on repeat:
server_1 | W1214 15:50:58.446481 1 server.go:230] Error while retrieving timestamps: rpc error: code = Unknown desc = Assigning IDs is only allowed on leader. with delay: 10s. Will retry…
zero_1 | W1214 15:51:00.906721 1 node.go:551] [1] Read index context timed out
zero_1 | I1214 15:51:00.906815 1 node.go:84] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 15:51:03.907158 1 node.go:551] [1] Read index context timed out
zero_1 | I1214 15:51:03.907259 1 node.go:84] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 15:51:06.907399 1 node.go:551] [1] Read index context timed out
zero_1 | I1214 15:51:06.907546 1 node.go:84] 1 no leader at term 3; dropping index reading msg
zero_1 | E1214 15:51:08.447363 1 oracle.go:479] Got error: Assigning IDs is only allowed on leader. while leasing timestamps: val:1
server_1 | W1214 15:51:08.447821 1 server.go:230] Error while retrieving timestamps: rpc error: code = Unknown desc = Assigning IDs is only allowed on leader. with delay: 10s. Will retry…
zero_1 | W1214 15:51:09.907622 1 node.go:551] [1] Read index context timed out
zero_1 | I1214 15:51:09.907699 1 node.go:84] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 15:51:12.907861 1 node.go:551] [1] Read index context timed out
zero_1 | I1214 15:51:12.907962 1 node.go:84] 1 no leader at term 3; dropping index reading msg
zero_1 | W1214 15:51:15.908142 1 node.go:551] [1] Read index context timed out
zero_1 | I1214 15:51:15.908258 1 node.go:84] 1 no leader at term 3; dropping index reading msg
zero_1 | E1214 15:51:18.448849 1 oracle.go:479] Got error: Assigning IDs is only allowed on leader. while leasing timestamps: val:1
These errors showed up after restarting the docker containers (which I had to do as a result of another error ("ResourceExhausted desc = grpc: received message larger than max (XXXXXXX vs 4194304)"}" that occurred while querying and loading new (little) data into Dgraph)