You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
In resource server, there are some resource items whose unique attribute changes almost at every publication. It can be avoided in some but not in all. This result in amount of data holding in a single redis key to higher value as number of days goes on. Possible Solution
Delete redis key and recreate it again (why recreate? because latest ingestion pipeline and resource server thinks the key always exists once the key is created on arrival of first packet). This can be done as cron job and with some threshold on no. of entries.
Drawback: Might lose data.
The text was updated successfully, but these errors were encountered:
Problem
In resource server, there are some resource items whose unique attribute changes almost at every publication. It can be avoided in some but not in all. This result in amount of data holding in a single redis key to higher value as number of days goes on.
Possible Solution
Delete redis key and recreate it again (why recreate? because latest ingestion pipeline and resource server thinks the key always exists once the key is created on arrival of first packet). This can be done as cron job and with some threshold on no. of entries.
Drawback: Might lose data.
The text was updated successfully, but these errors were encountered: