Health Check configuration

188 views
Skip to first unread message

rob.va...@gmail.com

unread,
Mar 19, 2018, 12:22:00 PM3/19/18
to Kill Bill users mailing-list
Hi,

In our development environment we are working with RDS. However we are running on a average small database so we sometimes encounter that the Health Check 'osgi-pool-Connection99Percent' is failing.

The health-check is integrated into our target groups and if it is unhealthy we reboot the service. So this kinda annoying that it is rebooting all the time.

Is there any way to update this treshold from 50ms to another value, based on the environment? Perhaps set it in a docker environment variable or something like that?

Kind regards
Rob


{
"com.codahale.metrics.health.jvm.ThreadDeadlockHealthCheck": {
"healthy": true
},
"main.pool.Connection99Percent": {
"healthy": true
},
"main.pool.ConnectivityCheck": {
"healthy": true
},
"org.killbill.billing.server.healthchecks.KillbillHealthcheck": {
"healthy": true,
"message": "OK"
},
"osgi.pool.Connection99Percent": {
"healthy": false,
"message": "99th percentile connection wait time of 281ms exceeds the threshold 50ms"
},
"osgi.pool.ConnectivityCheck": {
"healthy": true
},
"shiro.pool.Connection99Percent": {
"healthy": true
},
"shiro.pool.ConnectivityCheck": {
"healthy": true
}
}

Message has been deleted
Message has been deleted

Pierre-Alexandre Meyer

unread,
Mar 20, 2018, 6:49:30 AM3/20/18
to Rob Van Pamel, Kill Bill users mailing-list
Hi Rob,

You can configure the thresholds via the following properties:


These properties aren't exposed as environment variables on our 0.18.x Docker images, so you would need a custom killbill.properties file (e.g. bind mount) at $KILLBILL_CONFIG/killbill.properties.

Hope that helps,


--
You received this message because you are subscribed to the Google Groups "Kill Bill users mailing-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to killbilling-users+unsubscribe@googlegroups.com.
To post to this group, send email to killbilling-users@googlegroups.com.
Visit this group at https://groups.google.com/group/killbilling-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/killbilling-users/bf49fdc9-9647-4392-a2e3-966e240492b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Pierre

stephane brossier

unread,
Mar 22, 2018, 11:08:03 PM3/22/18
to rob.va...@gmail.com, Kill Bill users mailing-list
Rob,


We have exposed some of the configuration properties through docker as explained in this documentation. However, the property `org.killbill.dao.leakDetectionThreshold` has not been exposed so you would need to create an overlay (`kpm.yml.erb.overlay`) in your docker image -- see test here.

Stéphane


On Tue, Mar 20, 2018 at 2:37 AM, <rob.va...@gmail.com> wrote:

Hi,

I found that you could increase this value of 50ms to something higher (maybe not an ideal solution but for development this should work)

https://github.com/killbill/killbill-commons/blob/master/jdbi/src/main/java/org/killbill/commons/jdbi/guice/DaoConfig.java#L56

Can we update this value via a docker variable or how should we do this actually? Is there a file we should copy to the image and create a new docker image. If so, is this described somewhere?

Kind regards
  Rob

Op maandag 19 maart 2018 17:22:00 UTC+1 schreef rob.va...@gmail.com:
--
You received this message because you are subscribed to the Google Groups "Kill Bill users mailing-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to killbilling-users+unsubscribe@googlegroups.com.
To post to this group, send email to killbilling-users@googlegroups.com.
Visit this group at https://groups.google.com/group/killbilling-users.
Reply all
Reply to author
Forward
0 new messages