You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "weijin (JIRA)" <ji...@apache.org> on 2012/10/17 07:44:03 UTC

[jira] [Assigned] (TS-1433) enable_read_while_writer not working in 3.2.0

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

weijin reassigned TS-1433:
--------------------------

    Assignee: weijin
    
> enable_read_while_writer not working in 3.2.0
> ---------------------------------------------
>
>                 Key: TS-1433
>                 URL: https://issues.apache.org/jira/browse/TS-1433
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Cache
>    Affects Versions: 3.2.0
>         Environment: Ubuntu 10.04
>            Reporter: Kingsley Foreman
>            Assignee: weijin
>             Fix For: 3.3.1
>
>         Attachments: ts-1433.try1.diff, ts-1433.try2.diff, ts.3.2.x-1433.try3.diff
>
>
> enable_read_while_writer is not currently working as it should
> with the settings
> CONFIG proxy.config.cache.enable_read_while_writer INT 1
> CONFIG proxy.config.cache.max_doc_size INT 0
> CONFIG proxy.config.http.background_fill_active_timeout INT 0
> CONFIG proxy.config.http.background_fill_completed_threshold FLOAT 0
> If I do
> wget http://127.0.0.1:8080/largefile.mpg g -O /dev/null
> and then on the same box 30 seconds later (while the first one is still going I do)
> wget http://127.0.0.1:8080/largefile.mpg g -O /dev/null
> again
> The master server (after I kill them both) gets
> 012-09-03T10:49:32.007667+09:18 master1-adl6 nginx: 1.1.1.1 - - [03/Sep/2012:10:49:32 +0930] "GET /largefile.mpg HTTP/1.1" 200 306253448 "-" "Wget/1.12 (linux-gnu)" "-"
> 2012-09-03T10:49:32.879914+09:18 master1-adl6 nginx: 1.1.1.1 - - [03/Sep/2012:10:49:32 +0930] "GET /largefile.mpg HTTP/1.1" 200 226717704 "-" "Wget/1.12 (linux-gnu)" "-"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira