[
https://issues.apache.org/jira/browse/TS-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609331#comment-13609331
]
ASF subversion and git services commented on TS-1735:
-----------------------------------------------------
Commit dbf7124a945f38204b0548b1d2fdc54f51ed84ce in branch refs/heads/master
from [~john.v.kew...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=dbf7124 ]
TS-1735: Remove dead code that invokes missing vmap_config tool
Virtual IPs were once managed such that within a cluster they would
automatically rebalance themselves between nodes by bringing
subinterfaces up and down. After ATS was open sourced the original
setuid tool, vip_config (or traffic_vip_config) was inadvertently
removed; but the code which depended on this tool was not cleaned
up.
Since modern deployments either do not use this tool at all (because
it was broken for a few years) and modern deployments also have
some central system for managing cluster state reliably, we do not
need VMap to implement some scheme for automatically rebalancing
the ips.
This patch keeps much of the code for detecting ip address conflicts
and for receiving the multicast messages from the cluster; but we
remove all instances where we either bring up/down an interface.
Deployments should manage this through external state systems.
Note: VIPs do not actually bind to the specific addresses in vaddrs;
this is just an operations convience to ensure that a cluster has
no ip conflicts or unmanaged vips. This feature becomes even less
useful. LocalManager.cc would have to be modified in some way to
set this up properly.
> reclaimable freelist causes core in osx
> ---------------------------------------
>
> Key: TS-1735
> URL: https://issues.apache.org/jira/browse/TS-1735
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Bryan Call
> Fix For: 3.3.2
>
> Attachments: 0001-TS-1735-fix-initialization-of-_g_mattr.attr-V2.patch
>
>
> Global variable dependency and ininitialtion order can cause reclaimable
> freelist to core. Reclaimable freelist depends on a global mutex attribute.
> (gdb) bt
> #0 0x00007fff8fa17d46 in __kill ()
> #1 0x00007fff84824df0 in abort ()
> #2 0x00000001009ce697 in reclaimable_freelist_init (fl=<value temporarily
> unavailable, due to optimizations>, name=<value temporarily unavailable, due
> to optimizations>, type_size=<value temporarily unavailable, due to
> optimizations>, chunk_size=<value temporarily unavailable, due to
> optimizations>, alignment=<value temporarily unavailable, due to
> optimizations>) at ink_mutex.h:80
> #3 0x00007fff5fc13378 in
> __dyld__ZN16ImageLoaderMachO18doModInitFunctionsERKN11ImageLoader11LinkContextE
> ()
> #4 0x00007fff5fc13762 in
> __dyld__ZN16ImageLoaderMachO16doInitializationERKN11ImageLoader11LinkContextE
> ()
> #5 0x00007fff5fc1006e in
> __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEjRNS_21InitializerTimingListE
> ()
> #6 0x00007fff5fc0ffc4 in
> __dyld__ZN11ImageLoader23recursiveInitializationERKNS_11LinkContextEjRNS_21InitializerTimingListE
> ()
> #7 0x00007fff5fc0feba in
> __dyld__ZN11ImageLoader15runInitializersERKNS_11LinkContextERNS_21InitializerTimingListE
> ()
> #8 0x00007fff5fc01fc0 in __dyld__ZN4dyld24initializeMainExecutableEv ()
> #9 0x00007fff5fc05b04 in
> __dyld__ZN4dyld5_mainEPK12macho_headermiPPKcS5_S5_Pm ()
> #10 0x00007fff5fc01397 in
> __dyld__ZN13dyldbootstrap5startEPK12macho_headeriPPKclS2_Pm ()
> #11 0x00007fff5fc0105e in __dyld__dyld_start ()
--
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
