ezelkow1 commented on issue #12166: URL: https://github.com/apache/trafficserver/issues/12166#issuecomment-2784787890
One option you can try is setting the write lock failure option to setting `5`, https://docs.trafficserver.apache.org/en/9.2.x/admin-guide/files/records.config.en.html#proxy-config-http-cache-open-write-fail-action It is still considered experimental because in previous versions of ATS we could see eventual crashes with it enabled on specific content but it may be worth trying. This enables ATS to jump backwards in the state machine so when the write lock fails it can go back to the read state and wait in line. This wont directly address the IMS question but it would bring down the multiple origin requests as long as you have read while writer enabled. We discussed this a bit during our bug scrub call and it looks like while it removes the IMS header it does re-insert it based on the request, so an IMS header should end up existing in the cached copy, but it would still make the upstream request in your case. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
