漫话Redis源码之三十二

2024-02-06 09:48
文章标签 源码 redis 三十二 漫话

本文主要是介绍漫话Redis源码之三十二,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

关于report相关的函数,非核心逻辑。我一般是直接忽略,不纠结。这样对理解整个代码也有好处,该忽略就忽略,该屏蔽就屏蔽:

#ifdef __GNUC__
void rdbReportError(int corruption_error, int linenum, char *reason, ...) __attribute__ ((format (printf, 3, 4)));
#endif
void rdbReportError(int corruption_error, int linenum, char *reason, ...) {va_list ap;char msg[1024];int len;len = snprintf(msg,sizeof(msg),"Internal error in RDB reading offset %llu, function at rdb.c:%d -> ",(unsigned long long)server.loading_loaded_bytes, linenum);va_start(ap,reason);vsnprintf(msg+len,sizeof(msg)-len,reason,ap);va_end(ap);if (!server.loading) {/* If we're in the context of a RESTORE command, just propagate the error. *//* log in VERBOSE, and return (don't exit). */serverLog(LL_VERBOSE, "%s", msg);return;} else if (rdbCheckMode) {/* If we're inside the rdb checker, let it handle the error. */rdbCheckError("%s",msg);} else if (rdbFileBeingLoaded) {/* If we're loading an rdb file form disk, run rdb check (and exit) */serverLog(LL_WARNING, "%s", msg);char *argv[2] = {"",rdbFileBeingLoaded};redis_check_rdb_main(2,argv,NULL);} else if (corruption_error) {/* In diskless loading, in case of corrupt file, log and exit. */serverLog(LL_WARNING, "%s. Failure loading rdb format", msg);} else {/* In diskless loading, in case of a short read (not a corrupt* file), log and proceed (don't exit). */serverLog(LL_WARNING, "%s. Failure loading rdb format from socket, assuming connection error, resuming operation.", msg);return;}serverLog(LL_WARNING, "Terminating server after rdb file reading failure.");exit(1);
}static ssize_t rdbWriteRaw(rio *rdb, void *p, size_t len) {if (rdb && rioWrite(rdb,p,len) == 0)return -1;return len;
}int rdbSaveType(rio *rdb, unsigned char type) {return rdbWriteRaw(rdb,&type,1);
}/* Load a "type" in RDB format, that is a one byte unsigned integer.* This function is not only used to load object types, but also special* "types" like the end-of-file type, the EXPIRE type, and so forth. */
int rdbLoadType(rio *rdb) {unsigned char type;if (rioRead(rdb,&type,1) == 0) return -1;return type;
}/* This is only used to load old databases stored with the RDB_OPCODE_EXPIRETIME* opcode. New versions of Redis store using the RDB_OPCODE_EXPIRETIME_MS* opcode. On error -1 is returned, however this could be a valid time, so* to check for loading errors the caller should call rioGetReadError() after* calling this function. */
time_t rdbLoadTime(rio *rdb) {int32_t t32;if (rioRead(rdb,&t32,4) == 0) return -1;return (time_t)t32;
}int rdbSaveMillisecondTime(rio *rdb, long long t) {int64_t t64 = (int64_t) t;memrev64ifbe(&t64); /* Store in little endian. */return rdbWriteRaw(rdb,&t64,8);
}/* This function loads a time from the RDB file. It gets the version of the* RDB because, unfortunately, before Redis 5 (RDB version 9), the function* failed to convert data to/from little endian, so RDB files with keys having* expires could not be shared between big endian and little endian systems* (because the expire time will be totally wrong). The fix for this is just* to call memrev64ifbe(), however if we fix this for all the RDB versions,* this call will introduce an incompatibility for big endian systems:* after upgrading to Redis version 5 they will no longer be able to load their* own old RDB files. Because of that, we instead fix the function only for new* RDB versions, and load older RDB versions as we used to do in the past,* allowing big endian systems to load their own old RDB files.** On I/O error the function returns LLONG_MAX, however if this is also a* valid stored value, the caller should use rioGetReadError() to check for* errors after calling this function. */
long long rdbLoadMillisecondTime(rio *rdb, int rdbver) {int64_t t64;if (rioRead(rdb,&t64,8) == 0) return LLONG_MAX;if (rdbver >= 9) /* Check the top comment of this function. */memrev64ifbe(&t64); /* Convert in big endian if the system is BE. */return (long long)t64;
}

