Description
Trying to achieve an exponential retry on NMVB of .5s, 1s, 2s, 4s, 4s...for a maximum of 30s.
The behaviour I observe is retries are performed after 0.5s, 0.5s, 0.5s....1s, 2s, 3.3s, 4s, 1.3s
Couchbase env built as follows:
|
|
CouchbaseEnvironment env = DefaultCouchbaseEnvironment.builder()
|
.maxRequestLifetime(60000) // cancel, not reschedule after 6 seconds
|
.kvTimeout(30000)
|
.retryDelay(Delay.exponential(TimeUnit.MILLISECONDS, 4000 , 500)) // .5, 1, 2, 4, 4....
|
.build();
|
See 2 attached files, retry behaviour that shows the time delta since previous packet and the source packet capture.
App behaviour is 2 perform a single 'set' operation against a vbucket which has been forced into replica state (to stimulate NMVB responses).
Attachments
Issue Links
- relates to
-
JVMCBC-293 ExponentialDelay overflow prevention can be made every 64 attempt, not 32
- Resolved
For Gerrit Dashboard: JVMCBC-291 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
59951,2 | JVMCBC-291: Improve ExponentialDelay documentation | master | couchbase-jvm-core | Status: MERGED | +2 | +1 |