I am experiencing some odd behavior in dgraph I think. It seems that no matter how many predicates are moved off of my first server in a 5 server cluster, the storage continues to grow on that first machine. It has multiple GB vs the other servers having a few hundred MB and it just seems to continue to grow, even after a predicate move. Running this in AWS. Is there an explanation for this, or something I could have done to cause it?
I’d like you to try out a new version of Dgraph. I’m planning to make a new release, but wanted to fix a couple more bugs before I do. Can you try building from master? I’ve pulled in the new Badger (1.5.0), which actually does a better job of reclaiming disk space.