trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ocean" <oceanji...@vip.qq.com>
Subject Re: host database broken
Date Sat, 10 Aug 2013 14:07:45 GMT
hi all:
   I have a question in hostdb. In my use circumstance I have two origin server, one used
as master ,and the other as backup, I want all ats back to the master first if it worked normal,
if the master  is down , all should be to the backup. 
   I configured my dns with fixed order but not round robin,that is to say, the dns result
is fixed order.for example:
   www.example.com 192.168.1.1
   www.example.com 192.168.1.2
If I use dig command , the dns  return the results in this order all the time.
   but ats has a DNS resolver itself , I didn't know how it works. In my test, I  found that
ats choose the ip which has greater value, although I put the the greater value ip in second
place, in www.example.com ,  ats always choose 192.168.1.2 first.
     Can anybody tell me wether my guess is right?  and how can I let ats choose  the first
ip in priority? 


------------------ Original ------------------
From:  "zwoop"<zwoop@apache.org>;
Date:  Sat, Aug 10, 2013 07:14 AM
To:  "users"<users@trafficserver.apache.org>; 

Subject:  Re: host database broken



On Aug 9, 2013, at 4:55 PM, Reindl Harald <h.reindl@thelounge.net> wrote:

> 
> Am 10.08.2013 00:43, schrieb Leif Hedstrom:
>> On Aug 9, 2013, at 4:39 PM, Reindl Harald <h.reindl@thelounge.net> wrote:
>>> if it would be placed in /var/cache/trafficserver instead of /etc/trafficserver/internal
>>> all would be fine - the point is that for security reasons no server process
should
>>> need mandatory write access for /etc, not more and not less and for non-clustered
>>> all the messages below could go away easily
>> 
>> sounds good, file a bug and attach a patch :). It'd be a simple change I think, and
now that 
>> we've started v3.5.x development, it's ok to break compatibility
> 
> well, if i would be a C-programmer you already would have a patch as well as
> i would investigate what is eating CPU load all the long in idle-state which
> results in around 150 MHz idle-load

well, if you submit a bug in Jira, I'll fix the hostdb.config directory.

-- leif

.
Mime
View raw message