I could not answer to Cache Server JVM_HEAP_MAX size change because of the error "An error occurred while trying to submit your post. Please select an environment.", so I just post here.
The workaround in the thread did not work for us:
The setenv script has so many errors that the only way to setup the memory parameters was to setup ALL available parameters.... only in this case it worked.
This we had to setup on 18.104.22.168 (SLES11 x64) to get it working:
I've been talking with our VP of Engineering about this. There was a regression introduced in 4.5.7 and 5.0.0-5.0.3 that requires a workaround to set cache memory. (Fixed in 4.5.8 and 5.0.4). Our recommended workaround is detailed below.
When attempting to fix https://jira.jivesoftware.com/browse/JIVE-4103 so that 4.5.x heap settings would get picked up (i.e., if JVM_MAX_HEAP was present that would be used), a serious platform bug was introduced. The effect of this bug was that there was no way to edit cache.conf to change the heap setting. The only workaround was to edit /usr/local/jive/voldemort/config/setenv, but that file is overwritten (by design) on every RPM upgrade. We filed a bug for this, too (https://jira.jivesoftware.com/browse/JIVE-17882), which is fixed 5.0.4 and 4.5.8.
In the meantime, here is the workaround for various versions:
For 4.5.7 (includes workaround for JIVE-17882)
For 5.0.1, 5.0.2, 5.0.3 (includes work-around for JIVE-17882)
or, if upgrading in-place from 4.5.x: