metastar/meta-core
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

doc improvement

Browse Source
This commit is contained in:
Pierre
2026-05-10 19:47:05 +02:00
parent bd833b7be4
commit 3d65e7e951
1 changed files with 7 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/meta-core-architecture.md
+7 -14
View File
@@ -145,20 +145,13 @@ Meta-core runs as a **standalone container**. Other services connect to it via H
└──────────────────────────────┘ └──────────────────────────────┘
``` ```
For high availability, multiple meta-core instances can run with flock-based failover: The flock-based leader election primitive is described below. Multi-instance
meta-core deployments (with a sibling failover instance) were used in earlier
``` dev stacks but are deprecated; the dev compose now runs a single
┌─────────────────────┐ ┌─────────────────────┐ `metacore-app`. The election primitive itself is retained — it is what gates
│ meta-core │ │ meta-core-2 │ which process owns Redis and the writeable `/meta-core` state, and it remains
│ ★ LEADER │ │ follower │ correct under a single-instance deployment (the lock is held by that one
│ │ │ │ process for its lifetime).
│ [Redis] ───────────┼──────┼─► Connects to │
│ │ │ leader's Redis │
└─────────────────────┘ └─────────────────────┘
│
▼
/meta-core/locks/kv-leader.lock (flock held by leader)
```
--- ---