New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Started
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Sign in to add a comment

Issue 904453: Ack bad archivist messages and send them back into the pubsub queue

Reported by, Nov 12 Project Member

Issue description

This is a shorterm mitigation to turn certain classes of bugs in the archivist from "catastrophic" to "annoying"

The idea is that, currently if a archival task is failing (eg due to bad permissions), it gets nacked and goes into the front of the pubsub queue.  This is bad because legitimate requests are in the back of the queue and may never get processed.  If the message is acked instead, it allows legitimate requests to get processed first before the bad request is processed again.

Comment 1 by, Nov 20

Status: Started (was: Available)

Comment 2 by, Dec 20

Project Member
The following revision refers to this bug:

commit 511486c4da79cfe73784dee7e826bef5c3cdbb65
Author: Ryan Tseng <>
Date: Thu Dec 20 19:50:33 2018

[logdog] Add RescheduleArchiveTask endpoint

This adds a new RescheduleArchiveTask coordinator endpoint
to re-task archive tasks.

ArchiveDispatchTask was never used, so the name was repurposed.

Changed assumption in appengine/coordinator/archival.go that
a log stream archival can get tasked multiple times.

Bug: 904453
Change-Id: I4832731de224d7a74d6a4341bf27f9d2ebb8aff2
Commit-Queue: Ryan Tseng <>
Reviewed-by: Quinten Yearsley <>


Sign in to add a comment