yantrikdb-server 0.8.17

YantrikDB database server — multi-tenant cognitive memory with wire protocol, HTTP gateway, replication, auto-failover, and at-rest encryption
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
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
//! Oplog sync loop — followers continuously pull ops from the leader.
//!
//! For multi-DB clusters: on each tick, the follower
//! 1. Asks the leader for its database list
//! 2. Auto-creates any missing databases locally
//! 3. Pulls ops for each database independently with per-DB watermarks

use std::sync::Arc;
use std::time::Duration;

use futures::{SinkExt, StreamExt};
use tokio_util::sync::CancellationToken;

use yantrikdb_protocol::messages::*;
use yantrikdb_protocol::*;

use crate::cluster::client::{connect_and_handshake, CONNECT_TIMEOUT};
use crate::cluster::replication::{handle_oplog_apply, update_local_watermark};
use crate::cluster::ClusterContext;

const PULL_INTERVAL: Duration = Duration::from_millis(500);
const PULL_BATCH_SIZE: usize = 500;
const DB_LIST_REFRESH_INTERVAL: Duration = Duration::from_secs(10);
const CONTROL_SYNC_INTERVAL: Duration = Duration::from_secs(30);

/// Run the oplog sync loop. Followers and read replicas pull from the leader.
pub async fn run_sync_loop(ctx: Arc<ClusterContext>, cancel: CancellationToken) {
    let mut tick = tokio::time::interval(PULL_INTERVAL);
    tick.set_missed_tick_behavior(tokio::time::MissedTickBehavior::Skip);

    let mut last_db_list_refresh = tokio::time::Instant::now();
    let mut last_control_sync = tokio::time::Instant::now();

    tracing::info!(node_id = ctx.node_id(), "oplog sync loop started");

    loop {
        tokio::select! {
            _ = tick.tick() => {}
            _ = cancel.cancelled() => {
                tracing::info!(node_id = ctx.node_id(), "sync loop stopped");
                return;
            }
        }

        // Only followers and read replicas pull
        if !matches!(
            ctx.state.leader_role(),
            crate::cluster::LeaderRole::Follower | crate::cluster::LeaderRole::ReadOnly
        ) {
            continue;
        }

        // Find current leader's address
        let leader_id = match ctx.state.current_leader() {
            Some(id) => id,
            None => continue,
        };

        let leader_addr = match ctx
            .peers
            .snapshot()
            .into_iter()
            .find(|p| p.node_id == Some(leader_id))
        {
            Some(p) => p.addr,
            None => continue,
        };

        // Periodically refresh our database list from the leader
        if last_db_list_refresh.elapsed() >= DB_LIST_REFRESH_INTERVAL {
            if let Err(e) = sync_database_list(&ctx, &leader_addr).await {
                tracing::trace!(leader = %leader_addr, error = %e, "db list sync failed");
            }
            last_db_list_refresh = tokio::time::Instant::now();
        }

        // Periodically sync the control plane (databases + tokens) from
        // the leader via HTTP snapshot. This ensures tokens minted on the
        // leader are available on followers within ~30 seconds, fixing
        // the "token only works on one node" footgun. See task #83.
        if last_control_sync.elapsed() >= CONTROL_SYNC_INTERVAL {
            if let Err(e) = sync_control_plane(&ctx, &leader_addr).await {
                tracing::trace!(leader = %leader_addr, error = %e, "control plane sync failed");
            }
            last_control_sync = tokio::time::Instant::now();
        }

        // Pull ops for each known database
        let dbs = ctx.list_databases();
        for db_name in dbs {
            if let Err(e) = pull_db_from_leader(&ctx, &leader_addr, &db_name).await {
                tracing::trace!(
                    leader = %leader_addr,
                    db = %db_name,
                    error = %e,
                    "pull failed"
                );
            }
        }
    }
}

