View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000040 | Timekoin Server | General Issue | public | 2012-07-11 07:36 | 2012-08-03 16:23 |
| Reporter | warmach | Assigned To | KnightMB | ||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.6 | ||||
| Target Version | 2.41 | Fixed in Version | 2.41 | ||
| Summary | 0000040: "Do Not Purge" status lost | ||||
| Description | A peer's "Do Not Purge" status is lost when the timekoin server restarts. | ||||
| Steps To Reproduce | 1. Set a peer to "Do Not Purge", a first contact is good example 2. Clear the peer list (simulates system shutdown or extended loss of network connectivity) 3. Stop Timekoin 4. Start Timekoin 5. Go to peer list and see status of previously selected peer | ||||
| Tags | No tags attached. | ||||
|
|
In step 2 where you clear the peer list, are you removing all peers (including the ones in blue)? |
|
|
Clear the list yes, but using the "X" may not be right as if you are doing that you are intentionally clearing the peer list. In my case, I have several old computers that have stability issues. They either restart or lockup, usually at night when I'm not watching them. Regardless, they are off the network for more than 5 minutes. When I start the server again, it re-establishes the peers. Those that were blue (do not purge) are no longer blue. I have to into the edit screen to reset them. How ever you want to simulate that, feel free. |
|
|
Ah, the reason those peers are lost on restart is because all peers in the list are stored in RAM and not in the actual database. The peerlist gets a lot of activity (updates, deletes, inserts, etc.) so to avoid hitting the disk so much for the activity, those tables were moved into RAM. You can technically change them back to disk to help with the restart issue you are having. This command will do it in the mysql console when the timekoin database is selected: ALTER TABLE `active_peer_list` ENGINE = MYISAM; |
|
|
As a side note, we will look at the performance difference between the two modes of RAM and Disk. It might be useful to have a way for the user to switch between the two. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-07-11 07:36 | warmach | New Issue | |
| 2012-07-11 11:28 | KnightMB | Note Added: 0000032 | |
| 2012-07-11 12:13 | warmach | Note Added: 0000033 | |
| 2012-07-11 12:19 | KnightMB | Note Added: 0000034 | |
| 2012-07-11 12:19 | KnightMB | Assigned To | => KnightMB |
| 2012-07-11 12:19 | KnightMB | Status | new => acknowledged |
| 2012-07-11 12:22 | KnightMB | Note Added: 0000035 | |
| 2012-08-03 16:23 | KnightMB | Status | acknowledged => closed |
| 2012-08-03 16:23 | KnightMB | Resolution | open => no change required |
