DOC-4973 RS: Added JSON active degramentation known limitation to RS April release notes

Author: rrelledge

content/operate/rs/release-notes/rs-7-22-releases/_index.md

@@ -118,3 +118,7 @@ You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Enterprise S
 #### Query results might include hash keys with lazily expired fields
 
 If one or more fields of a hash key expire after an `FT.SEARCH` or `FT.AGGREGATE` query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.
+
+#### Active defragmentation does not stop mid-key for JSON
+
+Active defragmentation does not stop mid-key for JSON data. Large keys are defragmented in full, which might cause latency spikes.

content/operate/rs/release-notes/rs-7-22-releases/rs-7-22-x-tba.md

@@ -253,6 +253,10 @@ You cannot upgrade from a prior RHEL version to RHEL 9 if the Redis Enterprise S
 
 If one or more fields of a hash key expire after an `FT.SEARCH` or `FT.AGGREGATE` query begins, Redis does not account for these lazily expired fields. As a result, keys with expired fields might still be included in the query results, leading to potentially incorrect or inconsistent results.
 
+#### Active defragmentation does not stop mid-key for JSON
+
+Active defragmentation does not stop mid-key for JSON data. Large keys are defragmented in full, which might cause latency spikes.
+
 ## Security
 
 #### Open source Redis security fixes compatibility