subject:"\[Bug 55929\] Separate replica datacenter causes high query latency"

[Bug 55929] Separate replica datacenter causes high query latency

2014-03-06 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 Jesse (Pathoschild) wmb...@pathoschild.com changed: What|Removed |Added Status|RESOLVED|VERIFIED

[Bug 55929] Separate replica datacenter causes high query latency

2014-03-05 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 Tim Landscheidt t...@tim-landscheidt.de changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 55929] Separate replica datacenter causes high query latency

2014-03-05 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #8 from Nemo federicol...@tiscali.it --- Pathos, please mark this VERIFIED when you've migrated your tools and confirmed they run as fast as they should. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 55929] Separate replica datacenter causes high query latency

2014-03-05 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 Cyberpower678 cybernet...@yahoo.com changed: What|Removed |Added CC|

[Bug 55929] Separate replica datacenter causes high query latency

2014-03-05 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #10 from Cyberpower678 cybernet...@yahoo.com --- (In reply to Cyberpower678 from comment #9) (In reply to Tim Landscheidt from comment #7) Okay, closing then. (Well, FIXED doesn't quite fit it, but I think it's appropriate

[Bug 55929] Separate replica datacenter causes high query latency

2014-03-04 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #6 from Jesse (Pathoschild) wmb...@pathoschild.com --- Tool authors can now migrate to the new infrastructure[1], which resolves this issue. [1]: http://lists.wikimedia.org/pipermail/labs-l/2014-March/002160.html -- You are

[Bug 55929] Separate replica datacenter causes high query latency

2014-02-10 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 Nemo federicol...@tiscali.it changed: What|Removed |Added Blocks||61037 -- You are

[Bug 55929] Separate replica datacenter causes high query latency

2014-01-23 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #3 from silke.me...@wikimedia.de --- What has become of this issue since you moved Tool Labs in December? Is it still valid? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 55929] Separate replica datacenter causes high query latency

2014-01-23 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #4 from Nemo federicol...@tiscali.it --- (In reply to comment #3) What has become of this issue since you moved Tool Labs in December? Is it still valid? Yes, except that it got 50 % slower in the meanwhile: Page generated in

[Bug 55929] Separate replica datacenter causes high query latency

2014-01-23 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #5 from Jesse (Pathoschild) wmb...@pathoschild.com --- The latest timeline is now mid-March; the last blocker is the OpenStack setup by a contractor. See discussion at

[Bug 55929] Separate replica datacenter causes high query latency

2013-12-23 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 Nemo federicol...@tiscali.it changed: What|Removed |Added Blocks||58791 -- You are

[Bug 55929] Separate replica datacenter causes high query latency

2013-12-23 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 Nemo federicol...@tiscali.it changed: What|Removed |Added See Also|

[Bug 55929] Separate replica datacenter causes high query latency

2013-12-04 Thread bugzilla-daemon

https://bugzilla.wikimedia.org/show_bug.cgi?id=55929 --- Comment #2 from Jesse PW (Pathoschild) pathoschild+wmb...@gmail.com --- The latest timeline for this is mid-January[1], but all Toolserver accounts have been set to expire in early January[2]. Tool authors waiting for this ticket should