Cluster Monitor: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The cluster monitor lets you scale out MemCP over multiple nodes. Here is what you can achieve: * '''Multiple users''': each user has his own database * '''One big user''': Big tables are spread over multiple nodes * A mixture of both variants Each database and each shard (the piece where a part of a table's data is stored) can be placed either: * '''COLD''': only in storage backend * '''SHARED''': read-only on multiple nodes (e.g. the access table) * '''WRITE''': exc...") |
No edit summary |
||
| Line 10: | Line 10: | ||
* '''SHARED''': read-only on multiple nodes (e.g. the access table) | * '''SHARED''': read-only on multiple nodes (e.g. the access table) | ||
* '''WRITE''': exclusively on one node | * '''WRITE''': exclusively on one node | ||
Cluster monitors can coordinate all kinds of storage: | |||
* [[File System]] | |||
* [[S3 Buckets]] | |||
* [[Ceph/Rados]] | |||
Revision as of 20:51, 31 August 2025
The cluster monitor lets you scale out MemCP over multiple nodes. Here is what you can achieve:
- Multiple users: each user has his own database
- One big user: Big tables are spread over multiple nodes
- A mixture of both variants
Each database and each shard (the piece where a part of a table's data is stored) can be placed either:
- COLD: only in storage backend
- SHARED: read-only on multiple nodes (e.g. the access table)
- WRITE: exclusively on one node
Cluster monitors can coordinate all kinds of storage: