This should affect on-prem workflow, especially where a universe has previously been created using the same nodes
While creating a new cluster in-universe and the following error appears under a "failed uptime" health check:
Invalid uptime 238519 247305
The cause of this error is due to the extra running process of tserver and master which are also known as the “Zombie” process
This issue occurs when there are rogue or leftover processes running on the server, creating conflicting time values and causing the health check to have conflicting data.
Tservers may fail to start if the pid file is corrupted.
- Run the following command
# confirm if the following command returns more than one PID
# here should only be a single tserver or master proccess
ps -C <process_name> -o etimes=
[yugabyte@yb-1-user-identity-2-n1 ~]$->ps -C yb-tserver -o etimes=
[yugabyte@yb-1-user-identity-2-n1 ~]$->ps -C yb-master -o etimes=
As shown above, an example shows 2-yb-master and 2 yb-tserver. There should be only one.
2. Kill the extra process running in yb-master and yb-server:
3. confirm the output now has a single PID
[yugabyte@yb-1-user-identity-2-n1 ~]$ ps -C yb-tserver -o etimes=
[yugabyte@yb-1-user-identity-2-n1 ~]$ ps -C yb-master -o etimes=
If the above actions do not result in a successful Universe creation, please open a ticket with Yugabyte Support.
What does etimes means?
etime is elapsed time since the process was started, in the form [[DD-]hh:]mm:ss. etimes ELAPSED elapsed time since the process was started, in seconds