0005374: sessions: geographically separated data-centeres use case.

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0005374

[Resin]

minor

always

02-19-13 15:19

02-26-13 10:38

Reporter

alex

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

4.0.35

Summary

0005374: sessions: geographically separated data-centeres use case.

Description

rep by Keith J Paulson
-Our apps are running in 2-3 geographically separated datacenters.
-We use a common db2 database, so session are synced via it.

Additional Information

Attached Files

Relationships

Notes
(0006193) alex 02-19-13 16:07 edited on: 02-19-13 16:08	>Do you plan on using single Resins in all locations or Clustered Resins? (feel free to add this to the bug report or I can do that when you reply) We currently run them all as single, but with a common session store, so they all operate like a cluster spanning the 2-3 datacenters. Our load is managed by a cisco GSS, via DNS, so we cannot ensure a client is sticky to a specific datacenter; that is the root of our session issues.

(0006199) ferg 02-26-13 10:38	server/01jd

Issue History
Date Modified	Username	Field	Change
02-19-13 15:19	alex	New Issue
02-19-13 15:48	copart	Issue Monitored: copart
02-19-13 16:07	alex	Note Added: 0006193
02-19-13 16:08	alex	Note Edited: 0006193
02-19-13 16:08	alex	Description Updated
02-26-13 10:38	ferg	Note Added: 0006199
02-26-13 10:38	ferg	Assigned To	=> ferg
02-26-13 10:38	ferg	Status	new => closed
02-26-13 10:38	ferg	Resolution	open => fixed
02-26-13 10:38	ferg	Fixed in Version	=> 4.0.36

Mantis 1.0.0rc3[^]

35 total queries executed.
28 unique queries executed.