Hi, We are evaluating ATS as reverse proxy for some live video traffic. The client sends 1000s of parallel requests to the trafficserver for a bunch of URLs distributed across parallel connections. We want to limit the request to the origin at best to 1 request per URL and throttle it to atleast only a few requests per URL. However, we are seeing that there are many requests leaking to the origin for the same URL before trafficserver starts serving content out of its cache.
We have the below config in records.config as suggested in some of the other threads. This has RWW enabled and open_write_fail_action set to 5 (so..no need of collapse forwarding plugin as per: http://apache-traffic-server.24303.n7.nabble.com/collapsed-forwarding-still-leaking-to-origin-td4752.html#a4757 ) CONFIG proxy.config.cache.enable_read_while_writer INT 1 CONFIG proxy.config.http.background_fill_active_timeout INT 0 CONFIG proxy.config.http.background_fill_completed_threshold FLOAT 0.000000 CONFIG proxy.config.cache.max_doc_size INT 0 CONFIG proxy.config.cache.read_while_writer.max_retries INT 20 CONFIG proxy.config.cache.read_while_writer_retry.delay INT 50 CONFIG proxy.config.http.cache.max_open_read_retries INT 10 CONFIG proxy.config.http.cache.open_read_retry_time INT 100 CONFIG proxy.config.http.cache.open_write_fail_action INT 5 CONFIG proxy.config.thread.default.stacksize INT 2097152 CONFIG proxy.config.allocator.thread_freelist_size INT 1024 However, it appears there are still many duplicate requests that are leaking to the origin. Does anyone have a proven working config that limits the number of duplicate requests to origin ? ATS version : 10.0.0 thanks, -vishwas.
