[Blog] Introducing the memory retention policy for agentic memory in OpenSearch - #4201
Open
AirFunnyB wants to merge 3 commits into
Open
[Blog] Introducing the memory retention policy for agentic memory in OpenSearch#4201AirFunnyB wants to merge 3 commits into
AirFunnyB wants to merge 3 commits into
Conversation
…OpenSearch Signed-off-by: Erfan Ballew <ballewer@amazon.com>
AirFunnyB
requested review from
AMoo-Miki,
CEHENKLE,
elfisher,
kolchfa-aws,
krisfreedain,
natebower,
nateynateynate,
nknize and
peterzhuamazon
as code owners
August 4, 2026 07:58
|
Thank you for submitting a blog post! The blog post review process is: Submit a PR -> (Optional) Peer review -> Doc review -> Marketing review -> Published. |
|
Hi @AirFunnyB, It looks like you're adding a new blog post but don't have an issue mentioned. Please link this PR to an open issue using one of these keywords in the PR description:
If an issue hasn't been created yet, please create one and then link it to this PR. |
1 task
kolchfa-aws
added
New blog
Signed-off-by: Fanit Kolchina <kolchfa@amazon.com>
kolchfa-aws
reviewed
Aug 4, 2026
Signed-off-by: kolchfa-aws <105444904+kolchfa-aws@users.noreply.github.com>
kolchfa-aws
approved these changes
Aug 4, 2026
kolchfa-aws
left a comment
kolchfa-aws
left a comment
Collaborator
There was a problem hiding this comment.
@AirFunnyB Editorial review complete and rewrites applied. The blog is ready for final marketing review/publishing. cc: @pajuric
kolchfa-aws
added
Done and ready to publish
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a blog post introducing automatic memory lifecycle management for agentic memory in OpenSearch (the memory retention policy feature in ml-commons). The post covers:
retention_daysand/ormax_count) on a memory container for sessions, long-term memory, and history, enforced by a scheduled background job.plugins.ml_commons.memory.retention_enabled, which defaults tofalse; an admin enables it explicitly.No code changes — this PR adds blog content only.
Issues Resolved
N/A
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.
Supersedes #4191, which was closed with a corrupted commit; this PR reopens the same content on a clean history.