James Lovejoy

I am experiencing the same problem, was a resolution ever found to this?

Right now nodes use the external IP addresses of incoming peers to determine duplicate connections. I need to find a better method of detecting this.

http://hubris.media.mit.edu:8080/job/lit/lastSuccessfulBuild/artifact/

Tracker side: https://github.com/mit-dci/lit-tracker/commit/19b9417a258cc09b8f24d849c3cfc07d8e6ead37

Lit side: #200 (partial fix, read details)

Could there be a mechanism to apply replication back pressure in this case? The problem arises when there are enough nodes with sufficient bandwidth to the leader to reach commit...

Your rephrasing is correct. If it's best done outside NuRaft, how should one detect this condition? How does eBay do it? At present, it eventually leads to a `system_exit` on...

This might be cool to try: https://github.com/pingcap/tidb. Distributed, MySQL compatible and written in Go.

FYI the cointypes in the Lit params are supposed to be slip-0044 conforming.

I will be sending out an email shortly with details.