Execute the MongoDB Connection Health Check on Startup

[Inithron]

Description

It would be great if the MongoDB Connection Health Check could be improved.

Current behavior

After startup following health check is displayed:

{
    "status": "UP",
    "checks": [
        {
            "name": "MongoDB connection health check",
            "status": "UP"
        }
    ]
}

But this status is misleading / wrong. Even if no database is available, the status is UP. Only when the application tries to store the first message in the DB, the status goes to down:

{
    "status": "DOWN",
    "checks": [
        {
            "name": "MongoDB connection health check",
            "status": "DOWN",
            "data": {
                "<default>": "KO, reason: Timed out while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Client view of cluster state is {type=UNKNOWN, servers=[{address=localhost:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketOpenException: Exception opening socket}, caused by {java.net.ConnectException: Connection refused: no further information}}]",
                "<default-reactive>": "KO, reason: null"
            }
        }
    ]
}

Improvement

It would be great, if the connection to the DB would be checked on startup and not when the application tries to store the first message in the DB.

Benefit

With this changed approach the pod in Kubernetes would never get green if there is a wrong connection string or the DB is down.

Implementation ideas

No response

[quarkus-bot]

/cc @geoand (kubernetes), @iocanel (kubernetes), @jmartisk (health), @loicmathieu (mongodb), @xstefank (health)

[geoand]

Makes sense IMO

[geoand]

Looking at the code, it should work as expected.

What version of Quarkus are you using?

[Inithron]

I am using 3.17.6
Here is a small reproducer with a unit tests showing the mentioned behavior:

reproducer-for-45482.zip

[geoand]

Thanks!

[geoand]

#45523 fixes the issue