/// Pull the leader's control plane snapshot (databases + tokens) via
/// its HTTP admin endpoint and merge into our local control.db.
///
/// This is an additive merge: new databases and tokens from the leader
/// are inserted locally; local-only records are NOT deleted. The snapshot
/// is O(N) for N databases + tokens, which is fine for realistic control
/// plane sizes (< 1000).
async fn sync_control_plane(ctx: &Arc<ClusterContext>, leader_addr: &str) -> anyhow::Result<()> {
    let control = match ctx.control.as_ref() {
        Some(c) => c,
        None => return Ok(()), // no control db → single-node, nothing to sync
    };

    let secret = ctx
        .config
        .cluster_secret
        .as_deref()
        .ok_or_else(|| anyhow::anyhow!("no cluster_secret configured"))?;

    // leader_addr is the cluster RPC address (e.g. "192.168.4.141:7440").
    // The HTTP gateway runs on a different port. Derive it from the config
    // or fall back to the standard mapping: cluster_port → http_port.
    // Convention: if cluster port is 7440, HTTP is 7438.
    let http_addr = leader_addr.replace(":7440", ":7438");

    let url = format!("http://{}/v1/admin/control-snapshot", http_addr);

    // Use a simple HTTP client (reqwest would be ideal but we avoid adding
    // a new dependency; tokio::net::TcpStream + manual HTTP is too low-level.
    // Instead, shell out to curl which is available on all deployment targets).
    let output = tokio::process::Command::new("curl")
        .args([
            "-sS",
            "--max-time",
            "10",
            "-H",
            &format!("Authorization: Bearer {}", secret),
            &url,
        ])
        .output()
        .await?;

    if !output.status.success() {
        let stderr = String::from_utf8_lossy(&output.stderr);
        anyhow::bail!("control-snapshot HTTP failed: {}", stderr);
    }

    let snapshot: crate::control::ControlSnapshot = serde_json::from_slice(&output.stdout)?;

    let control = control.clone();
    let (dbs_added, tokens_added) = tokio::task::spawn_blocking(move || {
        let ctrl = control.lock();
        ctrl.import_snapshot(&snapshot)
    })
    .await??;

    if dbs_added > 0 || tokens_added > 0 {
        tracing::info!(
            dbs_added,
            tokens_added,
            "control plane sync: imported from leader"
        );
    }

    Ok(())
}

async fn sync_database_list(ctx: &Arc<ClusterContext>, leader_addr: &str) -> anyhow::Result<()> {
    let mut conn = connect_and_handshake(leader_addr, ctx).await?;
    let req = ClusterDatabaseListRequest {};
    let frame = make_frame(OpCode::ClusterDatabaseList, 0, &req)?;
    conn.send(frame).await?;

    let resp = tokio::time::timeout(CONNECT_TIMEOUT, conn.next())
        .await?
        .ok_or_else(|| anyhow::anyhow!("no db list response"))??;

    if resp.opcode != OpCode::ClusterDatabaseListResult {
        anyhow::bail!("unexpected opcode for db list: {:?}", resp.opcode);
    }

    let result: ClusterDatabaseListResponse = unpack(&resp.payload)?;

    // Auto-create any missing databases
    let local_dbs: std::collections::HashSet<String> = ctx.list_databases().into_iter().collect();
    for db in &result.databases {
        if !local_dbs.contains(db) {
            if let Err(e) = ctx.ensure_database(db) {
                tracing::warn!(database = %db, error = %e, "failed to auto-create database");
            }
        }
    }

    Ok(())
}

