This forum has been archived. All content is frozen. Please use KDE Discuss instead.

ktorrent (2.0.2) snubs only seed (???)

Tags: None
(comma "," separated)
k2
Registered Member
Posts
7
Karma
0
(was having trouble creating an account, so this is redundant with an email)

ktorrent (2.0.2) snubs only seed (???)

In a torrent which is initial seeding, ktorrent seems quite happy to
choke, and afterwards (??) snub the only seed who has data available.

I understand the choking, although it seems overeager to do so when the
incoming data is far below the observed maximum. However, snubbing a
peer which is already choked does not not seem understandable to me.

In any event, the net result is that ktorrent is not an assistive member
of an initial seed situation, acting only as a data sink, not as a data
retransmitter.
k2
Registered Member
Posts
7
Karma
0

Mon Nov 06, 2006 5:10 pm
Oh, FWIW, the initial seed is µTorrent 1.4.0.0.

The really nuts part is when it chokes the only seed causing the data transmission rate to drop to zero, stalling the transmission of in-progress chunks which no other peer posesses.
George
Moderator
Posts
5421
Karma
1

Mon Nov 06, 2006 6:20 pm
Why should we unchoke a seeder ? It has all the chunks, so there is no reason to unchoke it.
jdong
Registered Member
Posts
358
Karma
0

Mon Nov 06, 2006 6:45 pm
Correct me if I'm wrong, but the Choked field indicates whether or not the remote peer has choked you, right?

Also, snubbed is just an indication by your client that the peer has not sent any data to you in 60 seconds... but it does not block the peer from sending you more data, right?
k2
Registered Member
Posts
7
Karma
0

Tue Nov 07, 2006 2:18 am
Huh, it seems the display of attributes across a range of bittorrent clients is not completely consistent in terms of similar names meaning identical things. I guess that's no shock.

I was surprised to find nothing in the logging that had to do with the ongoing transfers with existing peers.
k2
Registered Member
Posts
7
Karma
0

Tue Nov 07, 2006 12:09 pm
These fields seem pretty bizarreo.

For example, I have now been continuously transmitting data to a given peer (ktorrent 2.0.2 as a seed) which is listed Choked: YES for the past 5 minutes.

Are these fields indicitave of anything useful?
lucke
Registered Member
Posts
205
Karma
0

Tue Nov 07, 2006 12:14 pm
Shouldn't you be surprised if you saw that you were downloading from a choked peer?
jdong
Registered Member
Posts
358
Karma
0

Tue Nov 07, 2006 4:11 pm
k2 wrote:These fields seem pretty bizarreo.

For example, I have now been continuously transmitting data to a given peer (ktorrent 2.0.2 as a seed) which is listed Choked: YES for the past 5 minutes.

Are these fields indicitave of anything useful?


Choked means that the peer has choked YOU, so you cannot download from the peer. IT doesn't mean you can't upload to that peer -- in fact, uploading more to that peer will increase the chances of that peer unchoking you.
George
Moderator
Posts
5421
Karma
1

Tue Nov 07, 2006 6:13 pm
lucke wrote:Shouldn't you be surprised if you saw that you were downloading from a choked peer?


No, there was a feature in the fast extensions which would allow you to download a couple of select chunks from a peer who has choked you. This feature has mysteriously dissappeared from the standard.


Bookmarks



Who is online

Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]