Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
There was an edge case in the dnode header parsing where we were dropping a dnode message from a peer. This happens when the dnode header arrives in one packet and rest of the message arrives in another packet. This fix will further reduce inconsistencies in the database. Yay!!
- Loading branch information
ce9b818
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense when the packet ends there, we need to get more data and re-parse from the right position instead of losing track. Yeah, we missed this case.