DOC-4067 added FAQ and note about harmless OOM message

Author: andy-stark-redis

content/integrate/redis-data-integration/ingest/data-pipelines/data-pipelines.md

@@ -495,3 +495,10 @@ completely. For example, you might want to apply a new transformation to all the
 data or refresh the dataset if RDI is disconnected from the
 source for a long time. In situations like these, you can *reset* the pipeline back
 to the snapshot phase. When this is complete, the pipeline continues with CDC as usual. 
+
+{{<note>}}During the snapshot phase and occasionally during CDC, Debezium
+will sometimes log a message saying that RDI is out of memory. This is just
+an information message, not an error condition, and is typically harmless. See the
+[Ingest FAQ]({{< relref "/integrate/redis-data-integration/ingest/faq#rdi-oom" >}})
+for more information.
+{{</note>}}

content/integrate/redis-data-integration/ingest/faq.md

@@ -59,10 +59,21 @@ replica of an Active-Active replication setup or an Auto tiering database.
 
 If you don't configure RDI to capture a specific set of tables in the schema then it will
 detect any new tables when they are added. Similarly, RDI will capture new table columns
-and changes to column names unless you configure it for a specfic set of columns.
+and changes to column names unless you configure it for a specific set of columns.
 Bear in mind that the Redis keys in the target database will change to reflect the
 new or renamed tables and columns.
 
+## Should I be concerned when the log says RDI is out of memory? {#rdi-oom}
+
+Sometimes the Debezium log will contain a message saying that RDI is out of
+memory. This is actually an information message, not an error. It means that
+RDI has used all available memory for its data streams and must now concentrate
+on processing the streams to make space for new data from the collector.
+The message is typically logged during the
+snapshot phase of the
+[ingest pipeline lifecycle]({{< relref "/integrate/redis-data-integration/ingest/data-pipelines/data-pipelines#ingest-pipeline-lifecycle" >}})
+but you may also sometimes see it during the CDC phase.
+
 ## What happens when RDI can't write to the target Redis database?
 
 RDI will keep attempting to write the changes to the target and will also attempt
@@ -79,7 +90,7 @@ more space available.
 ## What does RDI do if the data is corrupted or invalid?
 
 The collector reports the data to RDI in a structured JSON format. If
-the structure of the JSON data is invalid or if there is a fatal bug in the tranformation
+the structure of the JSON data is invalid or if there is a fatal bug in the transformation
 job then RDI can't transform the data. When this happens, RDI will store the original data
 in a "dead letter queue" along with a message to say why it was rejected. The dead letter
 queue is stored as a capped stream in the RDI staging database. You can see its contents