这篇关于漫话Redis源码之三十二的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/683909

相关文章

Redis Cluster模式配置

《RedisCluster模式配置》:本文主要介绍RedisCluster模式配置,本文给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考下吧... 目录分片 一、分片的本质与核心价值二、分片实现方案对比 ‌三、分片算法详解1. ‌范围分片(顺序分片)‌2. ‌哈希分片3. ‌虚

Springboot整合Redis主从实践

《Springboot整合Redis主从实践》:本文主要介绍Springboot整合Redis主从的实例,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录前言原配置现配置测试LettuceConnectionFactory.setShareNativeConnect

Redis过期删除机制与内存淘汰策略的解析指南

《Redis过期删除机制与内存淘汰策略的解析指南》在使用Redis构建缓存系统时,很多开发者只设置了EXPIRE但却忽略了背后Redis的过期删除机制与内存淘汰策略,下面小编就来和大家详细介绍一下... 目录1、简述2、Redis http://www.chinasem.cn的过期删除策略(Key Expir

Redis指南及6.2.x版本安装过程

《Redis指南及6.2.x版本安装过程》Redis是完全开源免费的,遵守BSD协议,是一个高性能(NOSQL)的key-value数据库,Redis是一个开源的使用ANSIC语言编写、支持网络、... 目录概述Redis特点Redis应用场景缓存缓存分布式会话分布式锁社交网络最新列表Redis各版本介绍旧

Java如何从Redis中批量读取数据

《Java如何从Redis中批量读取数据》:本文主要介绍Java如何从Redis中批量读取数据的情况,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一.背景概述二.分析与实现三.发现问题与屡次改进3.1.QPS过高而且波动很大3.2.程序中断,抛异常3.3.内存消

Redis中的Lettuce使用详解

《Redis中的Lettuce使用详解》Lettuce是一个高级的、线程安全的Redis客户端,用于与Redis数据库交互,Lettuce是一个功能强大、使用方便的Redis客户端,适用于各种规模的J... 目录简介特点连接池连接池特点连接池管理连接池优势连接池配置参数监控常用监控工具通过JMX监控通过Pr

python操作redis基础

《python操作redis基础》Redis(RemoteDictionaryServer)是一个开源的、基于内存的键值对(Key-Value)存储系统,它通常用作数据库、缓存和消息代理,这篇文章... 目录1. Redis 简介2. 前提条件3. 安装 python Redis 客户端库4. 连接到 Re

Redis迷你版微信抢红包实战

《Redis迷你版微信抢红包实战》本文主要介绍了Redis迷你版微信抢红包实战... 目录1 思路分析1.1hCckRX 流程1.2 注意点①拆红包:二倍均值算法②发红包:list③抢红包&记录:hset2 代码实现2.1 拆红包splitRedPacket2.2 发红包sendRedPacket2.3 抢

Golang实现Redis分布式锁(Lua脚本+可重入+自动续期)

《Golang实现Redis分布式锁(Lua脚本+可重入+自动续期)》本文主要介绍了Golang分布式锁实现,采用Redis+Lua脚本确保原子性,持可重入和自动续期,用于防止超卖及重复下单,具有一定... 目录1 概念应用场景分布式锁必备特性2 思路分析宕机与过期防止误删keyLua保证原子性可重入锁自动

8种快速易用的Python Matplotlib数据可视化方法汇总(附源码)

《8种快速易用的PythonMatplotlib数据可视化方法汇总(附源码)》你是否曾经面对一堆复杂的数据,却不知道如何让它们变得直观易懂?别慌,Python的Matplotlib库是你数据可视化的... 目录引言1. 折线图(Line Plot)——趋势分析2. 柱状图(Bar Chart)——对比分析3