Make language pack exporter use slave store

Bug #286236 reported by Jeroen T. Vermeulen
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Jeroen T. Vermeulen

Bug Description

The language pack exporter is practically a read-only process, with just a bit of writing at the end (and most of that is to the Librarian).

Thus it can make more effective use of replication if it uses the slave store.

Changed in rosetta:
importance: Undecided → High
status: New → Triaged
Changed in rosetta:
assignee: nobody → jtv
milestone: none → 2.1.11
status: Triaged → In Progress
Changed in rosetta:
importance: High → Medium
Changed in rosetta:
milestone: 2.1.11 → 2.1.12
Changed in rosetta:
milestone: 2.1.12 → 2.2.1
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Lowering priority on this one. At the moment the slave store is more heavily loaded than the master, so moving the script over wouldn't help us much right now.

Changed in rosetta:
importance: Medium → Low
Changed in rosetta:
milestone: 2.2.1 → 2.2.2
Changed in rosetta:
milestone: 2.2.2 → none
Changed in rosetta:
milestone: none → 2.2.7
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Fixed in devel 8775

Changed in rosetta:
status: In Progress → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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