Retry on received == required_responses in DCRP.on_read_timeout

Fixes PYTHON-55
This commit is contained in:
Tyler Hobbs
2014-04-24 14:04:48 -05:00
parent 061991f2a3
commit c40a1aa79e
2 changed files with 3 additions and 1 deletions

View File

@@ -10,6 +10,8 @@ Bug Fixes
closing excess connections
* Avoid handling a node coming up multiple times due to a reconnection attempt
succeeding close to the same time that an UP notification is pushed
* Correctly retry when received_responses == required_responses in
DowngradingConsistencyRetryPolicy.on_read_timeout() (PYTHON-55)
1.1.1
=====

View File

@@ -772,7 +772,7 @@ class DowngradingConsistencyRetryPolicy(RetryPolicy):
received_responses, data_retrieved, retry_num):
if retry_num != 0:
return (self.RETHROW, None)
elif received_responses < required_responses:
elif received_responses <= required_responses:
return self._pick_consistency(received_responses)
elif not data_retrieved:
return (self.RETRY, consistency)