Bug 1464854 - Timeout exception while retrieving configuration in ES pod log
Summary: Timeout exception while retrieving configuration in ES pod log
Keywords:
Status: CLOSED DUPLICATE of bug 1457642
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-26 05:52 UTC by Junqi Zhao
Modified: 2017-08-16 19:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-06-27 13:59:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
es log (48.71 KB, text/plain)
2017-06-26 05:52 UTC, Junqi Zhao
no flags Details
ansible inventory file (562 bytes, text/plain)
2017-06-26 05:52 UTC, Junqi Zhao
no flags Details

Description Junqi Zhao 2017-06-26 05:52:28 UTC
Created attachment 1291849 [details]
es  log

Description of problem:
Deployed logging via ansible, Timeout exception in ES log
java.util.concurrent.TimeoutException: Timeout after 30SECONDS while retrieving configuration for [config, roles, rolesmapping, internalusers, actiongroups](index=.searchguard.logging-es-ops-data-master-920fz5ed)
	at com.floragunn.searchguard.configuration.ConfigurationLoader.load(ConfigurationLoader.java:97)
	at com.floragunn.searchguard.action.configupdate.TransportConfigUpdateAction.nodeOperation(TransportConfigUpdateAction.java:262)
	at com.floragunn.searchguard.action.configupdate.TransportConfigUpdateAction.nodeOperation(TransportConfigUpdateAction.java:62)
	at org.elasticsearch.action.support.nodes.TransportNodesAction.nodeOperation(TransportNodesAction.java:93)
	at org.elasticsearch.action.support.nodes.TransportNodesAction$NodeTransportHandler.messageReceived(TransportNodesAction.java:229)
	at org.elasticsearch.action.support.nodes.TransportNodesAction$NodeTransportHandler.messageReceived(TransportNodesAction.java:225)
	at com.floragunn.searchguard.ssl.transport.SearchGuardSSLTransportService.messageReceivedDecorate(SearchGuardSSLTransportService.java:172)
	at com.floragunn.searchguard.transport.SearchGuardTransportService.messageReceivedDecorate(SearchGuardTransportService.java:191)
	at com.floragunn.searchguard.ssl.transport.SearchGuardSSLTransportService$Interceptor.messageReceived(SearchGuardSSLTransportService.java:113)
	at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:77)
	at org.elasticsearch.transport.TransportService$4.doRun(TransportService.java:378)
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

Version-Release number of selected component (if applicable):
# openshift version
openshift v3.6.122
kubernetes v1.6.1+5115d708d7
etcd 3.2.0

Images from brew registry
# docker images | grep logging
logging-kibana          v3.6                fd67e351dadf        2 days ago          342.4 MB
logging-elasticsearch   v3.6                1006eb106849        2 days ago          404.6 MB
logging-auth-proxy      v3.6                301fd39f57e0        2 days ago          229.6 MB
logging-fluentd         v3.6                dba31f5b54ba        2 days ago          232.5 MB
logging-curator         v3.6                a0148dd96b8d        2 weeks ago         221.5 MB

How reproducible:
Always

Steps to Reproduce:
1. Deploy logging via ansible
2. Check ES pod's log
3.

Actual results:
TimeoutException in ES pod's log

Expected results:
Should be no exception in ES pod's log

Additional info:
Attached inventory file and ES pod's log

Comment 1 Junqi Zhao 2017-06-26 05:52:56 UTC
Created attachment 1291850 [details]
ansible inventory file

Comment 2 Jeff Cantrill 2017-06-27 14:00:12 UTC

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


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