Improve read/write splitting in CP by using replicas for element-indexes #9996
-
Since Craft CMS 3.5.11.1 all POST-requests in the CP explicitly disable any configured replicas from being used for any queries. I suspect this is done for data integrity, mainly because the save-functions store data and then immediately re-query it to fill the newly created model. However, a side-effect of this change is that all element-indexes exclusively use the writer to query their entries, because Would it be possible to disable replicas in a more fine-grained way? For example by only disabling them when a transaction is started (and re-enabling them after)? Or at least by explicitly allowing them for element-indexes? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Yeah good call. Just made that change for the next release (6b2531f). |
Beta Was this translation helpful? Give feedback.
Yeah good call. Just made that change for the next release (6b2531f).