Bug 1027564 - TestCaseRunStatus cached in a non thread-safe way
Summary: TestCaseRunStatus cached in a non thread-safe way
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.8.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Yang Ren
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-07 06:13 UTC by Chaobin Tang
Modified: 2014-10-20 02:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-20 02:18:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Chaobin Tang 2013-11-07 06:13:21 UTC
Description of problem:

In 3.8.5, as a quick solution to the performance headache in aggregating the progress for one testrun, the case_run_status is cached using a class level dictionary which basically is a global variable. In a shared-nothing environment such as Apache WSGI, this is a thread-unsage. Because in one process, this dictionary gets outdated, it doesn't in other running processes.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Need to change it to a thread-safe way. Possible solution might be to utilize a robust caching backend, such as memcached or better redis.

Comment 1 cqi 2013-11-18 03:52:26 UTC
Related to 1027589

Comment 4 fhuang 2014-10-20 02:18:34 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1027589 has been modified.


Note You need to log in before you can comment on or make changes to this bug.