Launchpad itself

Librarian storage only supports LibraryFileContent IDs up to 0xffffffff

Bug #1923849 reported by Colin Watson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

LibraryFileContent.id is a bigint, so can go up to 2^63, but librarian-feed-swift has:

    if end_lfc_id is None:
        # Maximum id capable of being stored on the filesystem - ffffffff
        end_lfc_id = 0xffffffff

We're up to >78% of this limit, and we should really fix it before it becomes an emergency. We could extend the filesystem layout, but given Stuart's comment in https://bugs.launchpad.net/launchpad/+bug/1599001 I wonder whether it's approaching time to move to direct uploads to Swift instead.

Tags: librarian
Revision history for this message
Colin Watson (cjwatson) wrote :

In fact the limit is in lp.services.librarianserver.storage._relFileLocation, not only in librarian-feed-swift.

summary: - librarian-feed-swift only supports LibraryFileContent IDs up to
- 0xffffffff
+ Librarian storage only supports LibraryFileContent IDs up to 0xffffffff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.