Plan: logs nodes that store all synced logs (D263, planning only) #202

New issue

Open

opened 2026-10-13 06:38:33 +00:00 by kayg · 0 comments

kayg commented

2026-10-13 06:38:33 +00:00

Owner

Planning only. Facts to gather before the grill: bandwidth and disk for a logs node serving N machines of each kind (use research/log-volume numbers, compressed), sync transport over the mesh, behaviour while the logs node is down (buffer at source within the 5% cap), search routing (query the logs node instead of fanning out), multiple logs nodes, redaction staying at the source, access as an ordinary rule.

Owner, 2026-10-13: "mark a node as a 'logs' node that would mean we sync all the logs there, which specifically means, we have that node to store all the logs! let's plan around this (don't need to build anything yet, just plan plan plan)". Recorded in D263; amends D260's hybrid placement (full history on each machine) once grilled. Planning only. Facts to gather before the grill: bandwidth and disk for a logs node serving N machines of each kind (use research/log-volume numbers, compressed), sync transport over the mesh, behaviour while the logs node is down (buffer at source within the 5% cap), search routing (query the logs node instead of fanning out), multiple logs nodes, redaction staying at the source, access as an ordinary rule.

~~kayg referenced this issue 2026-10-28 17:53:56 +00:00~~

Orchestrator handover 2026-10-28: moving to a new machine #254

kayg referenced this issue

2026-10-28 18:00:45 +00:00

Orchestrator handover 2026-10-28: moving to a new machine #254

No labels

launch-qa

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kayg/infraternal#202

No description provided.

Rows
Columns