Got an error messages from hawkular-metrics

Question

Got an error messages from hawkular-metrics

YunSangJun opened this issue 5 years ago · comments

I got an error messages from hawkular-metrics pod.

‘Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: hawkular-cassandra/x.x.x.x:x (com.datastax.driver.core.exceptions.BusyPoolException: [hawkular-cassandra/x.x.x.x] Pool is busy (no available connection and the queue has reached its max size 256)))

I found a same case from redhat knowledge center.
I did the solution but same error is still occured.
https://access.redhat.com/solutions/3260071

Environment information
-Openshift version: 3.11
-Docker image version: docker.io/openshift/origin-metrics-hawkular-metrics:v3.11.0

OpenShift Bot · Answer 1 · Wed Sep 23 2020 01:12:54 GMT+0800 (China Standard Time)

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

OpenShift Bot · Answer 2 · Sat Oct 24 2020 03:08:15 GMT+0800 (China Standard Time)

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

OpenShift Bot · Answer 3 · Mon Nov 23 2020 04:57:37 GMT+0800 (China Standard Time)

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

OpenShift CI Robot · Answer 4 · Mon Nov 23 2020 04:57:52 GMT+0800 (China Standard Time)

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.