Upgrade to Cliquet 3 (fixes #345, fixes #fixes #369, fixes #421, fixes #424, fixes #433, fixes #434, fixes #461)

[leplatrem]

No description provided.

[almet]

"by to"

[almet]

That's a bunch of cool changes! Great.

[leplatrem]

I can't reproduce locally the timestamp constraint errors of the loadtest_simulation.

They seem to always occur on current bucket and collection creation, on the timestamps_pkey constraint.
This could be related to this code:
https://github.com/mozilla-services/cliquet/blob/3.0.0/cliquet/storage/postgresql/schema.sql#L154-L158
which inserts a timestamp when could not find one. Unicity can be violated with concurrent transactions.

PS: good news, load tests have approximately 15% more RPS from cliquet 2.15 to cliquet 3

BackendError: IntegrityError: (psycopg2.IntegrityError) duplicate key value violates unique constraint "timestamps_pkey"

DETAIL:  Key (parent_id, collection_id)=(/buckets/blocklist, collection) already exists.

CONTEXT:  SQL statement "INSERT INTO timestamps (parent_id, collection_id, last_modified)

      VALUES (uid, resource, ts)"

PL/pgSQL function collection_timestamp(character varying,character varying) line 14 at SQL statement

 [SQL: '\n        SELECT as_epoch(collection_timestamp(%(parent_id)s, %(collection_id)s))\n            AS last_modified;\n        '] [parameters: {'parent_id': u'/buckets/blocklist', 'collection_id': 'collection'}]; uid=None; errno=None; agent=python-requests/2.9.1; authn_type=None

CRITICAL:venusian:"PUT   /v1/buckets/blocklist/collections/addons" ? (? ms) (psycopg2.IntegrityError) duplicate key value violates unique constraint "timestamps_pkey"

DETAIL:  Key (parent_id, collection_id)=(/buckets/blocklist, collection) already exists.

[leplatrem]

Would you be willing to merge it like this and go forward ?

[Natim]

Yes I would :)

[almet]

Yes, I think we should merge this (but it needs to be rebased first)