summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2011-10-17 14:45:16 +0100
committerSimon MacMullen <simon@rabbitmq.com>2011-10-17 14:45:16 +0100
commit87c472085297325d9558757732100e4510607ae3 (patch)
tree4c8014b4a54d21f7e7f37863e78585436772f3ae
parenta485f9d41cffba4de004b135897649d4a04850a9 (diff)
downloadrabbitmq-server-87c472085297325d9558757732100e4510607ae3.tar.gz
Give up on attempting to improve clarity.
-rw-r--r--src/rabbit_msg_store.erl12
1 files changed, 6 insertions, 6 deletions
diff --git a/src/rabbit_msg_store.erl b/src/rabbit_msg_store.erl
index 9049c671..a25245c9 100644
--- a/src/rabbit_msg_store.erl
+++ b/src/rabbit_msg_store.erl
@@ -804,12 +804,12 @@ handle_cast({write, CRef, MsgId},
%% If all writes get eliminated, cur_file_cache_ets could
%% grow unbounded. To prevent that we delete the cache
%% entry here, but only if the message isn't in the
- %% current file (i.e. it has only ever been ignored). That
- %% way reads of the message can continue to be done client
- %% side, from either the cache or the non-current
- %% files. If the message *is* in the current file then the
- %% cache entry will be removed by the normal logic for
- %% that in write_message/4 and maybe_roll_to_new_file/2.
+ %% current file. That way reads of the message can
+ %% continue to be done client side, from either the cache
+ %% or the non-current files. If the message *is* in the
+ %% current file then the cache entry will be removed by
+ %% the normal logic for that in write_message/4 and
+ %% maybe_roll_to_new_file/2.
case index_lookup(MsgId, State1) of
[#msg_location { file = File }]
when File == State1 #msstate.current_file ->