Fix logging_vnode respect sync_log setting

AntidoteDB · Aug 15, 2019 · e53bec0 · e53bec0
1 parent b502dee
commit e53bec0
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 5 deletions.
diff --git a/include/antidote.hrl b/include/antidote.hrl
@@ -61,9 +61,6 @@
 -define(META_TABLE_NAME, a_meta_data_table).
 -define(REMOTE_META_TABLE_NAME, a_remote_meta_data_table).
 -define(META_TABLE_STABLE_NAME, a_meta_data_table_stable).
-%% At commit, if this is set to true, the logging vnode
-%% will ensure that the transaction record is written to disk
--define(SYNC_LOG, false).
 %% Uncomment the following line to use erlang:now()
 %% Otherwise os:timestamp() is used which can go backwards
 %% which is unsafe for clock-si
@@ -269,4 +266,4 @@
     %% true if this is the most recent snapshot in the cache
     is_newest_snapshot :: boolean()
 }).
--type snapshot_get_response() :: #snapshot_get_response{}.
+-type snapshot_get_response() :: #snapshot_get_response{}.
diff --git a/src/logging_vnode.erl b/src/logging_vnode.erl
@@ -144,7 +144,7 @@ read(Node, Log) ->
 -spec asyn_append(index_node(), key(), log_operation(), sender()) -> ok.
 asyn_append(IndexNode, Log, LogOperation, ReplyTo) ->
     riak_core_vnode_master:command(IndexNode,
-                                   {append, Log, LogOperation, ?SYNC_LOG},
+                                   {append, Log, LogOperation, is_sync_log()},
                                    ReplyTo,
                                    ?LOGGING_MASTER).