Instead of having the Swift storage engine try to delete the empty chunk(s) synchronously, we simply queue them and have a worker come along after 30s to delete the empty chunks. This has a few key benefits: it is async (doesn't slow down the push code), helps deal with Swift's eventual consistency (less retries necessary) and is generic for other storage engines if/when they need this as well |
||
|---|---|---|
| .. | ||
| buildlogsarchiver | ||
| buildmanager | ||
| chunkcleanupworker | ||
| gcworker | ||
| globalpromstats | ||
| gunicorn_registry | ||
| gunicorn_secscan | ||
| gunicorn_verbs | ||
| gunicorn_web | ||
| jwtproxy | ||
| logrotateworker | ||
| nginx | ||
| notificationworker | ||
| prometheus-aggregator | ||
| queuecleanupworker | ||
| repositoryactioncounter | ||
| security_notification_worker | ||
| securityworker | ||
| service_key_worker | ||
| storagereplication | ||
| syslog-ng | ||