Skip to content

Commit f54d02d

Browse files
committed
Remove extra details from msg_store_credit_disc_bound from example config
Having discussed with @michaelklishin & @hairyhum, it was agreed that these details belong in http://www.rabbitmq.com/persistence-conf.html
1 parent 2f34158 commit f54d02d

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

docs/rabbitmq.config.example

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -373,23 +373,9 @@
373373
%% {queue_index_embed_msgs_below, 4096},
374374

375375
%% The credits that a queue process is given by the message store.
376-
%%
377376
%% By default, a queue process is given 4000 message store credits,
378377
%% and then 800 for every 800 messages that it processes.
379378
%%
380-
%% A queue process persists AMQP messages by sending them 1 by 1 to the message store process.
381-
%% If the queue process sent 4000 AMQP messages and the message store process didn't manage to persist 800,
382-
%% the queue process will enter flow state. If the disks are fast and uncontended, as they should,
383-
%% the message store process will give the queue process 800 credits for every 800 messages that it processes.
384-
%%
385-
%% Messages which need to be paged out due to memory pressure will also use this credit.
386-
%%
387-
%% The Message Store is the last component in the credit flow chain.
388-
%% Learn more about credit flow: https://www.rabbitmq.com/blog/2015/10/06/new-credit-flow-settings-on-rabbitmq-3-5-5/
389-
%%
390-
%% This value only takes effect when messages are persisted to the message store.
391-
%% If messages are embedded on the queue index,
392-
%% then modifying this setting has no effect because credit_flow is NOT used when writing to the queue index.
393379
%% {msg_store_credit_disc_bound, {4000, 800}},
394380

395381
%% Whether or not to enable background GC.

0 commit comments

Comments
 (0)