Re: [Deluge] #1395: Same rank trackers should all be announced (was: [lt.sess_set.announce_to_all_tiers] Same rank trackers should all be announced)
Deluge
------------------------------+------------------------------------
Reporter: TooCh0za | Owner:
Type: feature-request | Status: new
Priority: minor | Milestone: 2.x
Component: Core | Version: 1.3.1
Resolution: | Keywords: multi-tracker announce
------------------------------+------------------------------------
Comment (by Cas):
There is a helpful implementation in [https://github.com/deluge-
torrent/deluge/pull/319 PR 319] but I want to gain some clarity on this
topic since the PR is attempting to enable `announce_to_all_trackers`
which matches the description of announcing to all trackers within a tier.
However I do not think this is correct setting to use since tiers are
meant to be load-balanced and runs the risk of client being banned if
announcing to every tracker in a tier.
I think the sane approach is to use `announce_to_all_tiers` that mimics
the existing uT spec.
== Relevant reading ==
libtorrent documentation
* http://libtorrent.org/single-page-ref.html
> `announce_to_all_trackers` controls how multi tracker torrents are
treated. If this is set to true, all trackers in the same tier are
announced to in parallel. If all trackers in tier 0 fails, all trackers in
tier 1 are announced as well. If it's set to false, the behavior is as
defined by the multi tracker specification.
>
> `announce_to_all_tiers` also controls how multi tracker torrents are
treated. When this is set to true, one tracker from each tier is announced
to. This is the uTorrent behavior. To be compliant with the Multi-tracker
specification, set it to false.
Transmission client discussion
* https://trac.transmissionbt.com/ticket/1699
* https://trac.transmissionbt.com/attachment/ticket/1699/dwk-lord-mmn-
log.txt
> each tier should be assumed to operate as a single tracker and assumed
to communicate amongst themselves as far as peerlists are concerned the
"backup" tiers are separate trackers that have no knowledge of the peers
on the primary or other tiers
!BitTorrent spec discussion
* https://github.com/bittorrent/bittorrent.org/issues/82
> I believe opentracker does data replication via multicast between
multiple nodes that ought to be published within the same tier. So
treating a single tier as load-balancing frontends would be correct in
that case.
* https://www.bittorrent.org/beps/bep_0012.html
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/1395#comment:9>
Deluge <https://deluge-torrent.org/>
Deluge Project