[jira] [Commented] (TS-2523) automatically max out the listen backlog
[
https://issues.apache.org/jira/browse/TS-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14957147#comment-14957147
]
zxcvbn4038 commented on TS-2523:
[~jamespeach][~dcarlin] This option is also undocumented, as part of this
change documentation should be added.
> automatically max out the listen backlog
>
>
> Key: TS-2523
> URL: https://issues.apache.org/jira/browse/TS-2523
> Project: Traffic Server
> Issue Type: Bug
> Components: Core, Network
>Reporter: James Peach
> Labels: incompatible, yahoo
> Fix For: sometime
>
>
> Rather than choosing the right value for {{proxy.config.net.listen_backlog}},
> we should support a -1 default. This would max out the listen backlog on
> systems where we know how to find that, and set it to {{SOMAXCON}} everywhere
> else.
> On Linux, the max backlog is 65535 (unsigned short), and the kernel will clip
> that to {{/proc/sys/net/core/somaxconn}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-2118) memcached plugin is in the source tree but does not build
[
https://issues.apache.org/jira/browse/TS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14957891#comment-14957891
]
James Peach commented on TS-2118:
-
Looks like the patch didn't attach?
> memcached plugin is in the source tree but does not build
> -
>
> Key: TS-2118
> URL: https://issues.apache.org/jira/browse/TS-2118
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: John Rushford
> Labels: newbie
> Fix For: 6.1.0
>
>
> The memcached_remap plugin is currently in our experimental plugin tree, but
> doesn't build even with {{--enable-experimental}}.
> This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TS-2118) memcached plugin is in the source tree but does not build
[
https://issues.apache.org/jira/browse/TS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14957896#comment-14957896
]
John Rushford edited comment on TS-2118 at 10/14/15 10:03 PM:
--
See the attached patch. I've made modifications so that this plugin may be
built if the package libmemcached 1.0 or greater has been installed on the
build host and if --enable-experimental-plugins is used with the configure
script. If libmemcached 1.0 or greater is not installed, the plugin will not
be built but the build will proceed and build all other experimental plugins.
See the attached TS-2118.diff
Patch should be attached now, had JIRA cockpit issues.
was (Author: jrushford):
Patch to fix this issue.
> memcached plugin is in the source tree but does not build
> -
>
> Key: TS-2118
> URL: https://issues.apache.org/jira/browse/TS-2118
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: John Rushford
> Labels: newbie
> Fix For: 6.1.0
>
> Attachments: TS-2118.diff
>
>
> The memcached_remap plugin is currently in our experimental plugin tree, but
> doesn't build even with {{--enable-experimental}}.
> This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2118) memcached plugin is in the source tree but does not build
[
https://issues.apache.org/jira/browse/TS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Rushford updated TS-2118:
--
Attachment: TS-2118.diff
Patch to fix this issue.
> memcached plugin is in the source tree but does not build
> -
>
> Key: TS-2118
> URL: https://issues.apache.org/jira/browse/TS-2118
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: John Rushford
> Labels: newbie
> Fix For: 6.1.0
>
> Attachments: TS-2118.diff
>
>
> The memcached_remap plugin is currently in our experimental plugin tree, but
> doesn't build even with {{--enable-experimental}}.
> This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-2118) memcached plugin is in the source tree but does not build
[
https://issues.apache.org/jira/browse/TS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958063#comment-14958063
]
John Rushford commented on TS-2118:
---
Hi James,
I added the m4 file and the AX_CXX_COMPILE_STDCXX_0X macro and
AM_CONDITIONAL so that it would build with older compilers like mine,
gcc 4.4.7 that use the -std=c++0x flag.
John
> memcached plugin is in the source tree but does not build
> -
>
> Key: TS-2118
> URL: https://issues.apache.org/jira/browse/TS-2118
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: John Rushford
> Labels: newbie
> Fix For: 6.1.0
>
> Attachments: TS-2118.diff
>
>
> The memcached_remap plugin is currently in our experimental plugin tree, but
> doesn't build even with {{--enable-experimental}}.
> This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TS-2118) memcached plugin is in the source tree but does not build
[
https://issues.apache.org/jira/browse/TS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958006#comment-14958006
]
James Peach commented on TS-2118:
-
Looks reasonable, though I'm not sure about the C++11 detection. We already use
{{AX_CXX_COMPILE_STDCXX_11}}. Looking at the memcached plugin, I didn't really
see anything that looked like it needed C++11.
> memcached plugin is in the source tree but does not build
> -
>
> Key: TS-2118
> URL: https://issues.apache.org/jira/browse/TS-2118
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: John Rushford
> Labels: newbie
> Fix For: 6.1.0
>
> Attachments: TS-2118.diff
>
>
> The memcached_remap plugin is currently in our experimental plugin tree, but
> doesn't build even with {{--enable-experimental}}.
> This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TS-2118) memcached plugin is in the source tree but does not build
[
https://issues.apache.org/jira/browse/TS-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14958006#comment-14958006
]
James Peach edited comment on TS-2118 at 10/14/15 11:28 PM:
Looks reasonable, though I'm not sure about the C\+\+11 detection. We already
use {{AX_CXX_COMPILE_STDCXX_11}}. Looking at the memcached plugin, I didn't
really see anything that looked like it needed C++11.
was (Author: jamespeach):
Looks reasonable, though I'm not sure about the C++11 detection. We already use
{{AX_CXX_COMPILE_STDCXX_11}}. Looking at the memcached plugin, I didn't really
see anything that looked like it needed C++11.
> memcached plugin is in the source tree but does not build
> -
>
> Key: TS-2118
> URL: https://issues.apache.org/jira/browse/TS-2118
> Project: Traffic Server
> Issue Type: Bug
>Reporter: Igor Galić
>Assignee: John Rushford
> Labels: newbie
> Fix For: 6.1.0
>
> Attachments: TS-2118.diff
>
>
> The memcached_remap plugin is currently in our experimental plugin tree, but
> doesn't build even with {{--enable-experimental}}.
> This should be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TS-3969) NetHandler::mainNetEvent always output DEBUG info "Unhandled epoll event" for EVENTIO_READ
Oknet Xu created TS-3969:
Summary: NetHandler::mainNetEvent always output DEBUG info
"Unhandled epoll event" for EVENTIO_READ
Key: TS-3969
URL: https://issues.apache.org/jira/browse/TS-3969
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: Oknet Xu
{code}
diff --git a/iocore/net/UnixNet.cc b/iocore/net/UnixNet.cc
index 5930273..188f2b4 100644
--- a/iocore/net/UnixNet.cc
+++ b/iocore/net/UnixNet.cc
@@ -487,7 +487,7 @@ NetHandler::mainNetEvent(int event, Event *e)
Debug("iocore_net_main", "Unhandled epoll event on write: 0x%04x
write.enabled=%d closed=%d write.netready_queue=%d",
get_ev_events(pd, x), vc->write.enabled, vc->closed,
write_ready_list.in(vc));
}
- } else if (!(get_ev_events(pd, x) & EVENTIO_ERROR)) {
+ } else if (!(get_ev_events(pd, x) & EVENTIO_READ)) {
Debug("iocore_net_main", "Unhandled epoll event: 0x%04x",
get_ev_events(pd, x));
}
} else if (epd->type == EVENTIO_DNS_CONNECTION) {
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
