04acaea231
Don't do version & block_ref updates in background on deletion
2020-04-19 20:52:20 +00:00
a6129d8626
Begin implement bucket management & admin commands
2020-04-19 17:15:48 +02:00
7131553c53
Refactor sharding logic; coming next: full replication with epidemic dissemination
2020-04-19 13:22:28 +02:00
4ba54ccfca
Reorder imports.
...
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
2020-04-18 19:39:57 +02:00
bd1618e78e
Remove proto.rs & move some definitions out of data.rs
2020-04-18 19:30:05 +02:00
69f1d8fef2
WIP
...
TODOs:
- ensure sync goes both way
- finish sending blocks to other nodes when they need them before deleting
2020-04-17 17:09:57 +02:00
867646093b
Table range deletion
2020-04-17 14:49:10 +02:00
2bea76ce16
Small refactorings
2020-04-12 22:24:53 +02:00
d1e8f78b2c
Trying to do TLS
2020-04-12 15:51:19 +02:00
5967c5a5af
Refactor a bit
2020-04-12 13:03:55 +02:00
9c931f5eda
Keep network status & ring in a tokio::sync::watch
...
advantages
- reads don't prevent preparing writes
- can be followed from other parts of the system by cloning the receiver
2020-04-11 23:53:32 +02:00
dcf58499a4
table::insert_many, version_table::updated
2020-04-11 19:43:29 +02:00
cf8fd948fc
Add block ref table
2020-04-10 23:11:52 +02:00
3477864142
Fix the Sync issue. Details:
...
So the HTTP client future of Hyper is not Sync, thus the stream
that read blocks wasn't either. However Hyper's default Body type
requires a stream to be Sync for wrap_stream. Solution: reimplement
a custom HTTP body type.
2020-04-10 22:01:48 +02:00
d66c0d6833
Why is it not Sync??
2020-04-09 23:45:07 +02:00
101444abb3
Some progress
2020-04-09 17:32:28 +02:00
4c1aee42d5
Reorganize table API
2020-04-09 16:16:27 +02:00
a450103ed0
Work & TODO
2020-04-08 23:47:34 +02:00
cc580da0ae
Some work
2020-04-08 23:01:49 +02:00
bacc76a057
Some work in actually storing things
2020-04-08 22:00:41 +02:00
