MOP Time-Outs

[KKruszynska]

On some days/times MOP time outs and doesn't allow Users to load the Target Details page. It may be occurring at the same time, or near times when run_TAP, fit_needed_PSPL, or other resource-consuming management commands are running. This is inconvinient if the User wants to only check the status of the event.

[rachel3834]

I agree, but there are sound underlying reasons for this.

MOP's target detail page offers the user the option to edit target parameters. MOP has several background processes running at intervals which also edit the target parameters. If a user accesses the target edit options at the same time as one of those processes, we have a potential data integrity issue.

So at the moment, MOP's background processes are designed in such a way as to lock access to a target if it is one of those which a management command is currently operating on. Once this process finishes, this lock is released, and the user can access the target detail page again.

This is a design choice, and alternative options could be imagined. For example it might be possible to grey-out the edit option from a target detail page that is being operated on, but still allow the user to view the page. That is a subtly that I will need input on from the TOM Dev team, so I've created this TOM issue to start that conversation.