max heap setting does not work
Opened this issue ยท 6 comments
I don't seem to have a locally-installed redis so it should be using the Linux 64-bit one inside the jar.
*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 3
>>> 'maxheap 128M'
Bad directive or wrong number of arguments
it's not maxheap
it's maxmemory
. Typo in the README.
I also ran into this, however on windows the maxheap
option DID work.
At least you don't get a fatal error on windows. I checked the conf file on windows and it does not mention a maxheap
option but # maxmemory <bytes>
.
I also checked the self documented conf files (versions 2.4, 2.6, 2.8 and 3.0) at redis conf documentation and couldn't find a maxheap option.
Therefore I would recommend using the maxmemory
option.
I am a bit confused with commit db9a01b by @jonfreedman. The discussion above suggests to use maxmemory
instead of maxheap
and the commit contradicts that. Can somebody shed some light to this?
@zabetak that's not my commit, I was saying the same thing as you...
Aaahh yes just realized :D Thanks for replying @jonfreedman