Fix Version/s: None
Currently there is one connection between any given host to another host in the cluster, the problem with this is:
1) This can become a bottleneck in some cases where the latencies are higher.
2) When a connection is dropped we also drop the queue and recreate a new one and hence the messages can be lost (Currently hints will take care of it and clients also can retry)
by making it a configurable option to configure the number of connections and also making the queue common to those connections the above 2 issues can be resolved.