[
https://issues.apache.org/jira/browse/TS-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035256#comment-13035256
]
Zhao Yongming commented on TS-621:
----------------------------------
I don't know why, from my point:
1, every miss will trigger up a write on the cluster, which will done with
success indeed.
2, but when do cache_read on the cluster, the remote side will just send back a
fail response.
here is my debug info from traffic.out:
{code}
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_msg) cache_op-s
op=1 seqno=1067 data=0x1189018 len=77 machine=0x11d65c0
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cluster_trace)
alloc_channel remote chan=1097 VC=0x12339d0
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cluster_trace) VC start
alloc remote chan=1097 VC=0x12339d0
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_proto) 0read op,
seqno=1067 chan=1097 bufsize=2097152 token=-308068854,548
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_hosting) Generic
volume: f572d8d for host:
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_new) new 0x12f96b0
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (http_match)
[SelectFromAlternates] # alternates = 5
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (http_seq)
[SelectFromAlternates] 5 alternates for this cached doc
[alts] There are 5 alternates for this request header.
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_proto)
setupVCdataRead CACHE_EVENT_OPEN_READ seqno=1067
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_close) do_io_close
0x12f96b0 -1 1
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_proto)
replyOpEvent(this=11fd4f0,event=1103,VC=ffffb115)
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_proto) cache
operation failed result=1103 seqno=1067 (this=11fd4f0)
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_proto) Sending
reply/data seqno=1067 buflen=0
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_proto)
replyOpEvent: freeing this=11fd4f0
[May 18 17:38:53.348] Server {47562039445248} DEBUG: (cache_free) free 0x12f96b0
[May 18 17:38:53.349] Server {47562039445248} DEBUG: (cluster_monitor_ping)
[10.62.163.237] ping: 0 34937
[May 18 17:38:53.349] Server {47562039445248} DEBUG: (cluster_trace)
free_channel remote chan=1097 VC=0x12339d0
{code}
while the common objects will just response:
{code}
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_msg) cache_op-s
op=1 seqno=821 data=0x1189018 len=75 machine=0x11d65c0
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_proto) 0read op,
seqno=821 chan=847 bufsize=2097152 token=-308068854,423
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_hosting) Generic
volume: f572d8d for host:
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_new) new 0x12bc9e0
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (http_match)
[SelectFromAlternates] # alternates = 1
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (http_seq)
[SelectFromAlternates] 1 alternates for this cached doc
[alts] There are 1 alternates for this request header.
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_proto)
setupVCdataRead CACHE_EVENT_OPEN_READ seqno=821
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_close) do_io_close
0x12bc9e0 -1 1
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_proto)
replyOpEvent(this=11fd4f0,event=1102,VC=12bc9e0)
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_proto)
connect_local success seqno=821 alldata=1
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_proto) Sending
reply/data seqno=821 buflen=77089
[May 18 17:18:36.358] Server {47562039445248} DEBUG: (cache_free) free 0x12bc9e0
{code}
> writing 0 bytes to the HTTP cache means only update the header... need a new
> API: update_header_only() to allow 0 byte files to be cached
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TS-621
> URL: https://issues.apache.org/jira/browse/TS-621
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Affects Versions: 2.1.5
> Reporter: John Plevyak
> Assignee: John Plevyak
> Fix For: 2.1.9
>
> Attachments: ts-621-jp-1.patch, ts-621-jp-2.patch, ts-621-jp-3.patch
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
