Bug 1726433
| Summary: | kibana presenting blank page or timeout | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.11.0 | CC: | anli, aos-bugs, jcantril, jfoots, mirollin, rmeggins, rsandu, stwalter |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The dynamic seeding is inefficient and user's with visibility to a large number of projects exposes this issue by making too many calls to the Elasticsearch cluster. Additionally, there is no caching for user requests causing the seeding process to occur more frequently.
Consequence: Calls to Elasticsearch can timeout before a response is returned.
Fix: Introduce caching of the API calls and ACL seeding
Result: Dynamic seeding is more efficient reducing the opportunity for page timeouts.
|
Story Points: | --- |
| Clone Of: | 1705589 | Environment: | |
| Last Closed: | 2019-07-23 19:56:39 UTC | Type: | --- |
| 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: | 1644008, 1705589, 1726434 | ||
| Bug Blocks: | |||
|
Comment 1
Jeff Cantrill
2019-07-02 20:18:03 UTC
*** Bug 1722218 has been marked as a duplicate of this bug. *** Couldn't reproduce this issue. Regression pass. move to verified. openshift3/ose-logging-kibana5:v3.11.128 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-2019:1753 |