Regression from 23.07 to 24.05 on model count lifecycle/restarts about server HOT 1 OPEN

@kthui @Tabrizian Any idea if this is an intended behaviour ? I want to make sure that unhealthy processes are restarted correctly , but playing with kill it seems that they're not.

When kill -9 : The process is killed and never restarts on new requests. The killed process tries to execute the jobs but remains hanging after this log :

I0620 11:06:12.646654 1013474 python_be.cc:1395] "model large_3, instance large_3_0_0, executing 1 requests"

When kill -11 : The process is killed, and try to restart after end of next request, resulting sometimes segfault and Triton server crashing with error code 137 and Signal 11 received. The other behaviour that can happen when sending this signal is the same as the -9 : executing one request and hanging on forever.

from server.