Fsdss-536 «2025»

If you want, I can:

(Note: supplying the actual feature description will yield a tailored plan.) FSDSS-536

Code Review – JIRA Ticket FSDSS‑536
Date: 2026‑04‑15
Reviewer: [Your Name]
Author: [Developer Name] If you want, I can:

| Type | Location / Link | |------|-----------------| | Log excerpt | tail -n 50 /var/log/fsdss/sync.log (see below) | | Screenshot | UI state | | Core dump / Thread dump | jstack <pid> > thread_dump.txt | | Metrics | Grafana panel showing CPU ~15 % and I/O wait spikes | (Note: supplying the actual feature description will yield

The synchronization should complete within Y minutes and all files should be replicated to the destination with status COMPLETED.

| 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). |

app.get('/api/v1/syncs', async (req, res) => 
  const userId = req.query.user_id;
  const rows = await db.any('SELECT id, status, last_checked, details FROM sync_jobs WHERE user_id = $1', [userId]);
  res.json( data: rows );
);