Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/10/2013 11:11 PM, Clint Byrum wrote: Excerpts from Adam Young's message of 2013-07-10 19:17:24 -0700: On 07/09/2013 07:33 PM, Jay Pipes wrote: On 07/08/2013 05:18 PM, Sean Dague wrote: On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

Excerpts from Adam Young's message of 2013-07-10 19:17:24 -0700: > On 07/09/2013 07:33 PM, Jay Pipes wrote: > > On 07/08/2013 05:18 PM, Sean Dague wrote: > >> On 07/01/2013 01:35 PM, Clint Byrum wrote: > >>> The way the new keystone-manage command "token_flush" works right now > >>> is quite broken

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

Excerpts from Adam Young's message of 2013-07-10 19:14:45 -0700: > On 07/09/2013 09:51 PM, Robert Collins wrote: > > PostgreSQL doesn't do gap locks, but instead you have to deal with > > http://wiki.postgresql.org/wiki/SSI : the transaction that is deleting > > 1M rows, for instance, will have a

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/09/2013 07:33 PM, Jay Pipes wrote: On 07/08/2013 05:18 PM, Sean Dague wrote: On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and InnoDB's gap locking behavior: https://bugs.launchpad.net/1188378 Pr

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/09/2013 09:51 PM, Robert Collins wrote: On 10 July 2013 11:00, Jay Pipes > wrote: > I am not up to speed on"InnoDB's gap locking behavior" but it is not something I would expect to be a problem in Postgresql. InnoDB and PostgreSQL behave i

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

far be it from me to ask. but isn't this something that should be addressed in oslo common db, and made configurable as an class definition or method argument? -matt On Tue, Jul 9, 2013 at 9:27 AM, Monty Taylor wrote: > > > On 07/09/2013 11:21 AM, Clint Byrum wrote: > > >>> You may want to up

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 10 July 2013 11:00, Jay Pipes wrote: > > I am not up to speed on"InnoDB's gap locking behavior" but it is > >> not something I would expect to be a problem in Postgresql. >> > > InnoDB and PostgreSQL behave in very different manners regarding locking > and transaction isolation, even though

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/08/2013 05:18 PM, Sean Dague wrote: On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and InnoDB's gap locking behavior: https://bugs.launchpad.net/1188378 Presumably other SQL databases like PostgreS

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/08/2013 08:32 PM, Adam Young wrote: On 07/08/2013 04:35 PM, Clint Byrum wrote: Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700: On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and In

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/09/2013 11:21 AM, Clint Byrum wrote: Yes please! Is this something that is in development, or at least recorded in a bug that someone like me can grab? I would love for that to be the default behavior. https://blueprints.launchpad.net/keystone/+spec/no-tokens-in-db __

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/09/2013 11:21 AM, Clint Byrum wrote: >>> You may want to update your snark! MySQL has its warts which are pretty >>> easy to take shots at, but it has been a "real" ACID compliant database >>> for well over a decade. >> My snark is more recently generated than that. There are plenty of >

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On Tuesday, July 9, 2013, Clint Byrum wrote: > Excerpts from Adam Young's message of 2013-07-09 06:19:19 -0700: > > On 07/08/2013 11:06 PM, Clint Byrum wrote: > > > Excerpts from Adam Young's message of 2013-07-08 17:32:30 -0700: > > >> On 07/08/2013 04:35 PM, Clint Byrum wrote: > > >>> Excerpts f

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

Excerpts from Adam Young's message of 2013-07-09 06:19:19 -0700: > On 07/08/2013 11:06 PM, Clint Byrum wrote: > > Excerpts from Adam Young's message of 2013-07-08 17:32:30 -0700: > >> On 07/08/2013 04:35 PM, Clint Byrum wrote: > >>> Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700: >

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/08/2013 11:06 PM, Clint Byrum wrote: Excerpts from Adam Young's message of 2013-07-08 17:32:30 -0700: On 07/08/2013 04:35 PM, Clint Byrum wrote: Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700: On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage co

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On Jul 8, 2013, at 20:34, Jamie Lennox wrote: > On Mon, 2013-07-08 at 21:55 -0400, Adam Young wrote: >> >> Tokens are, for the most part, immutable. Once they are written, they >> don't change except if they get revoked. This is a fairly rare >> occurance, but it does happen. >> >> Deleting

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On Mon, 2013-07-08 at 21:55 -0400, Adam Young wrote: > > Tokens are, for the most part, immutable. Once they are written, they > don't change except if they get revoked. This is a fairly rare > occurance, but it does happen. > > Deleting tokens based on age should be fairly straight forward, an

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

Excerpts from Adam Young's message of 2013-07-08 17:32:30 -0700: > On 07/08/2013 04:35 PM, Clint Byrum wrote: > > Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700: > >> On 07/01/2013 01:35 PM, Clint Byrum wrote: > >>> The way the new keystone-manage command "token_flush" works right

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

Tokens are, for the most part, immutable. Once they are written, they don't change except if they get revoked. This is a fairly rare occurance, but it does happen. Deleting tokens based on age should be fairly straight forward, and locks should not need to be held for a significant amount

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 9 July 2013 12:32, Adam Young wrote: > * I am asking about MySQL.. presumably a "real" database. >> > I have to admit I am a bit of a Postgresql Bigot. I don't really consider > MySQL a real database, althought it has improved a lot over the years. I > am not up to speed on"InnoDB's gap loc

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/08/2013 04:35 PM, Clint Byrum wrote: Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700: On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and InnoDB's gap locking behavior: https://bugs.

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and InnoDB's gap locking behavior: https://bugs.launchpad.net/1188378 Presumably other SQL databases like PostgreSQL will have similar problems with doing ma

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

Excerpts from Adam Young's message of 2013-07-08 13:18:55 -0700: > On 07/01/2013 01:35 PM, Clint Byrum wrote: > > The way the new keystone-manage command "token_flush" works right now > > is quite broken by MySQL and InnoDB's gap locking behavior: > > > > https://bugs.launchpad.net/1188378 > > > >

Re: [openstack-dev] [Keystone] Best way to do something MySQL-specific?

On 07/01/2013 01:35 PM, Clint Byrum wrote: The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and InnoDB's gap locking behavior: https://bugs.launchpad.net/1188378 Presumably other SQL databases like PostgreSQL will have similar problems with doing ma

[openstack-dev] [Keystone] Best way to do something MySQL-specific?

The way the new keystone-manage command "token_flush" works right now is quite broken by MySQL and InnoDB's gap locking behavior: https://bugs.launchpad.net/1188378 Presumably other SQL databases like PostgreSQL will have similar problems with doing massive deletes, but I am less familiar with th