Re: [Hawkular-dev] Could not connect to Cassandra ... - does it have to be a WARN with a stack trace?
Hi,
And how would you distinguish between real warning and incorrect one? This message is not
printed when Hawkular-Metrics starts standalone andshould not be removed. This is a
container issue in Hawkular and should be fixed there (so that no such error happens)
instead of breaking the logging in metrics. Most likely this happens with
embedded-cassandra I guess?
- Micke
----- Original Message -----
From: "Peter Palaga" <ppalaga(a)redhat.com>
To: "Discussions around Hawkular development"
<hawkular-dev(a)lists.jboss.org>
Sent: Monday, July 27, 2015 11:59:27 AM
Subject: [Hawkular-dev] Could not connect to Cassandra ... - does it have to be a WARN
with a stack trace?
Hi *,
There are several occurrences of this in every Hawkular start log:
WARN [org.hawkular.metrics.api.jaxrs.MetricsServiceLifecycle]
(metricsservice-lifecycle-thread) Could not connect to Cassandra cluster
- assuming its not up yet:
com.datastax.driver.core.exceptions.NoHostAvailableException: All
host(s) tried for query failed (tried: /127.0.0.1:9042
(com.datastax.driver.core.TransportException: [/127.0.0.1:9042] Cannot
connect))
plus the stack trace.
So given that this happens during every HK startup, could we not
classify it as normal and change it to INFO without the stack trace?
I am ready to prepare a PR unless somebody raises a hand against that.
Thanks,
Peter
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev