0001676: Need something in 3.1 for equivalent functionality of bind-ports-after-start

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001676

[Resin]

minor

always

04-10-07 12:34

01-16-08 12:04

Reporter

sam

View Status

public

Assigned To

ferg

Priority

urgent

Resolution

fixed

Status

closed

Product Version

3.1.0

Summary

0001676: Need something in 3.1 for equivalent functionality of bind-ports-after-start

Description

(rep by S Pannell)

We have a problem with our production application server that we would
like to deploy live. Basically we have a Production and Standby resin
instances running. When the production is down the standby takes over all
requests. This is working. However, there is one really nasty problem.
If the Production instance is down and then we start the production
instance all requests appear to be directly to the starting production
server before it has finished starting up. This means all requests are
hanging waiting for the production instance to start-up (which can take 5
minutes). During this time the site is unavailable.

Additional Information

In 3.0 this issue is solved by setting bind-ports-after-start.

Attached Files

Relationships

Notes
(0001922) ferg 05-15-07 15:08	In Pro, now use listen() to wait until the server completes initialization before listening.

(0002654) sam 01-16-08 12:03	fix made it into 3.1.3, not 3.1.2

Issue History
Date Modified	Username	Field	Change
04-10-07 12:34	sam	New Issue
05-15-07 11:39	copart	Issue Monitored: copart
05-15-07 15:08	ferg	Note Added: 0001922
05-15-07 15:08	ferg	Assigned To	=> ferg
05-15-07 15:08	ferg	Status	new => closed
05-15-07 15:08	ferg	Resolution	open => fixed
05-15-07 15:08	ferg	Fixed in Version	=> 3.1.2
01-16-08 12:02	sam	Resolution	fixed => reopened
01-16-08 12:03	sam	Resolution	reopened => open
01-16-08 12:03	sam	Note Added: 0002654
01-16-08 12:04	sam	Resolution	open => fixed

Mantis 1.0.0rc3[^]

33 total queries executed.
28 unique queries executed.