[ https://issues.apache.org/jira/browse/TS-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208510#comment-14208510 ]
ASF GitHub Bot commented on TS-3190: ------------------------------------ GitHub user shinrich opened a pull request: https://github.com/apache/trafficserver/pull/144 TS-3190: Limit the number of producers invoked via producer_run You can merge this pull request into a Git repository by running: $ git pull https://github.com/shinrich/trafficserver ts-3190 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/144.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #144 ---- commit d9cd23acb7b9b143ec8a2cdda450d17dfaf48c40 Author: shinrich <shinr...@network-geographics.com> Date: 2014-11-12T18:44:43Z TS-3190 Use the version of producer_run that runs a specific producer instead of all producers. commit 0a6fc4f21eddc6823020ef3ae4c7a1e95e87a5a1 Author: shinrich <shinr...@network-geographics.com> Date: 2014-11-12T18:46:04Z Add a clear half close flag. ---- > Change producer_run() to run a specific producer in more cases > -------------------------------------------------------------- > > Key: TS-3190 > URL: https://issues.apache.org/jira/browse/TS-3190 > Project: Traffic Server > Issue Type: Bug > Reporter: Susan Hinrichs > Assignee: Susan Hinrichs > > Found while tracking down TS-3105. It seemed like sometimes producers were > having producer_run called on them multiple times. producer_run can be run on > a particular producers or on all producers added at that point in time. > There are a couple places where multiple producers are set up and so > producer_run(NULL) makes sense. But in many cases a producer is carefully > added and then producer_run(NULL) is called on all producers that are around > that that point in time. > It seems safer to call producer_run() on the newly added producer in those > cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)