[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2017-03-27 Thread jcrespo
jcrespo added a comment. It just occurred to me an extra reason to avoid using a db master- master failover is a relative frequent operation: it will happen every time the master mysql is upgraded, or when there is a datacenter failover (2 of those will happen on April/May)- probably there wasn't a

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2017-03-25 Thread gerritbot
gerritbot added a comment. Change 344750 merged by jenkins-bot: [mediawiki/extensions/Wikibase@master] Document dispatchingLockManager option in $wgWBRepoSettings https://gerrit.wikimedia.org/r/344750TASK DETAILhttps://phabricator.wikimedia.org/T151993EMAIL PREFERENCEShttps://phabricator.wikimedia

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2017-03-07 Thread gerritbot
gerritbot added a comment. Change 325640 merged by jenkins-bot: [mediawiki/extensions/Wikibase] Add LockManagerSqlChangeDispatchCoordinator https://gerrit.wikimedia.org/r/325640TASK DETAILhttps://phabricator.wikimedia.org/T151993EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/ema

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2016-12-07 Thread aaron
aaron added a comment. If the owner fatals, the lock will have to expire (the TTL depends on the LockManager instance config and/or whether the context is CLI or web).TASK DETAILhttps://phabricator.wikimedia.org/T151993EMAIL PREFERENCEShttps://phabricator.wikimedia.org/settings/panel/emailpreferenc

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2016-12-07 Thread daniel
daniel added a comment. Without looking at the code, it seems we should be able to do without Database::lockIsFree. It's nice to do a check first to avoid a more expensive attempt to acquire a lock if we already know that that is likely to fail, but in the end, all we need is an atomic way to try t

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2016-12-07 Thread aaron
aaron added a comment. There is no analogous method. Maybe a non-blocking engageClientLock() call can replace the isClientLockUsed() call? Seems like chd_lock is used to determine whether to do a non-blocking check first before a blocking acquisition (which could race anyway, which I guess just eff

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2016-12-07 Thread Ladsgroup
Ladsgroup added a comment. @aaron: Hey, I'm working on this but it seems that RedisLockManager (and LockManagers in general) doesn't have lock lookup or I couldn't find it. Can you clarify if lock managers have something equivalent to Database::lockIsFree ?TASK DETAILhttps://phabricator.wikimedia.o

[Wikidata-bugs] [Maniphest] [Commented On] T151993: Implement ChangeDispatchCoordinator based on RedisLockManager

2016-12-06 Thread gerritbot
gerritbot added a comment. Change 325640 had a related patch set uploaded (by Ladsgroup): [very WIP] [Draft] [DNM] [I can't emphasize enough] Add RedisLockSqlChangeDispatchCoordinator https://gerrit.wikimedia.org/r/325640TASK DETAILhttps://phabricator.wikimedia.org/T151993EMAIL PREFERENCEShttps://