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
HI ;)
I want to run a big tx (1.4GB when committed in redis). For this, I'm using TxPipelined + Watch.
The problem is that when the first big tx is committed and takes its 1.4Gb, the second one with the same volume fails (OOM command not allowed when used memory > 'maxmemory') although the total redis ram is 3Gb.
What can I do besides adding ram?
I think about splitting the tx into multiple ones but rollback handling would be much more complex.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
HI ;)
I want to run a big tx (1.4GB when committed in redis). For this, I'm using
TxPipelined + Watch
.The problem is that when the first big tx is committed and takes its 1.4Gb, the second one with the same volume fails (OOM command not allowed when used memory > 'maxmemory') although the total redis ram is 3Gb.
What can I do besides adding ram?
I think about splitting the tx into multiple ones but rollback handling would be much more complex.
Beta Was this translation helpful? Give feedback.
All reactions