Dan Morgan created TS-1429:
------------------------------
Summary: Log collation of custom xml logs failing
Key: TS-1429
URL: https://issues.apache.org/jira/browse/TS-1429
Project: Traffic Server
Issue Type: Bug
Components: Logging
Affects Versions: 3.2.0
Environment: Linux
Reporter: Dan Morgan
When configuring logs_xml.config to send to a collation host with the
<CollationHosts> entry, we start to get these errors in traffic.out:
NOTE: [log-coll] send-queue full; orphaning logs [192.168.57.248:8085]
NOTE: [log-coll] send-queue clear; resuming collation [192.168.57.248:8085]
thousands of them.
It looks like there used to be a config value called:
collation_max_send_buffers that has been removed, but there's still code in
LogCollationClientSM.cc that references that value (which appears to now be
zero). Line 185 looks like:
if (m_buffer_send_list->get_size() >= Log::config->collation_max_send_buffers)
{
Debug("log-coll", "[%d]client::send - m_flow = DENY", m_id);
Note("[log-coll] send-queue full; orphaning logs "
"[%s:%u]", m_log_host->ip_addr().toString(ipb, sizeof(ipb)),
m_log_host->port());
m_flow = LOG_COLL_FLOW_DENY;
}
but since collation_max_send_buffers is zero, it always goes into that if block.
Just as a note as well, issue TS-1299
(https://issues.apache.org/jira/browse/TS-1299) which has a patch for 3.1.4,
never made it into 3.2 (looks like it was done on the same day as 3.2 was
released).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
