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
I'm having issues with my SSDB instance after 2 months of running it.
I write some data with SETX to expire the data after 1 month. And everything worked great but after 2 months aprox, it stopped working right. I execute the SETX commands and most of the time it doesn't have a response, so the data is not set into the database.
The data folder is about 400GB in data. (Also seems that the expired keys doesn't realease the disk space)
I reseted the database and everything start to work great again.
So there might be something corrupt that broke the database or there is an issue when the database is too big.
In the log files it doesn't show any error or anything.. but for example the SETX commands that failed doesn't appear there.
Any idea what could be happening?
The text was updated successfully, but these errors were encountered:
Did you set many key to expire at the small period of time? If too many key expires at the same time, the server may slow down. If this is the case, I would recommend set keys to expire at different point of time.
Check the CPU and disk IO usage when your SSDB instance stop working.
Hello.
I'm having issues with my SSDB instance after 2 months of running it.
I write some data with SETX to expire the data after 1 month. And everything worked great but after 2 months aprox, it stopped working right. I execute the SETX commands and most of the time it doesn't have a response, so the data is not set into the database.
The data folder is about 400GB in data. (Also seems that the expired keys doesn't realease the disk space)
I reseted the database and everything start to work great again.
So there might be something corrupt that broke the database or there is an issue when the database is too big.
In the log files it doesn't show any error or anything.. but for example the SETX commands that failed doesn't appear there.
Any idea what could be happening?
The text was updated successfully, but these errors were encountered: