[SERVER-53018] Make PrimaryOnlyService remove an instance from its in-memory map if the instance fails to insert its state doc Created: 22/Nov/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Service Arch
Sprint: Service Arch 2021-02-22, Service Arch 2021-03-08, Service Arch 2021-03-22, Service Arch 2021-04-05, Service Arch 2021-04-19, Service Arch 2021-05-17, Service Arch 2021-05-31
Participants:

 Description   

An instance can fail to insert its state doc because the instance conflicts with a running instance:

In both cases, we have made the instance fail with ConflictingOperationInProgress.

For now, we have made the command that creates the instance handle removing the instance from the in-memory map in this case, e.g. here.

It would be better for the POS machinery to handle this. There are two options:

  • Make the instance remove itself from its service if the instance fails to insert its state doc. This requires instances to have a pointer to their service.
  • Make the service remove the instance if the instance fails to insert its state doc. This requires services to monitor what their instances complete with.

suganthi.mani and I think the second option is cleaner.


Generated at Thu Feb 08 05:29:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.