iluminae
(Kenan Kessler)
September 17, 2021, 2:35pm
15
@Steve_Baroti it has been happening to us for several major versions, I do not think downgrading will let you escape from this. Especially since the only other supported major version is v20.11.x, and it’s support expires in 3 months.
Our cluster is an extremely heavy constant write scenario which I could imagine triggering some untested case by dgraph labs.
I have seen no mention from dgraph proper that any further effort has been put in to rectify this other than this attempt:
So, the cluster ran for a week in the cloud. We didn’t see this particular file does not exist issue. In fact, we just ran dgraph increment on the cluster, and it’s working fine.
But so many people make issues on here saying this is a consistent problem, I just cannot imagine it can be ignored indefinitely:
Under what circumstances is this known to happen?
2020-11-20T20:23:39.601Z WARN badgerbs v2@v2.2007.2/levels.go:1005 [Compactor: 0] LOG Compact FAILED with error: MANIFEST removes non-existing table 164: {elog:0xc01e3c24e0 thisLevel:0xc00202c900 nextLevel:0xc00202c960 top:[0xc01aa13960 0xc0339f82a0 0xc0229adc00 0xc035db8620 0xc029a7b6c0 0xc01fc7a000 0xc01a6380e0 0xc01c02dea0 0xc015708c40 0xc021cacee0 0xc0200810a0 0xc020c27dc0 0xc01ace7c00 0xc02b1cc620 0xc0385fad20] bot:[0xc038b4ba40 0xc032c0518…
There are 3 groups of 3 replicates, and one node has the following error, the query is no longer responding, causing a block.How should I deal with it?
W0716 14:37:32.990118 16346 log.go:36] [Compactor: 2] LOG Compact FAILED with error: MANIFEST removes non-existing table 15777621: {span:0xc00ceb4700 compactorId:2 t:{baseLevel:2 targetSz:[0 10485760 10485760 30006262 300062624 3000626242 30006262429] fileSz:[67108864 2097152 2097152 4194304 8388608 16777216 33554432]} p:{level:2 score:3.04369…
Report a Dgraph Bug
What version of Dgraph are you using?
Dgraph Version $ dgraph version
[Decoder]: Using assembly version of decoder
Page Size: 4096
Dgraph version : v20.11.3
Dgraph codename : tchalla-3
Dgraph SHA-256 : c3c1474369415e74b1a59ec7053cd1e585c9d55fe71243c72c48e313728d995a
Commit SHA-1 : 8d3eb766c
Commit timestamp : 2021-03-31 17:28:12 +0530
Branch : HEAD
Go version : go1.15.5
jemalloc enabled : true
For Dgraph official documentation, visit https://dgrap…
What version of Dgraph are you using?
Dgraph Version Dgraph version : v21.03.0
Dgraph codename : rocket
Dgraph SHA-256 : b4e4c77011e2938e9da197395dbce91d0c6ebb83d383b190f5b70201836a773f
Commit SHA-1 : a77bbe8ae
Commit timestamp : 2021-04-07 21:36:38 +0530
Branch : HEAD
Go version : go1.16.2
jemalloc enabled : true
What is the hardware spec (RAM, OS)?
32cpu 32GiB ram x12 alphas (4 groups, 3 replicas) (384cpu, 384GiB total) running it in k8s on GKE.
One of my nodes was s…
Relatively new to graph DBs, but have been using databases for a long time. We have a successful product running on SQL server using their graph extensions, but are assessing options for a more focused, portable graph-based back-end.
I managed to have completely broken my Dgraph install in about 30 minutes which is not encouraging. In particular the Ratan UI (both latest & dev) is throwing this error:
TypeError: Cannot read property 'find' of undefined
at a.value (Schema.js:343)
at Ha …
2 Likes