async fn pull_db_from_leader(
    ctx: &Arc<ClusterContext>,
    leader_addr: &str,
    db_name: &str,
) -> anyhow::Result<()> {
    let engine = ctx.engine_for(db_name)?;

    // Find our actor_id (used for exclusion to avoid pulling our own ops)
    let our_actor_id = {
        let db = engine.as_ref();
        db.actor_id().to_string()
    };

    // Per-database watermark key: "{leader_addr}:{db_name}"
    let watermark_key = format!("{}:{}", leader_addr, db_name);

    let watermark = crate::cluster::replication::get_local_watermark(&engine, &watermark_key)?;

    let (since_hlc, since_op_id) = match watermark {
        Some((hlc, op_id)) => (Some(hlc), Some(op_id)),
        None => (None, None),
    };

    let req = OplogPullRequest {
        database: db_name.to_string(),
        since_hlc,
        since_op_id,
        limit: PULL_BATCH_SIZE,
        exclude_actor: Some(our_actor_id),
    };

    let mut conn = connect_and_handshake(leader_addr, ctx).await?;
    let frame = make_frame(OpCode::OplogPull, 0, &req)?;
    conn.send(frame).await?;

    let resp = tokio::time::timeout(CONNECT_TIMEOUT, conn.next())
        .await?
        .ok_or_else(|| anyhow::anyhow!("no pull response"))??;

    if resp.opcode != OpCode::OplogPullResult {
        anyhow::bail!("unexpected opcode: {:?}", resp.opcode);
    }

    let result: OplogPullResult = unpack_frame(&resp)?;
    if result.ops.is_empty() {
        return Ok(());
    }

    let count = result.ops.len();
    let last_hlc = result.ops.last().map(|o| o.hlc.clone()).unwrap_or_default();
    let last_op_id = result
        .ops
        .last()
        .map(|o| o.op_id.clone())
        .unwrap_or_default();

    let apply = handle_oplog_apply(&engine, result.ops)?;

    // Update watermark only if we actually advanced
    if !last_op_id.is_empty() {
        update_local_watermark(&engine, &watermark_key, &last_hlc, &last_op_id)?;
    }

    // After applying replicated ops, the memories rows exist in SQLite but
    // their embedding columns are NULL (the oplog only carries embedding_hash,
    // not the full vector). Re-embed locally and populate both the column
    // and the in-memory HNSW index so recall() works on the follower.
    if apply.applied > 0 {
        if let Err(e) = backfill_embeddings(&engine).await {
            tracing::warn!(error = %e, "embedding backfill failed");
        }
    }

    if apply.applied > 0 {
        tracing::info!(
            leader = %leader_addr,
            db = %db_name,
            pulled = count,
            applied = apply.applied,
            skipped = apply.skipped,
            "oplog pull"
        );
    }

    Ok(())
}

