HardDesign: Distributed Task Scheduler (Cron at Scale)
A recurring task has been running every minute for a year. It has 525,600 execution log entries. How do you manage this data growth?
— Tests your understanding of this concept.
Answer Options
AKeep all entries forever
BPartition execution log by task_id and date, apply TTL-based deletion for old entries beyond retention period
CStore only the last 10 executions per task
DArchive to cold storage after 90 days
Want to see the correct answer?
Get the answer with a detailed explanation, plus practice 22+ more Design: Distributed Task Scheduler (Cron at Scale) questions with adaptive quizzes and timed interviews.
See the Answer on Guru Sishya →This question is from the Design: Distributed Task Scheduler (Cron at Scale) topic (System Design Cases).
More Design: Distributed Task Scheduler (Cron at Scale) Questions
Why is a single-server cron scheduler not suitable for production at scale?
HardWhat is the purpose of leader election in a distributed task scheduler?
HardA worker picks up a task and starts executing. The worker crashes mid-execution. What happens?
HardWhat is the 'thundering herd' problem in a task scheduler?
HardHow do you calculate the next_run_at for a cron expression after a successful execution?
Hard