GoshawkDB: A distributed, transactional, fault-tolerant object store
&gt; The trade-off is that in the case of failure (node failure or network partitions), operations may block until the failures have been resolved.<p>Curious how this works at scale.  For example if a node is down and N requests start blocking, is there an upper bound to N?  What happens when this is reached? Does N map to a goroutine? A file descriptor? Is there timeouts?<p>Seems like possibly a node going down essentially means the entire show going down if requests are filling up and not being resolved, you would think there may be a tipping point in which other requests may not be able to be served as all resources are blocked.<p>Possibly there is just a sane timeout and these requests also just fail, leaving the client to know something is amiss?