Details
Medium Description
When DistributedEntityOwnershipService dispatches a request to EntityOwnershipShard, it does not report errors (such as AskTimeoutExceptions) except on debug level. This means the application thinks it has a candidate registered, but in fact it is not propagated to backend. At the very least such failures should report an error to bring attention to the problem, but really the frontend should retry forwarding the registration (and unregistration) events.
Furthermore, backend reports a success as soon as the request is enqueued to BatchedModifications - which does not guarantee the candidate has been propagated to all participants.
Attachments
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 82990,3 | Raise EOS unsuccessful request reporting to error | master | controller | Status: MERGED | +2 | +1 |
| 83059,1 | Raise EOS unsuccessful request reporting to error | stable/neon | controller | Status: MERGED | +2 | +1 |
| 93089,2 | DistributedEntityOwnershipService may silently lose registrations | master | controller | Status: ABANDONED | 0 | -1 |
| 93094,1 | DistributedEntityOwnershipService may silently lose registrations | master | mdsal | Status: ABANDONED | 0 | -1 |
| 93227,2 | DistributedEntityOwnershipService may silently lose registrations | master | mdsal | Status: ABANDONED | 0 | -1 |
| 93229,1 | DistributedEntityOwnershipService may silently lose registrations retry | master | mdsal | Status: ABANDONED | -2 | -1 |
| 93497,11 | DistributedEntityOwnershipService may silently lose registrations | master | controller | Status: ABANDONED | 0 | +1 |
| 93499,1 | DistributedEntityOwnershipService may silently lose registrations | master | controller | Status: ABANDONED | -1 | -1 |