Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 297347

Protect against concurrent config transformations

$
0
0

Problem/Motivation

The config transformation uses a database table to back the transformed storage for both import and export. The process then assumes the transformed storage is safe to be used. This does not work well when a concurrent request kicks off another transformation that changes the configuration in that database table. This is in particular a problem when importing the config because a concurrent request to the synchronisation form triggers a the database table to be changed from which the config importer imports from.

Proposed resolution

Use the locking system to prevent concurrent requests from transforming at the same time.
Consider the transformation during the config import never to change.

Remaining tasks

write patch, review, commit.

User interface changes

none

API changes

none

Data model changes

none

Release notes snippet

n/a


Viewing all articles
Browse latest Browse all 297347

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>