When acquiring a database lock, Storage API assumes that the database name can be found in global $databases['default']['default']['database']
. I would venture to guess that this assumption works for the majority of configurations. This assumption is not valid, however, when the installation uses a database driver such as AutoSlave for Master/Slave database read/write splitting.
It's more of an annoyance than anything, since it fills up my logs. It also means that, in the unlikely event that multiple drupal sites share a database, but use AutoSlave (or a similar configuration), the database locks will not be properly namespaced.
Comments
Comment #2
Perignon CreditAttribution: Perignon commentedFeel free to patch to support this functionality, but this is not a bug for Storage API. I consider this a feature request since Storage API works with the default installation of Drupal.