I think it make sense to have two different timeouts. The client timeout
clearly affects user's experience with the application. The timeout could be
due to number of factors not directly related to thrift connection. The
client timeout could trigger retry of operation on a different instance of
th
I've been scratching my head on this one for a day now and I'm hoping someone
can help clear it up.
The initial question was: does it make sense to have a configurable connection
timeout (for a client connecting to a cassandra server) separate from the
thrift socket timeout (which governs *all*
