9e31a054aa
RecoverNode now uses on-disk database
1 year ago
88ce311b37
Remove all WAL-related files when loading new DB
1 year ago
b931e387be
First pass at removing in-memory support
1 year ago
23b8b6e5c9
Actually rename
1 year ago
2ac27c2ffc
Move Store tests back to single directory
1 year ago
65c6a56468
Remove the file
1 year ago
88d448851d
Blank out on-disk store tests
1 year ago
02b7ea7955
Close Store so temp storage can be cleaned up
1 year ago
e47c7a1b7b
Stress-test snapshotting
1 year ago
e497ee75f9
Fix typo
1 year ago
f06e547ab5
Less disk IO during load
1 year ago
f5517c0f66
Correct comment
1 year ago
9bdf048975
Better naming of temp backup file
1 year ago
b5cb889e1e
Auto-restore doesn't require ready() check
1 year ago
b7633143cc
Restore from file uses chunking
1 year ago
5ca5ce342e
Support internode LoadChunk()
1 year ago
1c8e52c5f7
Test_SingleNodeLoadBinaryFromReader passes
...
That's good, but much more extensive testing needed, and this needs to
replace the existing load path -- and then we move to 8.0.
1 year ago
93a752ae0e
Better variable names
1 year ago
1c6f691ff8
Integrate chunking - WIP
...
I need more sophisticated dechunker management.
1 year ago
13d47b24d8
Store can load from an io.Reader
...
This may be helpful for chunked-loads.
1 year ago
a40c43725f
More logic reversal
1 year ago
f81aad8fd3
Revert logic for clarity
1 year ago
21dff4a68c
Remove on-disk-startup control
...
With the move to WAL and "synchronous mode" to OFF, on-disk startup
times are very close to in-memory. There is no need for this control
anymore and it complicates the start-up code.
1 year ago
e845e0c243
Fix remaining expression test cases
1 year ago
f7ced46377
Count number of DB stats errors
1 year ago
36fa7f2afd
Detect DB stats error and log
1 year ago
7ce2c6b99a
Fix comment
1 year ago
7432bceca3
Since we're passed a ReadCloser, close it
1 year ago
4342650c33
Fix RecoverNode
1 year ago
ad73779285
Periodically record actually applied index
...
This ensures the system doesn't apply uncommitted log entries to the
FSM, if it runs the in-memory startup. There have been no reports of
this in the field -- it is an edge case -- but this removes any chance
of it.
1 year ago
abfe056b4c
Remove any -wal and -shm files on shutdown
...
If in WAL mode, open-and-close again to remove the -wal file. This is not strictly necessary, since any on-disk database files will be removed when rqlite next starts, but it leaves the directory containing the database file in a cleaner state.
1 year ago
6cd8d30749
Fix Store-level database-backup test
1 year ago
a6925414ef
Better comments
1 year ago
b2f28d1181
Better WAL control
1 year ago
2f7672d897
Enable WAL mode
1 year ago
585f9c9c05
Use Snapshot decoder in Store
1 year ago
58534d4815
Better name for V1 Snapshotter
1 year ago
c87931c45c
Factor Snapshot creation into own module
1 year ago
3f462eecfa
Remove all on-disk SQLite files on startup
1 year ago
7e1b8d12d7
Add full WAL support to DB layer
1 year ago
eed215c664
Only 1 Snapshot needs to be retained
1 year ago
b9253e6b41
Improve logging in Store
1 year ago
4a7ac2850f
rqlite doesn't (yet) support WAL mode SQLite data
1 year ago
92bc513242
Move FSMSnapshot to own source file
1 year ago
e4a0d96f23
Further refactoring
1 year ago
3dd37f8771
Move on-disk Store testing to distinct file
1 year ago
6c7c32ab4e
Remove racy test code
1 year ago
aed541b98e
Poll nodes
1 year ago
8a8e126061
Use some loops
1 year ago
ef42d28e36
Refactor and log more during test
...
https://ci.appveyor.com/project/otoolep/rqlite/builds/47107026 - this
looks racy, as the Leader had been detected, but the config not yet
applied. Leave for now and see if more info can be gathered. This may be
happening because WaitForLeader() has a fast path now.
1 year ago
Philip O'Toole