[QA environment] RedisClient::CannotConnectError

[christinach]

What maintenance needs to be done?

Investigate why we get so many RedisClient::CannotConnectError in QA

Level of urgency

• [ ] High
• [x] Moderate
• [ ] Low

EOL upgrade

• [ ] EOL Date MM/DD/YYYY

Why is this maintenance needed?

• We get errors in [honeybadger](RedisClient::CannotConnectError: Connection timed out - user specified timeout (redis://lib-redis-qa1.princeton.edu:6379/6) since 4/17/2024 with the message RedisClient::CannotConnectError: Connection timed out - user specified timeout (redis://lib-redis-qa1.princeton.edu:6379/6). See if we need to update anything in the connection between bibdata qa and redis-qa.
• Also related to honeybadger error RedisClient::ReadTimeoutError

• Acceptance criteria

  • [ ] The [honeybadger error RedisClient::CannotConnectError: Connection timed out]( - user specified timeout (redis://lib-redis-qa1.princeton.edu:6379/6) stops triggering
  • [ ] The honeybadger error RedisClient::ReadTimeoutError

Implementation notes, if any