漫话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客户端连接机制的实现方案

《Redis客户端连接机制的实现方案》本文主要介绍了Redis客户端连接机制的实现方案,包括事件驱动模型、非阻塞I/O处理、连接池应用及配置优化,具有一定的参考价值,感兴趣的可以了解一下... 目录1. Redis连接模型概述2. 连接建立过程详解2.1 连php接初始化流程2.2 关键配置参数3. 最大连

Redis MCP 安装与配置指南

《RedisMCP安装与配置指南》本文将详细介绍如何安装和配置RedisMCP,包括快速启动、源码安装、Docker安装、以及相关的配置参数和环境变量设置,感兴趣的朋友一起看看吧... 目录一、Redis MCP 简介二、安www.chinasem.cn装 Redis MCP 服务2.1 快速启动(推荐)2.

Redis中Stream详解及应用小结

《Redis中Stream详解及应用小结》RedisStreams是Redis5.0引入的新功能,提供了一种类似于传统消息队列的机制,但具有更高的灵活性和可扩展性,本文给大家介绍Redis中Strea... 目录1. Redis Stream 概述2. Redis Stream 的基本操作2.1. XADD

Knife4j+Axios+Redis前后端分离架构下的 API 管理与会话方案(最新推荐)

《Knife4j+Axios+Redis前后端分离架构下的API管理与会话方案(最新推荐)》本文主要介绍了Swagger与Knife4j的配置要点、前后端对接方法以及分布式Session实现原理,... 目录一、Swagger 与 Knife4j 的深度理解及配置要点Knife4j 配置关键要点1.Spri

Redis出现中文乱码的问题及解决

《Redis出现中文乱码的问题及解决》:本文主要介绍Redis出现中文乱码的问题及解决,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1. 问题的产生2China编程. 问题的解决redihttp://www.chinasem.cns数据进制问题的解决中文乱码问题解决总结

Redis的持久化之RDB和AOF机制详解

《Redis的持久化之RDB和AOF机制详解》:本文主要介绍Redis的持久化之RDB和AOF机制,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录概述RDB(Redis Database)核心原理触发方式手动触发自动触发AOF(Append-Only File)核

Redis分片集群、数据读写规则问题小结

《Redis分片集群、数据读写规则问题小结》本文介绍了Redis分片集群的原理,通过数据分片和哈希槽机制解决单机内存限制与写瓶颈问题,实现分布式存储和高并发处理,但存在通信开销大、维护复杂及对事务支持... 目录一、分片集群解android决的问题二、分片集群图解 分片集群特征如何解决的上述问题?(与哨兵模

SpringBoot连接Redis集群教程

《SpringBoot连接Redis集群教程》:本文主要介绍SpringBoot连接Redis集群教程,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录1. 依赖2. 修改配置文件3. 创建RedisClusterConfig4. 测试总结1. 依赖 <de

SpringBoot+Redis防止接口重复提交问题

《SpringBoot+Redis防止接口重复提交问题》:本文主要介绍SpringBoot+Redis防止接口重复提交问题,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不... 目录前言实现思路代码示例测试总结前言在项目的使用使用过程中,经常会出现某些操作在短时间内频繁提交。例

Redis 配置文件使用建议redis.conf 从入门到实战

《Redis配置文件使用建议redis.conf从入门到实战》Redis配置方式包括配置文件、命令行参数、运行时CONFIG命令,支持动态修改参数及持久化,常用项涉及端口、绑定、内存策略等,版本8... 目录一、Redis.conf 是什么?二、命令行方式传参(适用于测试)三、运行时动态修改配置(不重启服务