[
https://issues.apache.org/jira/browse/TS-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619848#comment-13619848
]
Leif Hedstrom commented on TS-1713:
-----------------------------------
Hmmm, ok. I'd recommend we reduce the storage entries then. It's absolutely
crazy that we'd consume 15000 bytes (15KB) for each entry. A vast majority of
people will never use SRV records, in forward proxy it's all but guaranteed
that a single entry fits in a 512 byte UDP package. Does the new calculation
assume that every entry is SRV ? Or does it always consume roughly 3x the
amount of storage now, even if there are no SRV records?
I understand 100MB is nothing for your boxes, but I know there are plenty of
use cases where a small memory footprint is important. Like, the way I use it,
this change would double my memory footprint (unless I tweak the configs
myself). I much rather have the settings somewhat reasonable for some large
number of people (i.e. small footprint) and let the ones who needs SRV records
change the configs (I don't know of anyone except Taobao that are using SRV
records).
> Querying SRV record doesn't work
> --------------------------------
>
> Key: TS-1713
> URL: https://issues.apache.org/jira/browse/TS-1713
> Project: Traffic Server
> Issue Type: Bug
> Components: DNS
> Reporter: Li-Wen Hsu
> Assignee: weijin
> Fix For: 3.3.2
>
> Attachments: support_srv.patch, ts-1713.diff
>
>
> For ATS > 3.0.x, when setting "CONFIG proxy.config.srv_enabled INT 1" in
> records.config , ATS blocks and return nothing to client, even no 404.
--
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
