Probable initial delay problem in registering process

[ElieFrancis1]

Hello, I have a random problem on a microservice that has other dependencies. The most important one in terms of initialization time is "hibernate". So, sometimes, the registering process doesn't work. A warning in the log displays the unreachable url. Example :

2022-11-17 09:40:50,555 WARNING [io.qua.eur.reg.EurekaRegistrationService$RegistrationFlow] (pool-8-thread-1) Health check not reachable: http://192.168.3.110:8112/q/health/well

But when I call the same url uising "curl", it works without any problem : curl http://192.168.3.110:8112/q/health/well { "status": "UP", "checks": [ ] }

On other microservices that don't use hibernate, I don't have this problem. Do you think that it is caused by the hard-coded initial delay at this line ? https://github.com/fmcejudo/quarkus-eureka/blob/53c85275c44cd532cf6e91174fc3c5056006edca/quarkus-eureka/src/main/java/io/quarkus/eureka/registration/EurekaRegistrationService.java#L85

Is it possible to make this delay configurable ?

[n-pickering]

I can confirm that if I change 3L to 30L it is able to register, when at 3L it was not able to.

• +1 for having this be configurable,
• or waiting for /q/health/well to respond before starting this process, see https://github.com/fmcejudo/quarkus-eureka/blob/53c85275c44cd532cf6e91174fc3c5056006edca/quarkus-eureka/src/main/java/io/quarkus/eureka/registration/EurekaRegistrationService.java#L67?

[fmcejudo]

Thanks @efrancis59 @n-pickering for reporting this issue, we can take a look how to make this time configurable.