Hi @JatinDevDG
It seems like that some mutations are the root cause for bringing the database in a state where certain subsequent queries are freezing dgraph.
I have the same problem on latest master. I’ll try to dig deeper and come up with a list of mutations and queries to reproduce this.
Edit: Has dgraph/badger some upper limit for string storage? I discovered that I accidentally saved a 262279 Byte string to some field and after that the database seems to be unstable. If there is some upper/unsafe limit, I think it would be good practice that the GraphQL interface throws an error in that case.
Edit 2: The size of the string does not seem to be the issue here as the the bug occurs also after I fixed it on my side. Will investigate further.