content indexer: Determine the identifier ranges to use to schedule those
Closed, MigratedEdits Locked
Actions

Assigned To

Authored By

	ardumont
	Nov 21 2018, 3:25 PM

Description

Now that the implementation is done (deployed).
It's time to determine the appropriate ranges of ids to use.

Indexers:

Status	Assigned	Task
Migrated	gitlab-migration	T439 Indexers: compute (and maintain up-to-date) the filetype of all blobs
Migrated	gitlab-migration	T1385 Monitor output of metadata indexers
Migrated	gitlab-migration	T359 Indexers: batch content analyzer infrastructure
Migrated	gitlab-migration	T1227 General improvments of the indexer: Schedule indexer tasks
Migrated	gitlab-migration	T1374 content indexer: Determine the identifier ranges to use to schedule those
Migrated	gitlab-migration	T818 indexer DB should not use bytea for mimetype and encoding columns

ardumont triaged this task as Normal priority.Nov 21 2018, 3:25 PM

ardumont created this task.

As we got around ~5b contents for now, i went for 100000 ranges of ~50k each
It's been scheduled and content indexers are now consuming again.