/// After replicated record ops are materialized, the memories rows have
/// no embedding (the oplog doesn't carry vectors). Re-embed each missing
/// row using the local embedder and populate both the SQLite column and
/// the in-memory HNSW vector index — piecewise per-row.
///
/// v0.8.11 (RFC 022 §2): rewritten to use `db.insert_vector()` and
/// `db.encrypt_embedding_pub()` (newly-public engine APIs in yantrikdb
/// 0.6.5) instead of the previous full `db.rebuild_vec_index()` at the
/// end of every batch. The rebuild was O(N log N) on the entire memories
/// table per backfill cycle, which produced multi-hour follower-recall
/// lag on tenants with 1k+ memories. Per-row insert is O(log N) per
/// memory and means each backfilled row is recallable as soon as its
/// own insert completes — not at the end of the batch.
///
/// Encrypted-cluster follower recall now works for the first time. The
/// previous implementation skipped encrypted writes entirely (with a
/// TODO comment) because the engine's `encrypt_embedding` method was
/// `pub(crate)`. v0.8.11 exposes it as `encrypt_embedding_pub` so the
/// encryption path is symmetric with what `record()` does on the leader.
async fn backfill_embeddings(engine: &std::sync::Arc<yantrikdb::YantrikDB>) -> anyhow::Result<()> {
    use rusqlite::params;

    // Collect rids + texts that need embedding
    let pending: Vec<(String, String)> = {
        let db = engine.as_ref();
        if !db.has_embedder() {
            return Ok(()); // no embedder, nothing we can do
        }
        let conn = db.conn();
        let mut stmt = conn.prepare(
            "SELECT rid, text FROM memories \
             WHERE embedding IS NULL \
             AND consolidation_status IN ('active', 'consolidated') \
             LIMIT 500",
        )?;
        let rows: Vec<_> = stmt
            .query_map([], |row| {
                Ok((row.get::<_, String>(0)?, row.get::<_, String>(1)?))
            })?
            .collect::<Result<_, _>>()?;
        rows
    };

    if pending.is_empty() {
        return Ok(());
    }

    let count = pending.len();
    tracing::debug!(
        count,
        "backfilling embeddings for replicated memories (piecewise)"
    );

    let mut backfilled = 0usize;
    let mut errors = 0usize;

    for (rid, text) in &pending {
        // 1. Re-embed the text locally. `db.embed()` runs the engine's
        //    embedder; if no embedder is configured we already returned
        //    above.
        let embedding = {
            let db = engine.as_ref();
            match db.embed(text) {
                Ok(v) => v,
                Err(e) => {
                    tracing::warn!(rid = %rid, error = %e, "embed failed during backfill");
                    errors += 1;
                    continue;
                }
            }
        };

        // 2. Serialise to the canonical f32 blob format `record()` writes.
        let blob = yantrikdb::serde_helpers::serialize_f32(&embedding);

        // 3. Encrypt the blob if encryption is enabled. With v0.8.11's
        //    public `encrypt_embedding_pub`, encrypted-cluster followers
        //    can finally complete this step. (Pre-v0.8.11 followers
        //    skipped encrypted writes here entirely.)
        let stored_blob = {
            let db = engine.as_ref();
            match db.encrypt_embedding_pub(&blob) {
                Ok(b) => b,
                Err(e) => {
                    tracing::warn!(rid = %rid, error = %e, "encrypt_embedding failed");
                    errors += 1;
                    continue;
                }
            }
        };

        // 4. UPDATE the SQLite memories row with the (possibly-encrypted)
        //    embedding column. Conn is dropped immediately after to free
        //    the lock before the HNSW write in step 5.
        {
            let db = engine.as_ref();
            let conn = db.conn();
            if let Err(e) = conn.execute(
                "UPDATE memories SET embedding = ?1 WHERE rid = ?2",
                params![stored_blob, rid],
            ) {
                tracing::warn!(rid = %rid, error = %e, "embedding UPDATE failed");
                errors += 1;
                continue;
            }
            // conn drops here, releasing the SQLite write lock before
            // we acquire the HNSW write lock — preserves engine lock
            // ordering: conn → … → vec_index.
        }

        // 5. Insert into HNSW piecewise. This is the v0.8.11 fix. Pre-v0.8.11
        //    this was a `db.rebuild_vec_index()` at the END of the loop,
        //    O(N log N) on the entire memories table, taking minutes-to-
        //    hours under load. Per-row insert is O(log N) per memory and
        //    runs as soon as the row is durable in SQLite, so recall on
        //    the follower sees each backfilled memory immediately rather
        //    than waiting for the batch to complete.
        //
        //    Idempotent on retry: if a previous poll cycle already inserted
        //    this rid, the HNSW backend dedupes; we re-attempt cheaply.
        //    The note `embedding IS NULL` guard at the SELECT in step 1
        //    means we won't re-process rows whose UPDATE in step 4
        //    succeeded — only failures retry.
        {
            let db = engine.as_ref();
            if let Err(e) = db.insert_vector(rid, &embedding) {
                tracing::warn!(rid = %rid, error = %e, "HNSW insert_vector failed during backfill");
                errors += 1;
                continue;
            }
        }

        backfilled += 1;
        // Per-row counter `yantrikdb_follower_backfill_inserted_total`
        // deferred to v0.8.12 along with the namespace_schema work; the
        // tracing::info! at end-of-batch below is sufficient operator
        // visibility for v0.8.11 (it logs both backfilled and errors).
    }

    tracing::info!(
        backfilled,
        errors,
        total = count,
        "follower HNSW backfill complete (piecewise insert)"
    );
    Ok(())
}