Sometimes, for a second at the beginning of a crawl,
the crawl elapsed time shows a false, large interval.
(It's ~ 303,000 hours, about the time since 1970.)
This seems to be due to the fact that the StatTracker
thread hasn't done its initiailization by the time
other threads are asking for data.
The ordering of statracker initiatialization should be
adjusted to avoid this timing issue.
Gordon Mohr
None
1.6.0
Public
|
Date: 2007-03-14 00:15
|
|
Date: 2005-09-08 23:32 Logged In: YES |
|
Date: 2005-05-17 20:30 Logged In: YES |
|
Date: 2004-10-20 21:55 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| artifact_group_id | None | 2005-09-23 18:01 | gojomo |
| status_id | Open | 2005-09-08 23:32 | gojomo |
| close_date | 2004-10-20 21:55 | 2005-09-08 23:32 | gojomo |
| resolution_id | Accepted | 2005-09-08 23:32 | gojomo |
| resolution_id | Fixed | 2005-05-17 20:30 | gojomo |
| status_id | Closed | 2005-05-17 20:30 | gojomo |
| summary | timing issue on crawl-start & run-time stat | 2005-05-17 20:30 | gojomo |
| status_id | Open | 2004-10-20 21:55 | gojomo |
| close_date | - | 2004-10-20 21:55 | gojomo |
| assigned_to | nobody | 2004-10-20 21:55 | gojomo |
| resolution_id | None | 2004-10-20 21:55 | gojomo |
| priority | 5 | 2004-09-01 21:57 | gojomo |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use