Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Thanks for reviews. Merging this.
Actually if one designs the 'keys' right for a db_redis table, should get no full table scans (I think, at least from my tests so far). So then will get no warnings after this merge.
Full table scans are actually dangerous because consume alot of kamailio PKG memory. So if one's db_redis table is big, and full scans are performed => kamailio processes won;t be able to load it in the first palce. So the WARNING for performing full table scan is still there, because of this.
Tip: For location table in db_redis i got no full table scans anymore (e.g. when contact expires or when user contacts is queried) when using this key definition:
modparam("db_redis", "keys", "location=entry:ruid&usrdom:username,domain&timer:expires")
... because index info is added in redis for 'user@domain' or for user's contact 'expires' so only those ones need to be scanned and iterated => no full scans needed
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.