yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1214720] Re: nova-manage db archive_deleted_rows fails if max_rows is a large number

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 04 Dec 2013 10:06:55 -0000
Reply-to: Bug 1214720 <1214720@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: nova
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1214720

Title:
  nova-manage db archive_deleted_rows fails if max_rows is a large
  number

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  The nova-manage db archive_deleted_rows fails if max_rows is a large number (I tried 1 million but a smaller value may also cause issues) because it receives an exception from the sqlalchemy and db layer regarding the number of parameters on the sql statement. 
  Database has a limite of maximum total length of host and indicator variables in SQL statement.  When I ran the archive, the table had 165822 rows in it and 18489 of those were not deleted. Therefore, 147333 rows had deleted=1. So get error from Database.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1214720/+subscriptions