From 99536f351c7ddaa54d3a721b256ac15cd5c92df3 Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Thu, 17 Nov 2016 22:28:21 -0600 Subject: [PATCH] PendingReleaseNotes: note on new omap limits Signed-off-by: Sage Weil --- PendingReleaseNotes | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/PendingReleaseNotes b/PendingReleaseNotes index 1591c49b07c3..b7456ed7ba43 100644 --- a/PendingReleaseNotes +++ b/PendingReleaseNotes @@ -90,3 +90,12 @@ jerasure_neon, shec_generic, shec_sse3, shec_sse4, and shec_neon. If you use any of these plugins directly you will see a warning in the mon log file. Please switch to using just 'jerasure' or 'shec'. + +* The librados omap get_keys and get_vals operations include a start key and a + limit on the number of keys to return. The OSD now imposes a configurable + limit on the number of keys and number of total bytes it will respond with, + which means that a librados user might get fewer keys than they asked for. + This is necessary to prevent careless users from requesting an unreasonable + amount of data from the cluster in a single operation. The new limits are + configured with `osd_max_omap_entries_per_request`, defaulting to 131,072, and + 'osd_max_omap_bytes_per_request', defaulting to 4MB. -- 2.47.3