Unify connection retry behavior across drivers

Bug #1520648 reported by Federico Ceratto on 2015-11-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tooz
Wishlist
Unassigned

Bug Description

Some Tooz drivers can handle configuration options for connection/command retry.
The interface is not consistent across drivers, e.g. Kazoo can handle a keyword argument connection_retry=KazooRetry()

Ideally, the default values should be the safest (e.g. retry connections forever)

Ben Nemec (bnemec) wrote :

Unfortunately the kazoo case is directly exposing the underlying driver interface. I don't know that that's a pattern we want to repeat, but some sort of common retry configuration does seem reasonable.

Changed in python-tooz:
status: New → Confirmed
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers