Update config

CONFIGURATION.md

@@ -62,7 +62,7 @@ fetch_error_backoff_ms                   |  C  | 0 .. 300000     |           500
 offset_store_method                      |  C  | none, file, broker |        broker | Offset commit store method: 'file' - local file store (offset.store.path, et.al), 'broker' - broker commit store (requires Apache Kafka 0.8.2 or later on the broker)
 check_crcs                               |  C  | true, false     |         false | Verify CRC32 of consumed messages, ensuring no on-the-wire or on-disk corruption to the messages occurred. This check comes at slightly increased CPU usage
 queue_buffering_max_messages             |  P  | 1 .. 10000000   |        100000 | Maximum number of messages allowed on the producer queue
-queue_buffering_max_kbytes               |  P  | 1 .. 2097151    |       4000000 | Maximum total message size sum allowed on the producer queue
+queue_buffering_max_kbytes               |  P  | 1 .. 2097151    |       4000000 | Maximum number of kilobytes per topic+partition in the local consumer queue. This value may be overshot by fetch_message_max_bytes. This property has higher priority than queued_min_messages.
 queue_buffering_max_ms                   |  P  | 0 .. 900000     |             0 | Maximum time, in milliseconds, for buffering data on the producer queue
 queue_buffering_overflow_strategy        |  P  | local_disk_queue, block_calling_process, drop_records | local_disk_queue| What strategy to pick in case the memory queue is full: write messages on a local disk queue and send them in kafka when the in memory queue have enough space, block calling process until memory queue has enough space or drop the messages
 message_send_max_retries                 |  P  | 0 .. 10000000   |             2 | How many times to retry sending a failing MessageSet. **Note:** retrying may cause reordering