Bug 1538171
| Summary: | Kibana timeout if viewing many (100M) records | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.7.1 | CC: | anli, aos-bugs, jcantril, pportant, rmeggins, sradco |
| Target Milestone: | --- | ||
| Target Release: | 3.7.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The load on the ES cluster is great enough to cause a request from Kibana to timeout before it is able to get a response.
Consequence: No results are returned and Kibana displays an error.
Fix: Modify the kibana image to allow configuration of the request timeout
Result: Kibana is able to retrieve data from Elasticsearch
|
Story Points: | --- |
| Clone Of: | 1530157 | Environment: | |
| Last Closed: | 2018-04-05 09:35:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1530157, 1589905 | ||
| Bug Blocks: | |||
|
Comment 1
Jeff Cantrill
2018-01-24 15:08:32 UTC
Ansible PR to support env setting during deployment: https://github.com/openshift/openshift-ansible/pull/6961 The timeout values can be modified as env in openshift3/logging-kibana/images/v3.7.31-1 The ENV can be set by openshift_logging_kibana_env_vars via openshift-ansible-3.7.29 So move bug to verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0636 |