blog documentation FAQ followers forum marketplace services youtube

solved redis no longer clearing cache correctly

The Jamroom Network » Forum » Using Jamroom » Page » redis no longer clearing cache correctly
soaringeagle
@soaringeagle
6 years ago
3,304 posts
its using 180 gigs despite being set to use a max of 4 gigs ram
its using 180 gigs on the ssd drive driving disk usage to near max..


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
updated by @soaringeagle: 09/09/18 04:46:08PM
brian
@brian
6 years ago
10,148 posts
This is an issue with your server - not Jamroom. Redis is an in memory data structure server, so unless your server has 180+ gigs of RAM then it cannot be using that much. Sounds like you need to turn off replication or logging:

https://redis.io/topics/config


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
soaringeagle
@soaringeagle
6 years ago
3,304 posts
its the drive for sure. not ram. replications not on. i'll check logging but could that have gobbled up that much space in just 24 hours/ seemed to happen just since last update


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
brian
@brian
6 years ago
10,148 posts
It's not related to the Jamroom module update - the module does not control or configure Redis in any way.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
soaringeagle
@soaringeagle
6 years ago
3,304 posts
can't figure out why its suddenly using up so much more drive space then. before clearing caches it was adding 1% every couple minutes


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
brian
@brian
6 years ago
10,148 posts
You've got Redis misconfigured if it is using disk space. When setup as a cache it will not use any disk space.

Make sure you have the "appendonly" config option set to "no".

You basically need to turn off persistence:

https://redis.io/topics/persistence


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
soaringeagle
@soaringeagle
6 years ago
3,304 posts
thats what i thought too but they told me it was using disk space ..
i don't think it did before
and not 100% certain thats the issue.


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
brian
@brian
6 years ago
10,148 posts
Yeah you will want to work that out with your hosting provider - it's not controlled by JR.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
soaringeagle
@soaringeagle
6 years ago
3,304 posts
appendonly is off but appendifsync is set to everysec is that right/


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities
brian
@brian
6 years ago
10,148 posts
soaringeagle:
appendonly is off but appendifsync is set to everysec is that right/

I think it is an important reminder that we are not hosting support for your server. I'm not trying to "not help" but pretty much any time you have a server problem it seems to result in a forum post here.

Here is the documentation on Redis persistence:

https://redis.io/topics/persistence

Read through that, and if you have a question on something in there that is not clear, make sure and contact your hosting provider - they are the ones who should be providing you with help configuring your server.

If you have a question about how to configure the Jamroom Redis module (i.e. Global Config, etc.) please let me know.

P.S. the "append" config options have no bearing if the append file is off.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
soaringeagle
@soaringeagle
6 years ago
3,304 posts
think the raide controller went bad or something.
missing 1/2 my media drive space
not sure why that would also cause the ssd to be more full.
but it does seem to be something with the raid configuration that suddenly went screwy


--
soaringeagle
head dreadhead at dreadlocks site
glider pilot student and member/volunteer coordinator with freedoms wings international soaring for people with disabilities

Tags