Changing data retention settings has no affect
Hello!
I was updating the data retention settings of a table within my Timeseries DB, and even though I can see settings have been updated in the console, I can see that the table still operates using the old settings.
I know this because if I were to send a new telemetry entry that's older than 6hrs (which was the default memoryStoreRetentionPeriodInHours), I would get an error.
So, that means the new memoryStoreRetentionPeriodInHours hasn't actually been applied - even though the console says so.
Hope I've managed to explain my situation. Happy to share more info if needed.
- Newest
- Most votes
- Most comments
Hi,
You may be running into the behavior described in the note on this page: https://docs.aws.amazon.com/timestream/latest/developerguide/storage.html The retention change will take effect from the point that you make the change onward. If you were to update your memory store retention period from 6hrs to say 24hrs, it would take 18hrs for the memory store to reflect the full 24hr window. Does this match the behavior you see?
Thanks for your feedback on Amazon Timestream!
Relevant content
- Accepted Answerasked 4 years ago
- asked 3 years ago
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated 10 months ago- Why is no data migrated from my Amazon S3 source endpoint even though my AWS DMS task is successful?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
Thank you for the response and sorry for the delay on my end.
I kinda understand your answer, but, on the other hand, still not sure if that's it.
So, it seems the doc says that, if I were to change the
memoryStoreRetentionPeriodInHours, to say, 7 days, then I'd need to wait 7 days in order to be able to insert records that are 7 days old? Is that the case?Thank you!
P.S. Luckily we're still not live with our project, so I was able to circumvent my issue by just destroying/deploying the same table, this time with new settings.