(Add as many steps as needed. If the bug is intermittent, note the frequency.)
| Concept | Description | |---------|-------------| | Topic Model | Hierarchical (Namespace → Topic → Partition). | | Retention | Configurable time‑based (e.g., 7 days) or size‑based (e.g., 1 TB). | | Exactly‑once | Transactional writes via two‑phase commit between LogStore and StreamEngine. | | Back‑pressure | gRPC flow‑control + token‑bucket per consumer group. | | Replay | Log‑based replay using offsets stored in MetaStore; supports snapshot‑based re‑processing (e.g., for ML feature pipelines). | FSDSS-536
Provide a fuller context for the issue.
FSDSS-536 is assumed to be a feature/task ID requiring design, implementation, testing, and deployment. This guide prescribes a complete, prescriptive plan covering requirements, architecture, implementation steps, testing, rollout, and monitoring. (Add as many steps as needed
useEffect(() =>
let mounted = true;
const fetchStatus = async () =>
const r = await fetch(`/api/v1/syncs?user_id=$userId`);
const json = await r.json();
if (mounted) setStatus(json.data);
;
fetchStatus();
const id = setInterval(fetchStatus, 5000);
return () => mounted = false; clearInterval(id); ;
, [userId]);