而在享受

会将大部分无关的逻辑和异常场景进行省略因为整个过程会涉及到大量

Redis

同样是用来存放响应客户端的数据ListclientReplyBlock

reply;

(如果有的话)设置事件轮询的阻塞前和阻塞后执行的函数启动事件轮询,

进入一个死循环,

各个属性进行默认值设置initServerConfig();//

解析命令行参数//

这里会对这些参数进行解析处理parsingCommandLineArguments();//

redisServer

beforeSleepaeSetBeforeSleepProc(server.el,beforeSleep);//

向事件轮询注册

afterSleepaeSetAfterSleepProc(server.el,afterSleep);//

启动事件轮询,

删除事件轮询aeDeleteEventLoop(server.el);return

redisServer

readQueryFromClientregisterClientFdReadFilesEvent();//

初始化

*3\r\n$3\r\nset\r\n$5\r\nmyKey\r\n$7\r\nmyValue\r\n

5.2

*3\r\n$3\r\nset\r\n$5\r\nmyKey\r\n$7\r\nmyValue\r\n,

服务端会

*3\r\n$3\r\nset\r\n$5\r\nmyKey\r\n$7\r\nmyValue\r\n,

client

*3\r\n$3\r\nset\r\n$5\r\nmyKey\r\n$7\r\nmyValue\r\n,

RESP

readQueryFromClient(aeEventLoop

*el,

中putRequestContentIntoClientQueryBuffer();//

querybuf

就关闭这个连接checkClientQueryBufferMoreThanOneGb();//

临时暂停这次请求,

客户端被暂停了temporaryPaurseThisRequest();//

mult

parseRequestContentIntoClientArgvByRequestType();//

}//

https://redis.io/resources/modules/moduleCallCommandFilters(c);//

argv[0]

lookupCommand(c-argv[0]-ptr);//

null

不符合就返回错误commandNullAndArgumentsNumberCheck(c-cmd

c-argc);//

返回错误requirePassCheckWhenCmdNotAuth(c-authenticated,

c-cmd);//

通知客户端重定向redirectClientIfNeedByKeyWhenClusterEnabled();//

lua

就尝试释放内存tryToReleaseMemoryWhenSetMaxMemoryAndNoLuaScriptTimeout();//

磁盘检测失败,

失败了pingAndWriteCommandsDeniedByDiskErrorByMaster();//

主从复制配置检查//

返回错误writeCommandsDeniedByMinSlavesNumberReply();//

10.

返回错误writeCommandDeniedBySlaveReadOnly();//

11.

返回错误subscribeClientCanHandleCommandCheck();//

12.

返回错误slaveSynchronizingOrConnectStateUnusualCheck();//

13.

commandIsNotExecAndDiscardAndMultiAndWatch())

{//

服务端执行的命令会同步传输给客户端sendCommandToMonitors();//

18.

如果需要进行统计记录latencyAddSampleIfNeeded();//

20.

慢日志记录slowlogPushEntryIfNeeded();//

21.

MAXMEMORY_FLAG_NO_SHARED_INTEGERS

(涉及

tryObjectEncoding(c-argv[2]);//

key

expireTimesetExpireTimeIfNeed(c-db,

c-argv[1],

表明当前的客户端有数据需要响应putCurrentClientToClientsPendingWriteIfNeed();//

将响应内容

replytryWriteResponseToBufOrReply();//

reply

关闭当前客户端checkClientOutputBufferLimitsWhenWriteToReply();

}逻辑概括如下:

sendReplyToClient事件轮询获取这个可写事件并触发

sendReplyToClient

处理带有输出缓冲区的客户端handleClientsWithPendingWrites();......

}int

handleClientsWithPendingWrites(void)

{client

getNextNodeFromLinkList(server.clients_pending_write))

{//

链表中删除removeTheClientFromeClientsPendingWrite(c);//

(client-buf

sendReplyToClientregistFileEventForClientWhenClientHaveDataToWrite(c);}

}7.2

的输出缓冲区有数据需要发送while(clientHasPendingReplies(c))

{//

同时从双写链表中删除这个节点writeDataToClientIfClientReplyHasData();}//

1024*64if

(currentHaveSendMoreThanMaxLimit())

{//

(haveSetMaxMemoryAndCurrentUsedMemoryLessThanMaxMemory())

{break;}//

从事件轮询中删除当前的发送数据事件delCurrentFileEventFromEventLoop();}//

client