PendingReleaseNotes: note on new omap limits

Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 1591c49b07c34530ac3e40d5453602f5d6e421df..b7456ed7ba43450026fbaa660622a4e272706881 100644 (file)
--- 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.