Kinto / Kinto/kinto

[cliquet] Timestamp uniqueness by parent_id under heavy load

Open
#602 7 comments 0 reactions 0 assignees View on GitHub
bug enhancement protocol:v2 stale
Dominant language
Python
Stars
4.4k
Forks
437
Avg merge
1d 2h
Merged PRs (30d)
15

Description

Original : https://github.com/mozilla-services/cliquet/issues/25

summary: we can improve the timestamp creation for postgres to avoid collisions on very high-load. But the scenario to have that issue is unlikely. (same user hammerting our server)

http://stackoverflow.com/questions/34817760/how-to-generate-unique-timestamps-in-postgresql

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reading the linked original issue and the PostgreSQL timestamp-uniqueness discussion, then locate the timestamp creation path for records sharing a parent_id. Done means preventing timestamp collisions under concurrent high-load writes without changing normal behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres, python
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.