You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/04/06 22:38:25 UTC

[jira] [Updated] (TS-4221) Truncated objects in the cache

     [ https://issues.apache.org/jira/browse/TS-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-4221:
------------------------------
    Assignee: Alan M. Carroll

> Truncated objects in the cache
> ------------------------------
>
>                 Key: TS-4221
>                 URL: https://issues.apache.org/jira/browse/TS-4221
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cache
>            Reporter: Leif Hedstrom
>            Assignee: Alan M. Carroll
>            Priority: Critical
>              Labels: A
>             Fix For: 6.2.0
>
>
> After upgrading to v6.1.x, we see a fair amount of these warnings:
> {code}
>     Feb 21 22:36:49 s_sys@machine-020.example.com traffic_server[33391]: {0x2aaab3c03700} WARNING: <CacheRead.cc:769 (openReadMain)> Document B302849 truncated at -941936464 of 1899191218, missing fragment 7B671521
>     Feb 22 00:19:01 s_sys@machine-020.example.com traffic_server[33391]: {0x2aaab3d04700} WARNING: <CacheRead.cc:769 (openReadMain)> Document FC28AC1D truncated at 792669024 of 884706125, missing fragment E85697A4
>     Feb 22 00:57:28 s_sys@machine-020.example.com traffic_server[33391]: {0x2aaab4a11700} WARNING: <CacheRead.cc:769 (openReadMain)> Document A2D26C6 truncated at 353345848 of 1978566429, missing fragment 8B26D5F3
> {code}
> It's happening across the border on all boxes upgraded to 6.1. We're not seeing any (or many) of these on the 5.3.x machines. According to Plevyak, this is indicative of bad writes, possibly broken connections. What's odd in our case is that we only see this on our child caches, the parents (running 6.1) do not see this at all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)