File System: Difference between revisions
Jump to navigation
Jump to search
(Created page with "In the file system persistency layer, each subfolder of your data folder is a database. Each folder has the following files: * schema.json - list of all tables, columns, keys and shards; is updated every time a shard is added or removed or the schema changes * schema.json.old - fallback file for crash recovery * [uuid]-[columnname] - the content of a column (in case the ENGINE is not MEMORY) * [uuid].log - transaction log in c...") |
No edit summary |
||
| Line 7: | Line 7: | ||
* [uuid]-[columnname] - the content of a column (in case the [[Persistency and Performance Guarantees|ENGINE]] is not MEMORY) | * [uuid]-[columnname] - the content of a column (in case the [[Persistency and Performance Guarantees|ENGINE]] is not MEMORY) | ||
* [uuid].log - transaction log in case the [[Persistency and Performance Guarantees|ENGINE]] is LOGGED or SAFE | * [uuid].log - transaction log in case the [[Persistency and Performance Guarantees|ENGINE]] is LOGGED or SAFE | ||
You can also use a [[Cluster Monitor]] for the File System persistency backend. The only thing you have to assure is that each node of the cluster points with -data to the same shared directory. | |||
Latest revision as of 19:59, 31 August 2025
In the file system persistency layer, each subfolder of your data folder is a database.
Each folder has the following files:
- schema.json - list of all tables, columns, keys and shards; is updated every time a shard is added or removed or the schema changes
- schema.json.old - fallback file for crash recovery
- [uuid]-[columnname] - the content of a column (in case the ENGINE is not MEMORY)
- [uuid].log - transaction log in case the ENGINE is LOGGED or SAFE
You can also use a Cluster Monitor for the File System persistency backend. The only thing you have to assure is that each node of the cluster points with -data to the same shared directory.