[SERVER-50742] Add a way for Instance::run() in POS to know whether it's called during stepup rebuildInstances or by Instance::getOrCreate(). Created: 03/Sep/20 Updated: 06/Dec/22 Resolved: 08/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||
| Participants: | |||||||||||||
| Comments |
| Comment by Spencer Brody (Inactive) [ 08/Sep/20 ] |
|
Discussed this with the PrimaryOnlyService design crew and we decided not to change this for now. The idea behind the PrimaryOnlyService design was for each of the implementations to be state machines, and so we're comfortable forcing implementations to adhere to that model (including an initial state that can be used to determine whether or not the state document needs to be persisted as the first step of run()) for now. If this causes pain to multiple implementations then we are open to revisiting in the future. |