Bug 1007458

Summary: [RFE] Be able to change the timeout in console/app/models/rest_api/base.rb
Product: OpenShift Container Platform Reporter: Nick Harvey <niharvey>
Component: RFEAssignee: Dan McPherson <dmcphers>
Status: CLOSED WONTFIX QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2.1CC: aos-bugs, bleanhar, cpelland, erich, jokerman, libra-onpremise-devel, lmeyer, mmccomas, niharvey
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-15 20:52:52 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:

Description Nick Harvey 2013-09-12 14:14:56 UTC 
Description of problem: 

There is a timeout hard coded in console/app/models/rest_api/base.rb that the customer would like to change in their OSE env.


Version-Release number of selected component (if applicable): 1.2


Expected results:
Be able to extend that value if necessary.
Comment 2 Luke Meyer 2014-02-17 15:12:33 UTC 
I assume you're talking about the idle/open/read timeouts under class ActiveResource::Connection::Base. At least, looking at a 2.0 installation, that's what I see.

I think those can already be configured. Nick, do you have time to try this out?

It's not documented anywhere, but poking through the code it looks like you can set these with options in the console conf like:

    BROKER_API_IDLE_TIMEOUT=4
    BROKER_API_OPEN_TIMEOUT=3
    BROKER_API_READ_TIMEOUT=240

I would assume the same for 1.2.

If so, we should probably mention it in the console conf example...
Comment 4 Luke Meyer 2014-10-10 16:16:39 UTC 
Customer case is long closed. Add the values above in console.conf we ship and test them out. Consider a kbase or adding to the component timeouts section of the docs (probably only need BROKER_API_READ_TIMEOUT here -- the others have defaults that should serve in most cases and would just be distracting).