Bug 1459877 - Hawkular-metrics fails when one instance Cassandra is disabled
Hawkular-metrics fails when one instance Cassandra is disabled
Status: CLOSED DUPLICATE of bug 1459968
Product: OpenShift Container Platform
Classification: Red Hat
Component: Metrics (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: ---
Assigned To: Matt Wringe
Liming Zhou
Depends On:
  Show dependency treegraph
Reported: 2017-06-08 08:35 EDT by Vladislav Walek
Modified: 2017-06-08 14:55 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-06-08 14:55:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vladislav Walek 2017-06-08 08:35:00 EDT
Description of problem:

The metrics are running with two node of Cassandra with each replication controller and pv. However, when you scale down one node, the hawkular will fail with following error:

com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: / 

Where ip is the ip of the pod which was scaled down.
I found that hawkular when starting is attaching the cassandra nodes like this:

08:02:44,344 INFO  [com.datastax.driver.core.Cluster] (ServerService Thread Pool -- 78) New Cassandra host / added
08:02:44,344 INFO  [com.datastax.driver.core.Cluster] (ServerService Thread Pool -- 78) New Cassandra host hawkular-cassandra/ added

Which one os the pod's ip and one svc's ip. However, if the one pod is scaled down, it will show the error above.
Just adding that the replication factor is set to 1.
(com.datastax.driver.core.exceptions.UnavailableException: Not enough replicas available for query at consistency LOCAL_ONE (1 required but only 0 alive)))
(cf. output included)

I know that there is no HA on Cassandra or load balancing, but the issue is hawkular, why it is taking the ip of the pod and not the ip of the service as primary source?

Version-Release number of selected component (if applicable):
OpenShift Container Platform 3.4.0

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 3 Matt Wringe 2017-06-08 14:55:12 EDT
I am marking this as a duplicate of 1459968

*** This bug has been marked as a duplicate of bug 1459968 ***

Note You need to log in before you can comment on or make changes to this bug.