-
Notifications
You must be signed in to change notification settings - Fork 1
/
asagi_archive_auto_failover_notes.txt
62 lines (25 loc) · 1.29 KB
/
asagi_archive_auto_failover_notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
asagi_archive_auto_failover_notes.txt
Notes on auto-failover script.
===== PLAN =====
Periodically test if the archive is working.
If it is not working, trigger some arbitary code to trigger failover.
Failover refers to automatic reconfiguration of the host from its main job to active archival.
+++ Questions about how to do it +++
How do we differentiate between 4chan breaking and the archive breaking?
Check 4chan's API for updates?
Do we need to store more information than the highest post_num and image_num?
What triggers should be used to detect failure?
Lack of new posts?
Highest seen post_num not increasing in a given time period?
Error pages/codes accessing archive.
Exceptions, use pokemon-style exception handling to trigger failover on bugs.
What are sensible thresholds?
Do these change based on the board being observed?
Use most active board in the archive as the failure-canary?
Should more than one board be tested? How many boards need to fail before triggering failover code?
What sort of response should occur on failure?
Leave this to the admin running the script to decide, simply provide ability to run arbitary shell commands.
===== Basic high-level pseudocode =====
# Load archive API JSON
===== USAGE =====
TODO