I wish. Unfortunately dgraph labs proper have reportedly not been able to reproduce this issue at all, and so no official direction on mitigation or repair has been given. The only saving grace is the design of dgraph allows a corrupt node without losing anything (assuming you are running the proper shardreplicas=3 setup), and node removal-readding takes only a minute without impact to the application.
But I run into this weekly, sometimes bi-weekly.