# We use start period of 30s to avoid marking the container unhealthy on slow or contended CI hosts.
#
# If in production, you have a 30s startup, please report to https://gitter.im/openzipkin/zipkin
# including the values of the /health and /info endpoints as this would be unexpected.
HEALTHCHECK --interval=5s --start-period=30s --timeout=5s CMD ["docker-healthcheck"]
Hi all, just joined to the tracing world and already i have a question.
So we have just setup 2 zipkin servers with 5 node cassandra and 3 node kafka. We can receive/store traces without issues. But when i try to search traces with min or max duration parameter set, server gives
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /10.110.220.8:9042 (com.datastax.driver.core.exceptions.BusyPoolException: [/10.110.220.8:9042] Pool is busy (no available co
nnection and the queue has reached its max size 40960)), /10.110.220.9:9042 (com.datastax.driver.core.exceptions.BusyPoolException: [/10.110.220.9:9042] Pool is busy (no available connection and the queue has reached its max size 40960)), /10.110.220.6:9042 (com.datastax.
driver.core.exceptions.BusyPoolException: [/10.110.220.6:9042] Pool is busy (no available connection and the queue has reached its max size 40960)), /10.110.220.7:9042, /10.110.220.5:9042 [only showing errors of first 3 hosts, use getErrors() for more details])
errors. Im not sure where to look for debugging so i am open to suggestions.
Also we currently cant calculate dependencies because cron jobs not finishing before the next one starts. So this issue might be related to performance of our cassandra cluster.
cassandra: 3.11.8,
zipkin: 2.21
Thanks,
Hello everyone! :) I've just started instrumenting some services at work and hit a snag. I'm trying to work out what's best practice when creating a new span. The wording in https://zipkin.io/pages/instrumenting.html is a little ambiguous to me. Should I be creating a new span before I make a request (and send the new spanId with that request) or should the server receiving that request start a new span? I gather the choice is also up to me, but I'm wondering what the common pattern is.
Thanks in advance!