Details
-
Improvement
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
None
-
1
-
SDK50, SDK52
Description
In MB-57384 it was found that if a memcached connection is dropped in gocbcore then SET_WITH_META operations will not be retried. This behaviour is not ideal for cbbackupmgr where we would like to retry when the connection is dropped.
Charles Dixon asked me to raise this ticket on this slack thread. A few ideas were suggested including:
- using the user provided retrier to decide whether to retry
- making SET_WITH_META idempotent
Note that for cbbackupmgr we would also like to retry SETs.
Attachments
Issue Links
- relates to
-
MB-57384 [CBM] [Restore] Suspected lack of retries in restore when there is a connection failure
- Open
-
GOCBC-1585 Expose non-idempotent requests that fail with EOF to retry orchestrator
- Closed
For Gerrit Dashboard: GOCBC-1433 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
202556,2 | GOCBC-1433: Add support for considering Set(Meta) as idempotent | master | gocbcore | Status: ABANDONED | -1 | 0 |