@MichelDiz Seems to be a memory leak This issue mentions memory leak with alpha process however we are observing memory issues with zero.
I will be capturing the memory profile next time this issue occurs.
Current profile for the zero leader:
File: dgraph
Build ID: 9e4f0ee8831675148f4e65856b61a661f45ae84e
Type: inuse_space
Time: Sep 25, 2020 at 11:42pm (+0630)
Entering interactive mode (type "help" for commands, "o" for options)
(pprof) top 100
Showing nodes accounting for 648.37MB, 95.78% of 676.96MB total
Dropped 150 nodes (cum <= 3.38MB)
flat flat% sum% cum cum%
496.51MB 73.34% 73.34% 496.51MB 73.34% github.com/dgraph-io/dgraph/dgraph/cmd/zero.(*Oracle).commit
83.20MB 12.29% 85.63% 83.20MB 12.29% github.com/dgraph-io/badger/v2/skl.newArena (inline)
19.68MB 2.91% 88.54% 19.68MB 2.91% github.com/dgraph-io/badger/v2.(*Txn).modify
13MB 1.92% 90.46% 13MB 1.92% github.com/dgraph-io/dgo/v200/protos/api.(*TxnContext).Unmarshal
7MB 1.03% 91.50% 7MB 1.03% github.com/golang/snappy.NewReader (inline)
6.84MB 1.01% 92.51% 6.84MB 1.01% github.com/dgraph-io/dgraph/protos/pb.(*MembershipState).Marshal
4.98MB 0.74% 93.24% 4.98MB 0.74% reflect.mapassign
4.78MB 0.71% 93.95% 6.06MB 0.9% github.com/dgraph-io/badger/v2/y.(*WaterMark).process.func1
4.50MB 0.66% 94.61% 4.50MB 0.66% github.com/dgraph-io/badger/v2.(*DB).newTransaction
3.82MB 0.56% 95.18% 3.82MB 0.56% bytes.makeSlice
3.08MB 0.45% 95.63% 4.58MB 0.68% github.com/dgraph-io/badger/v2/pb.(*TableIndex).Unmarshal
0.98MB 0.14% 95.78% 9.98MB 1.47% github.com/gogo/protobuf/proto.mergeAny