Bug 1064106

Summary:	Copy Trans times out with large enough documents
Product:	[Retired] Zanata	Reporter:	Carlos Munoz <camunoz>
Component:	Component-CopyTrans	Assignee:	Carlos Munoz <camunoz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2	CC:	djansen, ecohen, hpeters, sflaniga, zanata-bugs
Target Milestone:	---
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.3.0-SNAPSHOT (20140218-0947)	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-20 05:47:43 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:
Embargoed:

Description Carlos Munoz 2014-02-12 02:58:48 UTC

Description of problem:
When running copy trans against a large document, it is possible that the process will fail due to a transaction timeout error.

Version-Release number of selected component (if applicable):
3.2.x

How reproducible:
Sometimes - If the document is large enough.

Steps to Reproduce:
1. Upload or push a large document.
2. Run copy trans on the version (UI), or let the client run copy trans.

Actual results:
If the document is large enough, it will fail due to a transaction timeout.

Expected results:
Copy trans finishes successfully.

Comment 1 Carlos Munoz 2014-02-12 03:17:39 UTC

Made copy trans operate on batches so that even large documents are handled properly. There is still very small possibility of a batch taking way too long and timing out the transaction, but it is very low.

See:
https://github.com/zanata/zanata-server/pull/372

Comment 2 Damian Jansen 2014-02-18 02:30:32 UTC

43 minutes in and still going (ETA 1 day, 6 hours, 23 mins)

Verified at 1bf60cc19d6941929f586c3e8d62390fbb41644d

Comment 7 Sean Flanigan 2014-03-20 05:47:43 UTC

Closing VERIFIED bugs for Zanata server 3.3.2.