FoundationDB

Connection management among fdb processes


#1

Are there knobs to tune how many connections are created among the fdb processes ? So far it seems to me that there is only one connection created from one ‘peer’ to another.

If there is none, under some extreme circumstances when a single connection is saturated, e.g. a huge amount of data being transferred, what are the recommended steps to deal with it ? When a connection is being used to transfer a large amount of data, other send requests have to wait for this particular connection as I understand it, which increases the overall latency.

Thanks