Bobcares

Redis disable persistence – How we do it easily?

by | Feb 29, 2020

Are you trying to disable persistence in Redis? We can help you with it.

Redis persistence allows us to log every change in the dataset. However, due to disk space shortage, some users may need to disable persistence in Redis.

At Bobcares, we often receive requests to disable it as part of our Server Management Services.

Today, let us discuss how our Support Engineers disable Redis persistence easily for our customers.

 

A quick look at Redis data persistence

As we all know, Redis is a key-value store that also functions as a database, cache and a message broker.

Moreover, Redis is an in-memory database. So, the data in the RAM is lost once the process has been stopped.

Therefore, data persistence is important in Redis. If we store this data to disk, then we can back it up to a remote location in the case of failure.

And, Redis cloud provides two methods to persist the data to disk. They are Append Only File (AOF) and Snapshot (RDB).

 

How we disable persistence?

Snapshot or RDB takes the data at that moment and writes it to the disk, in a binary file called dump.rdb.

On the other hand, AOF writes all the incoming “write” commands to the disk. Data persistence is optional and we can disable it too.

Though persistence prevents data loss, it increases the disk space usage abundantly. So, in cases where we cant persist large data on disk, we disable persistence.

Recently, one of our customers approached us to disable it.  Our Support Engineers followed the below steps to disable it easily.

1. Firstly, we disable the AOF. To do so, we edit the /etc/redis/redis.conf file and set the appendonly directive to NO. Mostly, this will be the default value.

2. Then, we disable RDB snapshotting. And, there are three default configurations defined in the save directive.

We need to disable these three configurations to disable RDB. So, we use the below command to get the default configurations.

redis disable persistence

Then, to disable the save configuration, we use the command,

config set save ""

Finally, we restart the Redis server. Then, we can confirm the new configuration as below.

redis disable persistence

Then, if we scan the redis.conf file, we get no results for the save configurations.

Similarly, we can also use the below command to disable RDB snapshotting.

sed -e '/save/ s/^#*/#/' -i /etc/redis/redis.conf && sudo service redis-server restart

This command will comment out the save configurations in the /etc/redis/redis.conf file and restart the Redis server.

 

[Need more assistance to disable Redis persistence? – We’re available 24/7 to help you.]

 

Conclusion

In today’s writeup, we saw how our Support Engineers disable persistence in Redis.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF