[Hawkular-dev] Could not connect to Cassandra ... - does it have to be a WARN with a stack trace?

[Gary Brown]

Could it be changed to generate INFO until the first connection is made, and after that if the same issue occurs, then raise a WARN?

Regards
Gary

----- Original Message -----
> 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>