-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Description
What version of Dgraph are you using?
v1.2.2
Have you tried reproducing the issue with the latest release?
No
What is the hardware spec (RAM, OS)?
ubuntu 18.04 - CPU 4Core - 8GB Ram
Dgraph configurations
they registered as service in /etc/systemd/system/dg0.service and ...
for example
[Unit]
Description=my main dgraph zero server
After=network.target
StartLimitBurst=5
StartLimitIntervalSec=10
[Service]
Type=simple
Restart=always
RestartSec=1
User=root
ExecStart=/usr/local/bin/dgraph zero --config /db/z0/config.json
[Install]
WantedBy=multi-user.target
1 Zero [
{
"my": "localhost:5080",
"replicas": 3,
"wal": "/db/z0/zw"
}
]
3 Alphas [
{
"my": "localhost:7080",
"zero": "localhost:5080",
"lru_mb": 2048,
"postings": "/db/a0/p",
"wal": "/db/a0/w"
},{
"my": "localhost:7079",
"zero": "localhost:5080",
"lru_mb": 2048,
"postings": "/db/a1/p",
"wal": "/db/a1/w",
"port_offset": -1
},{
"my": "localhost:7078",
"zero": "localhost:5080",
"lru_mb": 2048,
"postings": "/db/a2/p",
"wal": "/db/a2/w",
"port_offset": -2
}
]
Expected behaviour and actual result.
current Dgraph index 0x16993f
I have a really edgy and complicated data including 2000 exams and ~50000 Questions and 200000 choices. each node has a ~owner . in other word there is a person who owned all those nodes.
there are some other things he owed too.
i've got nothing when runing:
{
data(func:uid(UserUid)) {
owner @filter(type(Exam)) {
uid
name
}
}
}
bot i have this one
{
data(func:uid(UserUid)) {
owner @filter(uid(ExamUid)) {
uid
name
}
}
}
and this one
{
data(func:type(Exam)) @filter(uid(ExamUid)) {
uid
}
}
It happened to me twice and i restore from backup each time.
i zipped the p&w and also export the database after crashing and zipped it to and here they are
the exported data is not complete. i mean don't contain the whole data. so i couldn't restore it.
export.zip
w.1.zip
the p.1.zip
Main Questions
fixing data is not important . the most important thing is that what should i do to prevent this happen again?
can Simultaneous requests cause this?