1078747 - Please change the timers.connectionDuration and callDuration on loop-server

Status: RESOLVED INVALID

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Description

[Mark Banner (:standard8)]

On loop-server for production, please change the config values:

timers.connectionDuration to 60
callDuration to 80

https://github.com/mozilla-services/loop-server/blame/master/loop/config.js#L282
https://github.com/mozilla-services/loop-server/blame/master/loop/config.js#L308

This is a temporary workaround for bug 1073410 and other related issues. By increasing the connectionDuration, we're hoping to give folks more time to accept the get user media prompt. It will still cause bug 1073410 to be hit if the user takes too long.

Comment 1

[Mark Banner (:standard8)]

(In reply to Mark Banner (:standard8) from comment #0)
> timers.connectionDuration to 60
> callDuration to 80

I meant 30 seconds for timers.connectionDuration. cullDuration is correct at 80 seconds.

Comment 2

[Bob Micheletto [:bobm]]

These configuration changes have been manually patched into the running loop-server application servers for a production Break/Fix.  A pull request will be submitted shortly to the primary Cloud Operations personnel to make it permanent.  

Notes: 
1. The timers.connectionDuration has been set to 30, as we initially requested, and later verified, in the loop-server IRC channel.
2. The timers.connectionDuration setting has been configured in the settings.json file not directly through config.js.
3. The default for the callDuration setting was patched directly into the config.js file.

Comment 3

[Bob Micheletto [:bobm]]

Pull request sent for part of configuration change:
https://github.com/mozilla-services/puppet-config/pull/909

The config.js file is part of the loop-server RPM, and will have to wait for a new RPM to be built with change in the callDuration parameter.  That is unless it can be overridden in the settings.json file.

Comment 4

[James Bonacci [:jbonacci]]

Is this currently in Stage and Production (manually patched)?
Is this a *permanent* change for loop-server with the upcoming release 0.12.4?
REF
Stage: https://bugzilla.mozilla.org/show_bug.cgi?id=1078293
Prod: https://bugzilla.mozilla.org/show_bug.cgi?id=1078664

Comment 5

[Rémy Hubscher (:natim)]

This is now fixed in production for a long time.