I found a description about BZ59274:
There are about 12 caches which does not have any HITs. The caches will
show HITs when the cache is cleared but later the problem reappears
after few weeks.
I don't know what the means, but hopefully you can decipher it.
BTW - we are on #traffic-sever on irc.freenode.net if you want to chat...
-Bryan
On 11/11/2009 03:56 PM, Bryan Call wrote:
There was some work done by a consulting group when I first join the
group a couple years ago. Part of the project was for them to supply
bug fixes they did in their version of the source tree.
We might be able to lookup the bug numbers. I might have had a
spreadsheet with information about it.
-Bryan
On 11/11/2009 03:43 PM, John Plevyak wrote:
Weird. Here are the comments that prompted me:
Cache.cc: prev_recover_pos = 0; //Bug fixed by YTS Team,
yamsat BZ 59274
Cache.cc: if (recover_pos == prev_recover_pos) //Bug fixed by YTS
Team, yamsat BZ59274
Cache.cc: goto Lclear; //Bug fixed by YTS Team,
yamsat BZ59274
Cache.cc: prev_recover_pos = recover_pos; //Bug fixed by YTS
Team, yamsat BZ59274
P_CachePart.h: ink_off_t prev_recover_pos; //Bug fixed by YTS
Team, yamsat BZ59274
Leif Hedstrom wrote:
On 11/11/2009 04:14 PM, John Plevyak wrote:
Would it be possible for me to see bug report BZ59274 and follow up
discussion?
I'd like to understand the situation better.
Hmmm, is that an old Inktomi bug? We don't have those, I'm prety
sure :/. I checked the Yahoo Bugzilla, and that ticket number is
something unrelated to TS. :)
-- leif
