Skip to content
This repository has been archived by the owner on May 29, 2020. It is now read-only.

Client re-dialing #3

Open
philhofer opened this issue Oct 1, 2014 · 3 comments
Open

Client re-dialing #3

philhofer opened this issue Oct 1, 2014 · 3 comments

Comments

@philhofer
Copy link
Member

The client should make a decent effort to re-dial a bad connection.

Perhaps a client should hold more than one connection? (Benchmarking should tell us whether or not that actually improves throughput.)

@philhofer
Copy link
Member Author

An update: at this point, there's no indication that using more than one network connection per client actually improves performance. But client should still re-dial.

@ttacon
Copy link
Collaborator

ttacon commented Jan 14, 2015

How about a different RedialClient that redials if the connection is lost, I could see certain users wanting to know when a connection is lost (the normal Client)?

@philhofer
Copy link
Member Author

Actually, now that I'm thinking about it, *ClusterClient with one remote address already does this, albeit with a little more overhead than is strictly necessary.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants