I have used several shared web hosting packages over the years, however, more recently I have encountered issues that have me questioning the purpose of delays in configuration changes.
The web host in question is 1&1, which applies config changes with a delay.
The question // What is the benefit of delaying configuration changes?
Update additional question // Why would some changes take the specified time (e.g. 10 minutes), and sometimes several hours?
The story // The most recent incident was caused using the 1&1's WebsiteBuilder by a tech to create a temporary page. After this, the finalized site (html/js/css/etc.) was placed on the server through FTP. The following events occurred after:
- Removed the domain from the selection was applied immediately (i.e. selected -none-).
- Changed the domain destination folder, which were delayed a few minutes.
- Skip a few hours
- Another tech attempted some changes through the WebsiteBuilder.
- This change forced the Control Panel to copy the existing site files to a different folder.
- The change was applied immediately.
- My mistake here was removing the newly created folder, and reapplying the domain destination folder.
- This change did not take effect immediately; in fact, it took several hours.
- The last tech kept attempting to fix the site by making changes on the Control Panel.
Due to the configuration effect delays on step 4, the tech kept making changes (presumably adding more changes to the configuration queue, I'm guessing).
Finally, all of these changes threw the site into a cycle of failed access, directory listing denied, 404's, etc.