- Notifications
You must be signed in to change notification settings - Fork2
Distributed event log storage for Urbit.
License
wexpertsystems/seguro
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
This is the work-in-progress repo for Phase 2 of the Seguro implementation fortheUrbit project.
More information:
After installing the clients and server packages of FoundationDB, the defaultserver should be reconfigured for local testing. This can be done using thefdbcli
utility on Linux and MacOS:
fdbcliconfigure single ssd
This will set the default local FoundationDB cluster to store a single copy ofdata on disk.
The following command will run all Seguro tests:
maketest
Alternatively, the unit or integration tests can be run separately from each other:
make test-unitmake test-integ
The following command will run all Seguro benchmarks:
make benchmark
The state of the local FoundationDB cluster can be monitored using thefdbcli
utility. It's self-documented, butadditional information can be found in theofficial FoundationDB documentation.
However, be warned that thefdbcli
can be finicky, and can lie. Some examples:
- Complaining that there is no memory available with 12GB memory available
- Complaining that there is no space on the drive available when there is 50GB space available
- Errors during benchmark tests while the
status
command shows nothing wrong - No errors during benchmark tests while the
status
command shows memory and storage warnings
If the test or benchmark suites suffer a fatal error, the local FoundationDB may be stranded in an unclean state. It maybe necessary to manually drop keys from the cluster to ensure tests/benchmarks accurately measurecorrectness/performance:
fdbcliwritemode onclearrange""\xFF
The above series of commands will drop all keys from the FoundationDB cluster.
If the FoundationDB cluster becomes so broken during development that a hard reset is required, the following commandswill return the cluster to its initial state after a fresh installation:
sudo systemctl stop foundationdbsudo rm -rf /var/lib/foundationdb/datasudo systemctl start foundationdbfdbcliconfigure new single ssd