redis key过期未删除

redis版本:5.0.3
redis模式:master
Redis的key过期后,又重新设置了过期时间为10秒,key对应的value变成了时间戳。
期望是key过期后再获取该key时,该过期key自动删除,这如何解决?

“重新设置了过期时间为10秒,key对应的value变成了时间戳” 看起来是设置过期时间的命令没用对?
ttl key 查看key还剩多少时间
expire key seconds 设置seconds秒后key过期
set key val [EX seconds] EX是指定过期时间,放[]是表示可选。执行set key val后,key的内容变成val,且key永不过期。你是否用了这个?

  • 你可以参考下这个问题的回答, 看看是否对你有帮助, 链接: https://ask.csdn.net/questions/7758350
  • 我还给你找了一篇非常好的博客,你可以看看是否有帮助,链接:redis的key与value乱码问题
  • 除此之外, 这篇博客: Redis源码分析:过期key删除与设置key的过期时间中的 过期key删除 部分也许能够解决你的问题, 你可以仔细阅读以下内容或跳转源博客中阅读:
  • 检查键的是否过程主要是通过在获取到key时,然后获取key时,来判断该key是否已经过期。在getCommand中,会调用到如下流程

    void getCommand(client *c) {
        getGenericCommand(c);
    }
    
    int getGenericCommand(client *c) {
        robj *o;
    
        if ((o = lookupKeyReadOrReply(c,c->argv[1],shared.nullbulk)) == NULL)  // 先查找该key
            return C_OK;
    
        if (o->type != OBJ_STRING) {
            addReply(c,shared.wrongtypeerr);
            return C_ERR;
        } else {
            addReplyBulk(c,o);
            return C_OK;
        }
    }
    
    robj *lookupKeyReadOrReply(client *c, robj *key, robj *reply) {
        robj *o = lookupKeyRead(c->db, key);    // 查找该key
        if (!o) addReply(c,reply);
        return o;
    }
    
    robj *lookupKeyRead(redisDb *db, robj *key) {
        return lookupKeyReadWithFlags(db,key,LOOKUP_NONE);
    }
    

    在lookupKeyReadWithFlags函数中,有该expireIfNeeded来判断是否过期删除;

    int expireIfNeeded(redisDb *db, robj *key) {
        if (!keyIsExpired(db,key)) return 0;                                        // 检查是否是过期了 如果没有过期则返回0
    
        /* If we are running in the context of a slave, instead of
         * evicting the expired key from the database, we return ASAP:
         * the slave key expiration is controlled by the master that will
         * send us synthesized DEL operations for expired keys.
         *
         * Still we try to return the right information to the caller,
         * that is, 0 if we think the key should be still valid, 1 if
         * we think the key is expired at this time. */
        if (server.masterhost != NULL) return 1;
    
        /* Delete the key */
        server.stat_expiredkeys++;
        propagateExpire(db,key,server.lazyfree_lazy_expire);            
        notifyKeyspaceEvent(NOTIFY_EXPIRED,
            "expired",key,db->id);
        return server.lazyfree_lazy_expire ? dbAsyncDelete(db,key) :
                                             dbSyncDelete(db,key);              // 判断是通过惰性删除还是同步删除
    }
    

    这就是在获取的过程中来删除已经过期的key,删除的过程中既要在数据库中保存的数据删除还需要在过期字典中删除。

    从以上流程可知,设置key的过期都是设置了过期时间之后就执行完成,此时,还需要知道什么时候会去检查哪些key过期了呢,什么时候去检查呢,答案就是在Redis服务器启动的时候,初始化了一个serverCron函数,定时执行;在该函数中有如下过程;

    databasesCron  -> activeExpireCycle
    

    activeExpireCycle函数就是删除对应过期key的执行函数;

    void activeExpireCycle(int type) {
        /* This function has some global state in order to continue the work
         * incrementally across calls. */
        static unsigned int current_db = 0; /* Last DB tested. */
        static int timelimit_exit = 0;      /* Time limit hit in previous call? */
        static long long last_fast_cycle = 0; /* When last fast cycle ran. */
    
        int j, iteration = 0;
        int dbs_per_call = CRON_DBS_PER_CALL;
        long long start = ustime(), timelimit, elapsed;
    
        /* When clients are paused the dataset should be static not just from the
         * POV of clients not being able to write, but also from the POV of
         * expires and evictions of keys not being performed. */
        if (clientsArePaused()) return;
    
        if (type == ACTIVE_EXPIRE_CYCLE_FAST) {                                     // 是否是快速的过期
            /* Don't start a fast cycle if the previous cycle did not exit
             * for time limit. Also don't repeat a fast cycle for the same period
             * as the fast cycle total duration itself. */
            if (!timelimit_exit) return;                                                // 如果过期时间不存在则返回
            if (start < last_fast_cycle + ACTIVE_EXPIRE_CYCLE_FAST_DURATION*2) return;
            last_fast_cycle = start;                                                    // 开始时间设置成最后一次时间
        }
    
        /* We usually should test CRON_DBS_PER_CALL per iteration, with
         * two exceptions:
         *
         * 1) Don't test more DBs than we have.
         * 2) If last time we hit the time limit, we want to scan all DBs
         * in this iteration, as there is work to do in some DB and we don't want
         * expired keys to use memory for too much time. */
        if (dbs_per_call > server.dbnum || timelimit_exit)
            dbs_per_call = server.dbnum;                                                // 限制访问的数据库数量
    
        /* We can use at max ACTIVE_EXPIRE_CYCLE_SLOW_TIME_PERC percentage of CPU time
         * per iteration. Since this function gets called with a frequency of
         * server.hz times per second, the following is the max amount of
         * microseconds we can spend in this function. */
        timelimit = 1000000*ACTIVE_EXPIRE_CYCLE_SLOW_TIME_PERC/server.hz/100;           // 获取过期的时间限制值
        timelimit_exit = 0;
        if (timelimit <= 0) timelimit = 1;
    
        if (type == ACTIVE_EXPIRE_CYCLE_FAST)
            timelimit = ACTIVE_EXPIRE_CYCLE_FAST_DURATION; /* in microseconds. */       // 转换成微秒
    
        /* Accumulate some global stats as we expire keys, to have some idea
         * about the number of keys that are already logically expired, but still
         * existing inside the database. */
        long total_sampled = 0;
        long total_expired = 0;
    
        for (j = 0; j < dbs_per_call && timelimit_exit == 0; j++) {                     // 遍历对应的数据库 检查是否需要停止
            int expired;
            redisDb *db = server.db+(current_db % server.dbnum);                        // 获取对应的数据库
    
            /* Increment the DB now so we are sure if we run out of time
             * in the current DB we'll restart from the next. This allows to
             * distribute the time evenly across DBs. */
            current_db++;
    
            /* Continue to expire if at the end of the cycle more than 25%
             * of the keys were expired. */
            do {
                unsigned long num, slots;
                long long now, ttl_sum;
                int ttl_samples;
                iteration++;
    
                /* If there is nothing to expire try next DB ASAP. */
                if ((num = dictSize(db->expires)) == 0) {                               // 获取过期字典列表 如果该数据库没有过期字典则停止
                    db->avg_ttl = 0;
                    break;
                }
                slots = dictSlots(db->expires);
                now = mstime();
    
                /* When there are less than 1% filled slots getting random
                 * keys is expensive, so stop here waiting for better times...
                 * The dictionary will be resized asap. */
                if (num && slots > DICT_HT_INITIAL_SIZE &&
                    (num*100/slots < 1)) break;
    
                /* The main collection cycle. Sample random keys among keys
                 * with an expire set, checking for expired ones. */
                expired = 0;
                ttl_sum = 0;
                ttl_samples = 0;
    
                if (num > ACTIVE_EXPIRE_CYCLE_LOOKUPS_PER_LOOP)
                    num = ACTIVE_EXPIRE_CYCLE_LOOKUPS_PER_LOOP;             // 获取过期key的次数
    
                while (num--) {
                    dictEntry *de;
                    long long ttl;
    
                    if ((de = dictGetRandomKey(db->expires)) == NULL) break;        // 随机获取key
                    ttl = dictGetSignedIntegerVal(de)-now;                          
                    if (activeExpireCycleTryExpire(db,de,now)) expired++;           // 如果超时了则过期删除掉
                    if (ttl > 0) {
                        /* We want the average TTL of keys yet not expired. */
                        ttl_sum += ttl;                                             // 如果没有过期则获取过期时间
                        ttl_samples++;
                    }
                    total_sampled++;
                }
                total_expired += expired;                                           // 加上已经删除的key的数量
    
                /* Update the average TTL stats for this database. */
                if (ttl_samples) {
                    long long avg_ttl = ttl_sum/ttl_samples;
    
                    /* Do a simple running average with a few samples.
                     * We just use the current estimate with a weight of 2%
                     * and the previous estimate with a weight of 98%. */
                    if (db->avg_ttl == 0) db->avg_ttl = avg_ttl;
                    db->avg_ttl = (db->avg_ttl/50)*49 + (avg_ttl/50);               // 更新平均过期的比率
                }
    
                /* We can't block forever here even if there are many keys to
                 * expire. So after a given amount of milliseconds return to the
                 * caller waiting for the other active expire cycle. */
                if ((iteration & 0xf) == 0) { /* check once every 16 iterations. */
                    elapsed = ustime()-start;
                    if (elapsed > timelimit) {
                        timelimit_exit = 1;
                        server.stat_expired_time_cap_reached_count++;
                        break;
                    }
                }
                /* We don't repeat the cycle if there are less than 25% of keys
                 * found expired in the current DB. */
            } while (expired > ACTIVE_EXPIRE_CYCLE_LOOKUPS_PER_LOOP/4);             // 如果找到的值过期的比率不足25%则停止
        }
    
        elapsed = ustime()-start;
        latencyAddSampleIfNeeded("expire-cycle",elapsed/1000);                      // 设置执行消耗的时间
    
        /* Update our estimate of keys existing but yet to be expired.
         * Running average with this sample accounting for 5%. */
        double current_perc;
        if (total_sampled) {
            current_perc = (double)total_expired/total_sampled;
        } else
            current_perc = 0;
        server.stat_expired_stale_perc = (current_perc*0.05)+
                                         (server.stat_expired_stale_perc*0.95);
    }
    

    该函数主要分两种情况下的删除;

    1. 快速删除,即该函数将尝试不超过一定时间内不重复执行的策略,即不超过两个1000微秒
    2. 慢删除,即通过时间限制为REDIS_HZ周期的百分比,来执行删除的过期key

    通过随机的抽取百分之二十五的key来达到删除过期key的目的,从而保证了一些过期的key在很久不访问时占用内存资源。