| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Trying to separate:
1. Stuff for handling the swarm of nodes and generic table data replication
2. Stuff for the object store core application: metadata tables and block management
3. Stuff for the S3 API
|
|
|
|
|
|
| |
TODOs:
- ensure sync goes both way
- finish sending blocks to other nodes when they need them before deleting
|
|
|
|
|
|
|
| |
Issue: RC increases also when the block ref entry is first put by the actual client.
At that point the client is probably already sending us the block content,
so we don't need to do a get...
We should add a delay before the task is added or find something to do.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
advantages
- reads don't prevent preparing writes
- can be followed from other parts of the system by cloning the receiver
|
| |
|
| |
|
|
|