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

[Lucas Ponce]

+1

The WARNING message is correct as the component cannot connect to Cassandra, so, I don't remove those messages.

But as TH says, it's a matter of how to define the embedded cassandra in this scenario to be up and running before that the components.

Lucas

----- Original Message -----
> From: "Thomas Heute" <theute at redhat.com>
> To: "Discussions around Hawkular development" <hawkular-dev at lists.jboss.org>
> Sent: Monday, July 27, 2015 11:42:04 AM
> Subject: Re: [Hawkular-dev] Could not connect to Cassandra ... - does it have to be a WARN with a stack trace?
> 
> Glad I am not the only one that finds those messages annoying :)
> 
> Indeed, this is an Hawkular issue with embedded Cassandra.
> We should fix it by properly defining the startup dependencies, we may also
> think of keeping "embedded Cassandra" as a separate process.
> 
> The idea of "embedding Cassandra" is that we don't need to ask users to go
> download it, "install it" and run it.
> But we could consider having a Cassandra in a different process (configured
> for our needs such as the data location, port and other settings) that is
> required to be started prior to run Hawkular (Hawkular would need to fail
> quickly and clearly if the user "forgot" to start Cassandra).
> 
> PS: I am not advocating for one or the other solution as I don't know the
> advantages/drawbacks of both solutions
> 
> Thomas
> 
> 
> 
> 
> 
> On 07/27/2015 11:11 AM, Michael Burman wrote:
> > 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 at redhat.com>
> > To: "Discussions around Hawkular development"
> > <hawkular-dev at 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> > _______________________________________________
> > hawkular-dev mailing list
> > hawkular-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hawkular-dev
> >
> 
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>