View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000008 | Timekoin Server | Performance Issue | public | 2012-06-21 23:21 | 2012-06-22 16:33 |
| Reporter | KnightMB | Assigned To | KnightMB | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.1 | ||||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0000008: Bogus or duplicate transaction not filtered from the queue | ||||
| Description | The transaction queue can fill up with bogus or duplicate transactions. The transactions are never recorded as they are eventually purged, but it still waste processing time to do it. | ||||
| Steps To Reproduce | Happens when another peer isn't purging it's queue properly and has stale transactions that get replicated across the network every cycle. | ||||
| Tags | No tags attached. | ||||
|
|
The queue manager normally just checks for a valid transaction by testing out the keys and hashes. But the timestamp is usually ignored, thus old transactions can land in the queue even though they will be purged when it comes time to enter them in the transaction history due to being duplicates. The additional server overhead can be saved if the stale transactions are filtered from ever entering the system to begin with. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-06-21 23:21 | KnightMB | New Issue | |
| 2012-06-21 23:21 | KnightMB | Status | new => assigned |
| 2012-06-21 23:21 | KnightMB | Assigned To | => KnightMB |
| 2012-06-21 23:24 | KnightMB | Note Added: 0000008 | |
| 2012-06-21 23:24 | KnightMB | Status | assigned => confirmed |
| 2012-06-22 16:33 | KnightMB | Status | confirmed => resolved |
| 2012-06-22 16:33 | KnightMB | Fixed in Version | 2.41 => 1.2 |
| 2012-06-22 16:33 | KnightMB | Resolution | open => fixed |
