[OP-190] Failsoft capacity when too many nodes are down to get the QUORUM Created: 18/Mar/15  Updated: 19/May/15  Resolved: 18/May/15

Status: Closed
Project: Opush
Component/s: None
Affects Version/s: None
Fix Version/s: 3.1.0

Type: Improvement Priority: Normal
Reporter: Thomas HILAIRE Assignee: Thomas HILAIRE
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to OP-137 Customize RetryPolicy to avoid Cassan... Closed
Rank: 6805

 Description   

see OP-137



 Comments   
Comment by Thomas HILAIRE [ 06/May/15 ]

QA:
OK tested with a centos 6.6 and three Cassandra nodes:
When cassandra.retry-policy is set to RETRY_OR_CL_DOWNGRADE

  • it retries on write timeout until that 'cassandra.max-retries" is reached WITHOUT downgrading the CL
  • it retries on read timeout until that 'cassandra.max-retries" is reached WITHOUT downgrading the CL
  • it retries on unavailable until that 'cassandra.max-retries" is reached BY downgrading the CL

Note: a type has been found so this ticket goes back in REVIEW but we can avoid to do the QA again

Comment by Thomas HILAIRE [ 06/May/15 ]

reopen due of a typo

Comment by Jenkins Continuous Integration Server [ 18/May/15 ]

FAILURE: Integrated in opush-master #229
OP-190 Fix a typo (thilaire: 096184e5527aa860a53725be4495ff74ab3e4488)

  • push-dao-cassandra/src/main/java/org/obm/push/cassandra/RetryOrCLDowngradeRetryPolicy.java
Comment by Stephane COLSON [ 19/May/15 ]

OK closed already tested by Thomas HILAIRE, not retested for this typo in a log...

Generated at Sun Aug 18 04:49:39 CEST 2019 using JIRA 6.1.1#6155-sha1:7188aeec9a6b57d61ea04c52f235f15f55c105e2.