[ https://issues.apache.org/jira/browse/TS-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862248#action_12862248 ]
John Plevyak commented on TS-329: --------------------------------- Gack it looks like this patch also fixes pipe() based signaling. Is this same code in 2.0.X? Is pipe signaling broken in that is is it running your version? Looking over the patch I realize that the signaling code is kind of a mess now. try_signal has never been used and should be removed. The ProtectedQueue::signal() doesn't call the hook, so the bool fast_signal doesn't really make sense in that signal doesn't relate to fast_signal. Sheesh. I think some cleanup is in order, but then cleanup is in order all over the code. Also it looks like this patch is against the tree with George's standalone iocore patch which I don't think has been committed yet. If you don't have time or want to do the cleanup then check this in as we need the pipe() fix in any case. > delay seen in handling the client's request while running with accept thread > ----------------------------------------------------------------------------- > > Key: TS-329 > URL: https://issues.apache.org/jira/browse/TS-329 > Project: Traffic Server > Issue Type: Improvement > Components: Core > Reporter: vijaya bhaskar mamidi > Priority: Minor > Attachments: patch.329 > > > Recent tests prove that while using accept thread, we do end up waiting for a > period of time before handling the > request from the client. This is because the signal is not delivered to a net > thread to handle the new connection because of epoll_wait timeout > Fix is to provide a schedule_imm_signal method which can be used in accept > thread to signal a given net thread for handling new connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.