Shared-Nothing Persistence
The shared-nothing persistence example shows how to make an application be its own persister using the internal shared-nothing persistence feature.
Shared-nothing persistence can be demonstrated using the ASOperations example. With shared-nothing persistence, each seeder in the space stores its space entries locally on disk.
Using ASOperations for shared-nothing persistence, you will be able to see how data is recovered from disk. If all seeders in a space go down, data recovery is initiated using as-admin after the seeders are brought back up.
The following is the default location for persisting data:
data_store_path/metaspace_name/space_name/member_name
Where data_store_path defaults to your user home directory. Use the -data_store command line option to change the default data_store_path location.
Shared-nothing persistence is built into ActiveSpaces, so there is no persistence interface that you need to implement. The only thing you have to do is to define a space with a persistence type of shared-nothing.
- Starting ASOperations for Shared-Nothing Persistence
- Using Shared-Nothing Persistence
One of the interesting things to see demonstrated for shared-nothing persistence, is how recovery occurs when all of the seeders for a space go down and then come back up.