diff options
author | Simon MacMullen <simon@rabbitmq.com> | 2011-10-17 14:42:37 +0100 |
---|---|---|
committer | Simon MacMullen <simon@rabbitmq.com> | 2011-10-17 14:42:37 +0100 |
commit | a485f9d41cffba4de004b135897649d4a04850a9 (patch) | |
tree | 0c458adc6cce7cce13b7555426aeba7ed57b13ab /src/rabbit_msg_store.erl | |
parent | 06a4dba44907014874e9a2db16fc98166ecad507 (diff) | |
download | rabbitmq-server-a485f9d41cffba4de004b135897649d4a04850a9.tar.gz |
Rephrase to make Matthias happier...
Diffstat (limited to 'src/rabbit_msg_store.erl')
-rw-r--r-- | src/rabbit_msg_store.erl | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/src/rabbit_msg_store.erl b/src/rabbit_msg_store.erl index 67940963..9049c671 100644 --- a/src/rabbit_msg_store.erl +++ b/src/rabbit_msg_store.erl @@ -803,13 +803,13 @@ handle_cast({write, CRef, MsgId}, ignored, State), %% 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 hasn't been written - %% into the 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. + %% 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. case index_lookup(MsgId, State1) of [#msg_location { file = File }] when File == State1 #msstate.current_file -> |