search

ArctosDB / dev

Current public release and project roadmap for development
https://arctos.database.museum
Apache License 2.0
0 stars 0 forks source link

further limit component loader reorder #53

Open dustymc opened 2 days ago

dustymc commented 2 days ago

Source

https://github.com/ArctosDB/dev/issues/51

Summary

That was possibly a bug, and it was possibly caused by multiple component loader reorder requests. Such updates have been limited to a single user per time period, but that is possibly not sufficient.

Possibly it would be better to remove user control altogether, there's clearly some sort of back-end/front-end/scheduler-API weirdness involved in allowing that to change, but priorities do change and I'm very hesitant to completely remove that ability unless forced.

https://dev.lucee.org/t/duplicate-scheduled-tasks/4086 - a very old, unsolved, non-replicable Lucee bug - describes behavior similar to that in the logs.

User Interface Changes

Component loader processing order updates will be allowed less frequently.

Data Structure Changes

None.

campmlc commented 2 days ago

Is there a way to allow the loader to automatically prioritize small, faster requests over larger, slow ones? The primary reason for needing to change the processing order is to expedite a small, urgently needed process, such as a bulkload for a loan that needs to go out that day, over a larger, slow request that will clog up the pipeline for hours or days.