Add sync_strategy comments
This commit is contained in:
parent
2db28c3028
commit
fce7cbd2ef
1 changed files with 7 additions and 0 deletions
|
@ -114,6 +114,13 @@
|
||||||
%% low memory installations), there should not be huge variance in outcomes
|
%% low memory installations), there should not be huge variance in outcomes
|
||||||
%% from modifying these numbers.
|
%% from modifying these numbers.
|
||||||
%%
|
%%
|
||||||
|
%% The sync_strategy determines if the store is going to flush writes to disk
|
||||||
|
%% before returning an ack. There are three settings currrently supported:
|
||||||
|
%% - sync - sync to disk by passing the sync flag to the file writer (only
|
||||||
|
%% works in OTP 18)
|
||||||
|
%% - riak_sync - sync to disk by explicitly calling data_sync after the write
|
||||||
|
%% - none - leave it to the operating system to control flushing
|
||||||
|
%%
|
||||||
%% On startup the Bookie must restart both the Inker to load the Journal, and
|
%% On startup the Bookie must restart both the Inker to load the Journal, and
|
||||||
%% the Penciller to load the Ledger. Once the Penciller has started, the
|
%% the Penciller to load the Ledger. Once the Penciller has started, the
|
||||||
%% Bookie should request the highest sequence number in the Ledger, and then
|
%% Bookie should request the highest sequence number in the Ledger, and then
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue