aboutsummaryrefslogtreecommitdiff
path: root/src/block_ref_table.rs
Commit message (Collapse)AuthorAgeFilesLines
* Don't do version & block_ref updates in background on deletionAlex Auvolat2020-04-191-7/+5
|
* Reorder imports.Alex Auvolat2020-04-181-1/+2
| | | | | | | 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
* WIPAlex Auvolat2020-04-171-0/+5
| | | | | | TODOs: - ensure sync goes both way - finish sending blocks to other nodes when they need them before deleting
* Implement getting missing blocks when RC increasesAlex Auvolat2020-04-171-4/+1
| | | | | | | 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.
* Table range deletionAlex Auvolat2020-04-171-7/+8
|
* Small refactoringsAlex Auvolat2020-04-121-1/+1
|
* Trying to do TLSAlex Auvolat2020-04-121-2/+2
|
* Refactor a bitAlex Auvolat2020-04-121-8/+7
|
* Keep network status & ring in a tokio::sync::watchAlex Auvolat2020-04-111-2/+5
| | | | | | advantages - reads don't prevent preparing writes - can be followed from other parts of the system by cloning the receiver
* Local refcounting of blocksAlex Auvolat2020-04-111-2/+14
|
* table::insert_many, version_table::updatedAlex Auvolat2020-04-111-1/+1
|
* Add block ref tableAlex Auvolat2020-04-101-0/+51