一次Redis的使用Bug记要(exec)
一次Redis的使用Bug记录(exec)
博主在一次项目中,使用了工具类中的Redis类,因为该Redis没有封装管道pipeline和exec命令,所以就大笔一挥来了一段__call;
代码如下(其中$this->_connect()返回的为一个Redis实例)。
之后的事情感觉中文已经无法表述,上代码就是类似这样的
$redis->pipeline();
$redis->lpop($key);
$redis->lpop($key);
$redis->exec();
自己写了简单例子测试之后,正常情况下应该会返回$key队列中的两个栈顶元素,即array('item1','item2');但是该次最终的返回结果竟然是NULL,博主这时候
就超级疑惑,难道是call_user_fun_array()这个申请的函数是木有返回值,尼玛,那这样不是坑死老爹吗。而这仅仅是个人猜测,php宝册在手不虚,发现并无此
说明,但是有一个简单的例子为,看下面的例子加亲自测试是有返回值,那就是说此次猜想不成功。
好吧,只能继续debug了,许久之后依然木有发现问题,请教公司一同事,他来了之后发现你说那就既然是$this->_connect()是一个redis对象,
那上面不是还有一个$this->_redis的句柄吗,直接替换,之后在神奇的事情发生了,尼玛有返回值了。
好吧,那问题就可以猜想一二了,这个肯定说明了$this->_connect()和$this->_redis肯定有哪些地方不太一样,如上面的代码,我们直接把两个变量dump了出来。
之后发现是这样的,如下图看官们应该明白这根本是不同的两个资源。
感觉知道问题所在了,返回了看_connect()函数,发现里面是没有Redis单例的,每次都是new了一个Redis对象。
所以还不知道问题所在的看官可以继续跟着哥往下走。
这个问题呢,我们技术人啥也不说了,上代码,在一批redis的操作命令中,动用了三个不同的redis对象,第三次是直接exec,连pipeline都木有,那肯定是NULL.
这你敢相信,反正我是信了,我也是醉了,当然也是我自己坑了自己。问题到此真相大白。有一次自坑的打怪之路。

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Redis cluster mode deploys Redis instances to multiple servers through sharding, improving scalability and availability. The construction steps are as follows: Create odd Redis instances with different ports; Create 3 sentinel instances, monitor Redis instances and failover; configure sentinel configuration files, add monitoring Redis instance information and failover settings; configure Redis instance configuration files, enable cluster mode and specify the cluster information file path; create nodes.conf file, containing information of each Redis instance; start the cluster, execute the create command to create a cluster and specify the number of replicas; log in to the cluster to execute the CLUSTER INFO command to verify the cluster status; make

How to clear Redis data: Use the FLUSHALL command to clear all key values. Use the FLUSHDB command to clear the key value of the currently selected database. Use SELECT to switch databases, and then use FLUSHDB to clear multiple databases. Use the DEL command to delete a specific key. Use the redis-cli tool to clear the data.

To read a queue from Redis, you need to get the queue name, read the elements using the LPOP command, and process the empty queue. The specific steps are as follows: Get the queue name: name it with the prefix of "queue:" such as "queue:my-queue". Use the LPOP command: Eject the element from the head of the queue and return its value, such as LPOP queue:my-queue. Processing empty queues: If the queue is empty, LPOP returns nil, and you can check whether the queue exists before reading the element.

Using the Redis directive requires the following steps: Open the Redis client. Enter the command (verb key value). Provides the required parameters (varies from instruction to instruction). Press Enter to execute the command. Redis returns a response indicating the result of the operation (usually OK or -ERR).

Using Redis to lock operations requires obtaining the lock through the SETNX command, and then using the EXPIRE command to set the expiration time. The specific steps are: (1) Use the SETNX command to try to set a key-value pair; (2) Use the EXPIRE command to set the expiration time for the lock; (3) Use the DEL command to delete the lock when the lock is no longer needed.

On CentOS systems, you can limit the execution time of Lua scripts by modifying Redis configuration files or using Redis commands to prevent malicious scripts from consuming too much resources. Method 1: Modify the Redis configuration file and locate the Redis configuration file: The Redis configuration file is usually located in /etc/redis/redis.conf. Edit configuration file: Open the configuration file using a text editor (such as vi or nano): sudovi/etc/redis/redis.conf Set the Lua script execution time limit: Add or modify the following lines in the configuration file to set the maximum execution time of the Lua script (unit: milliseconds)

Use the Redis command line tool (redis-cli) to manage and operate Redis through the following steps: Connect to the server, specify the address and port. Send commands to the server using the command name and parameters. Use the HELP command to view help information for a specific command. Use the QUIT command to exit the command line tool.

In Debian systems, readdir system calls are used to read directory contents. If its performance is not good, try the following optimization strategy: Simplify the number of directory files: Split large directories into multiple small directories as much as possible, reducing the number of items processed per readdir call. Enable directory content caching: build a cache mechanism, update the cache regularly or when directory content changes, and reduce frequent calls to readdir. Memory caches (such as Memcached or Redis) or local caches (such as files or databases) can be considered. Adopt efficient data structure: If you implement directory traversal by yourself, select more efficient data structures (such as hash tables instead of linear search) to store and access directory information
