In D7 it was possible to use a custom lock handler through $conf['lock_inc']. This feature is of course gone, but how do you instruct Drupal to use another backend than DatabaseLockBackend? Do we need a LockFactory::get() method like we have with Cache? Or is there another way to do it?

CommentFileSizeAuthor
#1 1897806-1-lock-factory.patch2.7 KBgielfeldt

Comments

gielfeldt’s picture

gielfeldt commented
StatusFileSize
new 1897806-1-lock-factory.patch2.7 KB

Submitting a rudimentary patch, in case we need a LockFactory::get().

gielfeldt’s picture

gielfeldt commented
Status: Active » Needs review
gielfeldt’s picture

gielfeldt commented
Category: support » bug

This is actually a regression I guess.

alansaviolobo queued 1: 1897806-1-lock-factory.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 1: 1897806-1-lock-factory.patch, failed testing.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

adammalone’s picture

adammalone
Primary language English
Location San Francisco
commented
Issue summary: View changes
Status: Needs work » Closed (works as designed)

This can be defined be registering the lock in the services.yml in sites/default.

Using the memcache lock example:

  services:
    lock:
      class: Drupal\Core\Lock\LockBackendInterface
      factory: memcache.lock.factory:get