aboutsummaryrefslogtreecommitdiff
path: root/src/table.rs
Commit message (Collapse)AuthorAgeFilesLines
* Pretty loggingAlex Auvolat2020-04-211-2/+2
|
* Don't do version & block_ref updates in background on deletionAlex Auvolat2020-04-191-3/+3
|
* More aggressive sync timings & improve other stuffAlex Auvolat2020-04-191-3/+9
|
* Begin implement bucket management & admin commandsAlex Auvolat2020-04-191-10/+19
|
* Add support for fully replicated tables with epidemic dissemination of updatesAlex Auvolat2020-04-191-3/+17
|
* Refactor sharding logic; coming next: full replication with epidemic ↵Alex Auvolat2020-04-191-30/+57
| | | | dissemination
* Massive RPC refactoringAlex Auvolat2020-04-181-87/+35
|
* Fix sync: use max root checksum levelAlex Auvolat2020-04-171-2/+2
|
* Several resync workers; add delay on retry resyncAlex Auvolat2020-04-171-5/+5
|
* Implement missing handler for read_rangeAlex Auvolat2020-04-171-0/+36
|
* Don't send items...Alex Auvolat2020-04-171-18/+25
| | | | | ...if syncer doesn't need them because he's going to delete the partition anyway. Also, fix block resync queue
* Make sync send data both waysAlex Auvolat2020-04-171-7/+7
|
* WIPAlex Auvolat2020-04-171-31/+87
| | | | | | 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-3/+8
| | | | | | | 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-4/+15
|
* Make all requests continue in the background even after we got enough responses.Alex Auvolat2020-04-161-1/+2
|
* WIPAlex Auvolat2020-04-161-3/+21
|
* WIPAlex Auvolat2020-04-161-2/+19
|
* Begin work on sync...Alex Auvolat2020-04-161-17/+18
|
* Small refactoringsAlex Auvolat2020-04-121-9/+9
|
* Keep network status & ring in a tokio::sync::watchAlex Auvolat2020-04-111-29/+20
| | | | | | advantages - reads don't prevent preparing writes - can be followed from other parts of the system by cloning the receiver
* table::insert_many, version_table::updatedAlex Auvolat2020-04-111-21/+80
|
* (Try to) disable LTO ?Alex Auvolat2020-04-101-0/+5
|
* Fix the Sync issue. Details:Alex Auvolat2020-04-101-33/+61
| | | | | | | 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.
* Why is it not Sync??Alex Auvolat2020-04-091-10/+15
|
* Locally, transactionsAlex Auvolat2020-04-091-16/+39
|
* Something worksAlex Auvolat2020-04-091-3/+8
|
* Some progressAlex Auvolat2020-04-091-20/+8
|
* Reorganize table APIAlex Auvolat2020-04-091-29/+71
|
* Work & TODOAlex Auvolat2020-04-081-35/+41
|
* Some workAlex Auvolat2020-04-081-15/+107
|
* Some work in actually storing thingsAlex Auvolat2020-04-081-0/+116
generated by cgit v1.2.3 (git 2.25.1) at 2024-09-20 21:41:25 +0000