Environment

• Yugabyte Platform - 2.6, 2.8. 2.10, 21.12

Issue

Some older versions of Yugabyte enabled Yedis by default. During upgrades, node adds, etc. it’s possible that YugabyteDB Anywhere may enable health checks for Yedis even though it is not in use. These health checks may fail, leading to spurious health check failures.

For Ex: Health check error :

"FailedConnectivity with redis-cli". 

ps -ef | grep tserver
/home/yugabyte/tserver/bin/redis-cli -h 10.185.8.20 -p 6379 ping
yugabyte 11927 1 0 Oct09 ? 00:00:00 bash -c set -o pipefail;

 Additional Information: 

• Please be sure to review the validation steps prior to making any changes to your cluster. As a general recommendation, always take a backup of the config file via the `get_universe_config` command for future reference, should it be needed.

Warning:

• Some caution is needed here, as these changes to metadata should only be done with the assistance of Yugabyte Support.
  
  

Resolution

Overview

The procedure below can be used to disable Yedis health checks by editing the universe_details_json in the Yugaware Postgres database

Steps

1. Before starting, take a backup of the Platform database using yb_platform_backup.sh using the steps in the link below:

https://docs.yugabyte.com/preview/yugabyte-platform/administer-yugabyte-platform/back-up-restore-yp

2. Connect to the platform Postgres Database:

$sudo docker exec -it postgres psql -U postgres yugaware 

3. Check whether the enableYEDIS value is set in the universe_details_json in the Postgres database:

$SELECT universe_details_json::jsonb->'clusters'->0->'userIntent'->'enableYEDIS' AS enableYEDIS FROM universe WHERE name = '<universe_name>';

4. If the above configuration parameter is true for any Universe where Yedis should not be enabled, it will need to be updated to false.

Start a transaction and make the update:

$BEGIN;
UPDATE universe
SET universe_details_json = jsonb_set(universe_details_json::jsonb, '{clusters, 0, userIntent, enableYEDIS }', 'false') 
WHERE name = '<universe_name>';

5. Check if the update looks good (no typos, etc.):

$SELECT universe_details_json::jsonb->'clusters'->0->'userIntent'->'enableYEDIS' AS enableYEDIS FROM universe WHERE name = '<universe_name>';

6. After Updating the Universe, now commit the transaction.

$COMMIT;