Hello there,

I'm testing the db_redis with usrloc module in mode 3 and i have been noticing that every time that kamailio checks if there is contacts expired then it logs the following warning messages:

WARNING: PR_LOG: 5a14aea50d9d9b17-75@172.31.1.11: db_redis [redis_dbase.c:1099]: db_redis_perform_query(): performing full table scan on table 'location' while performing query
WARNING: PR_LOG: 5a14aea50d9d9b17-75@172.31.1.11: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 0 is 'expires'
WARNING: PR_LOG: 5a14aea50d9d9b17-75@172.31.1.11: db_redis [redis_dbase.c:1102]: db_redis_perform_query(): scan key 1 is 'expires'
WARNING: PR_LOG: 5a14aea50d9d9b17-75@172.31.1.11: db_redis [redis_dbase.c:1274]: db_redis_perform_delete(): performing full table scan on table 'location' while performing delete
WARNING: PR_LOG: 5a14aea50d9d9b17-75@172.31.1.11: db_redis [redis_dbase.c:1277]: db_redis_perform_delete(): scan key 0 is 'expires'
WARNING: PR_LOG: 5a14aea50d9d9b17-75@172.31.1.11: db_redis [redis_dbase.c:1277]: db_redis_perform_delete(): scan key 1 is 'expires'

I'm not sure what is the rational behind of this, but having these logs being written when we have log level equal 2 in production is something unnecessary, so i'm asking if it shouldn't be better we have it as debug instead of warning? or do you forecast any performance issues using usrloc module in mode 3 with db_redis?

Thank you for your support

Cheers

José

Cumprimentos

José Seabra