Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1538171 - Kibana timeout if viewing many (100M) records
Kibana timeout if viewing many (100M) records
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.1
Unspecified Unspecified
unspecified Severity high
: ---
: 3.7.z
Assigned To: Jeff Cantrill
Anping Li
:
Depends On: 1530157 1589905
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-24 10:07 EST by Jeff Cantrill
Modified: 2018-06-11 11:47 EDT (History)
6 users (show)

See Also:
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 05:35:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/origin-aggregated-logging/pull/905 None None None 2018-01-24 10:07 EST
Github openshift/origin-aggregated-logging/pull/913 None None None 2018-01-24 10:08 EST
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:35 EDT

  None (edit)
Comment 3 Jeff Cantrill 2018-02-01 09:35:48 EST
Ansible PR to support env setting during deployment: https://github.com/openshift/openshift-ansible/pull/6961
Comment 4 Anping Li 2018-02-25 01:40:56 EST
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.
Comment 8 errata-xmlrpc 2018-04-05 05:35:31 EDT
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

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