[
https://issues.apache.org/jira/browse/TS-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162588#comment-13162588
]
Leif Hedstrom commented on TS-1027:
-----------------------------------
Test it :). Yes, there will be some penalty, but it also depends on your
configs. There's an initial hash on the hostname, so if you have unique
hostnames on each remap rule, it ought to be O(1). However, degenerated cases
with lots of rules for the same host could have some performance implications
(however, it does a trie on the prefix part of the path in that case).
This is in theory though, things might have changed. If you are seeing
performance problems, we should investigate. At a minimum, rules with unique
hostnames should be O(1) always (it's a simple hash table lookup).
> remap.config limited to ~255 entries
> ------------------------------------
>
> Key: TS-1027
> URL: https://issues.apache.org/jira/browse/TS-1027
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 3.0.2
> Reporter: Greg Dallavalle
>
> Remap.config errors out trafficserver when the entries exceed ~249
> Due to issue TS-1024 I am using a large number of remaps to workaround the
> issue. With this limit I'm unable to proceed with ATS. If there are ways to
> overcome these problems, by all means, I'd be happy to listen and test.
> The errors from traffic.out:
> [Nov 21 15:20:08.572] Server {1080866016} ERROR: Cannot insert duplicate!
> [Nov 21 15:20:08.573] Server {1080866016} ERROR: Couldn't insert into trie!
> [Nov 21 15:20:08.573] Server {1080866016} ERROR: Could not insert new mapping
> [Nov 21 15:20:08.573] Server {1080866016} WARNING: Could not add rule at line
> #249; Aborting!
> [Nov 21 15:20:08.578] Server {1080866016} WARNING: [ReverseProxy] Unable to
> add mapping rule to lookup table at line 249
> FATAL: [ReverseProxy] Unable to add mapping rule to lookup table at line 249
> /usr/bin/traffic_server - STACK TRACE:
> /usr/lib/trafficserver/libtsutil.so.3(ink_fatal_va+0xf7)[0x400301a7]
> /usr/lib/trafficserver/libtsutil.so.3(ink_fatal+0x2c)[0x4003020c]
> /usr/bin/traffic_server(_ZN10UrlRewrite10BuildTableEv+0x5a2)[0x819b402]
> /usr/bin/traffic_server(_ZN10UrlRewriteC1EPKc+0x337)[0x819da87]
> /usr/bin/traffic_server(_Z18init_reverse_proxyv+0x9a)[0x810bb6a]
> /usr/bin/traffic_server(_Z20init_HttpProxyServerv+0xb)[0x814664b]
> /usr/bin/traffic_server(main+0x12bb)[0x80b547b]
> /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x40561113]
> /usr/bin/traffic_server[0x80baffd]
> [Nov 21 15:20:08.638] Manager {3072087760} ERROR:
> [LocalManager::pollMgmtProcessServer] Server Process terminated due to Sig 6:
> Aborted
> [Nov 21 15:20:08.639] Manager {3072087760} ERROR: (last system error 2: No
> such file or directory)
> [Nov 21 15:20:08.639] Manager {3072087760} ERROR: [Alarms::signalAlarm]
> Server Process was reset
> [Nov 21 15:20:08.639] Manager {3072087760} ERROR: (last system error 2: No
> such file or directory)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
