[CORE-241] Queries will immediately move to the next queue when timeout is < or = to 0 Created: 23/Nov/16 Updated: 09/Dec/16 Resolved: 23/Nov/16 |
|
| Status: | Closed |
| Project: | i2b2 Core Software |
| Component/s: | CRC Cell |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.08a |
| Type: | Improvement | Priority: | Major |
| Reporter: | Janice Donahoe | Assignee: | Janice Donahoe |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Rank: | 0|hzzzzg:i |
| Sprint: | Release 1.7.08a Sprint |
| i2b2 Feature/s: |
Queries
|
| i2b2 Sponsored Project/s: |
i2b2 Core
|
| Affects Database/s: |
All databases
|
| Testing Notes: | This improvement was tested with the following scenarios.
1. Timeout set to -1. 2. Timeout set to 0. 3. Timeout set to 100 as well as the default settings of 14400 and 43200. No issues were found during the testing. |
| Participant/s: |
| Description |
|
The amount of time a query will run before timing out is defined in the crc.properties file. There are three properties, one for each queue (small, medium, and large).
Currently, if the timeout settings for any of these queues was defined as 0 or -1, the CRC would attempt to run the query and then it would time out. This improvement will change that process. When the timeout is set to anything less than or equal to 0 the CRC will no longer attempt to run the process. The query will be immediately moved to the next queue to begin the process of running the query in that queue. |
| Comments |
| Comment by Janice Donahoe [ 09/Dec/16 ] |
| The change for this issue was included in the 1.7.08a release. |