Deluge 1.3.14 (same "issue" with 1.3.13 though)
LibTorrent 1.0.11.0
OS: Windows 10 x64
Plugins: ltConfig
Greetings,
I've got Deluge set up to only allow one torrent downloading at a time. This is to avoid files "colliding" since at times torrents containing the same files are added.
One thing I'm struggling with in this scenario is that if two torrents with the same files are added within a certain time span, the second torrent will start hash checking immediately even though it's still queued.
This causes the second torrent to start downloading a most of the files once it's removed even though they already exist.
How I expect it to work is that once the first torrent is finished the queued one will get active and start hashing and then immediately start seeding unless there's files that differ.
Is there any way around this issue? I'm guessing it's not considered a bug but rather a feature request.
Regards,
MH
Torrent hashes when added in queued state
-
- Member
- Posts: 19
- Joined: Wed Mar 08, 2017 5:08 pm
-
- Member
- Posts: 19
- Joined: Wed Mar 08, 2017 5:08 pm
Re: Torrent hashes when added in queued state
Is this a bug (in which case I'll create a bug report) or by design?
If it controlled by Deluge or libtorrent?
If it controlled by Deluge or libtorrent?
Re: Torrent hashes when added in queued state
-
- Member
- Posts: 19
- Joined: Wed Mar 08, 2017 5:08 pm
Re: Torrent hashes when added in queued state
I appreciate the reply Cas.
If I'm reading the above information correctly, it would indeed have the potential to solve the issue I am trying to work around.
However, my question is regarding the work around I would like to do that's not working as expected, which is, why a torrent added in queued state is hash-checked immediately instead of once it's that specific torrents turn to start download?
Descriptions of the scenario (one torrent currently downloading and the limit is one active download):
Currently: Add > Hash-check on files > Queued > Download
Expected: Add > Queued > Hash-check on files > Download
If I'm reading the above information correctly, it would indeed have the potential to solve the issue I am trying to work around.
However, my question is regarding the work around I would like to do that's not working as expected, which is, why a torrent added in queued state is hash-checked immediately instead of once it's that specific torrents turn to start download?
Descriptions of the scenario (one torrent currently downloading and the limit is one active download):
Currently: Add > Hash-check on files > Queued > Download
Expected: Add > Queued > Hash-check on files > Download
Re: Torrent hashes when added in queued state
Torrents are hash-checked upon adding to determine what pieces are required and whether to download or seed, this is controlled by libtorrent.
-
- Member
- Posts: 19
- Joined: Wed Mar 08, 2017 5:08 pm
Re: Torrent hashes when added in queued state
Thanks for clearing that up and thanks for a great software!