ReplyError: ERR SETTINGS_KEY_NOT_FOUND when use in Clustering mode with Redis 7.x about bottleneck

[mfrye]

Just ran into this as well

[menbatisiunissart]

same issue here as well

[avermeil]

Getting this same error as well:

ReplyError: ERR SETTINGS_KEY_NOT_FOUND
    at parseError (/usr/api/node_modules/redis-parser/lib/parser.js:179:12)
    at parseType (/usr/api/node_modules/redis-parser/lib/parser.js:302:14) {
  command: 'EVALSHA',
  args: [
    '8bd3e064b718321194a8df49c69e48fd0ffb4dcd',
    8,
    'b_builtwith_throttler_settings',
    'b_builtwith_throttler_job_weights',
    'b_builtwith_throttler_job_expirations',
    'b_builtwith_throttler_job_clients',
    'b_builtwith_throttler_client_running',
    'b_builtwith_throttler_client_num_queued',
    'b_builtwith_throttler_client_last_registered',
    'b_builtwith_throttler_client_last_seen',
    1665586647495,
    'b9zz33fpice'
  ],
  code: 'ERR'
}

[yarinvak]

We're also experiencing it with bitnami/redis:7.0.4-debian-11-r4, any workaround? @SGrondin

[ricardofrancoli]

Same here:

ReplyError: ERR SETTINGS_KEY_NOT_FOUND
  command: 'EVALSHA',
  args: [
    '8bd3e064b718321194a8df49c69e48fd0ffb4dcd',
    8,
    'b_awql_throttler_settings',
    'b_awql_throttler_job_weights',
    'b_awql_throttler_job_expirations',
    'b_awql_throttler_job_clients',
    'b_awql_throttler_client_running',
    'b_awql_throttler_client_num_queued',
    'b_awql_throttler_client_last_registered',
    'b_awql_throttler_client_last_seen',
    1665734323793,
    '0efrswlefrmj'
  ],
  code: 'ERR'
}

[nlopez99]

We're experiencing this on an elasticache redis instance running 6.2.6, any updates on this? @SGrondin

[HelloKashif]

It's probably happening because of the heartbeat check which validates that keys exist on redis. But since Groups timeout kills the limiter after timeout those keys don't exist anymore.

bottleneck/src/Scripts.coffee

Line 84 in b835283

headers: ["validate_keys", "validate_client", "process_tick"]

The error usually goes away once the group_check.lua runs so a quick hack would be ignore the error for a while until it goes away

[dobrynin]

Also ran into this. Between this issue and ETIMEDOUT errors, it's been very difficult to get ioredis cleanly working w/ ElastiCache 😢