Re: AWS ELB with HA proxy showing 5XX errors

2017-09-08 Thread DHAVAL JAISWAL 
Great Information.

New configuration made as follows.

resolvers myresolver
  nameserver dns1 169.254.169.253:53
  resolve_retries   3
  timeout retry 1s
  hold valid   10s

backend mybackend
server server1 internal-testinelbtomcat-193184.ap-
southeast-1.elb.amazonaws.com:8080 check resolvers myresolver





On Thu, Sep 7, 2017 at 8:23 PM, Michael Ezzell  wrote:

>
> On Sep 6, 2017 5:18 AM, "DHAVAL JAISWAL"  wrote:
>
> I have some queries as well. Will above configuration slow down request -
> response or site performance ?
>
>
> The configuration you have shown seems valid.
>
> If this system is running in Amazon VIC, you can replace the nameserver IP
> address with 169.254.169.253.  This is a resolver provided by the VPC
> infrastructure that is always available regardless of the IPv4 CIDR block
> of the VPC.  There should be no need for additional resolvers, since if
> this isn't working, your instance's hypervisor has almost certainly failed
> and the instance will have failed along with it.
>
> http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/
> VPC_DHCP_Options.html#AmazonDNS
>
>


-- 
Thanks & Regards
Dhaval Jaiswal

Re: AWS ELB with HA proxy showing 5XX errors

2017-09-07 Thread Michael Ezzell 
On Sep 6, 2017 5:18 AM, "DHAVAL JAISWAL"  wrote:

I have some queries as well. Will above configuration slow down request -
response or site performance ?


The configuration you have shown seems valid.

If this system is running in Amazon VIC, you can replace the nameserver IP
address with 169.254.169.253.  This is a resolver provided by the VPC
infrastructure that is always available regardless of the IPv4 CIDR block
of the VPC.  There should be no need for additional resolvers, since if
this isn't working, your instance's hypervisor has almost certainly failed
and the instance will have failed along with it.

http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_DHCP_Options.html#AmazonDNS

AWS ELB with HA proxy showing 5XX errors

2017-09-06 Thread DHAVAL JAISWAL 
I want to ensure if there is any IP change of AWS ELB it should not give
any 5XX, 503 or affect the production site.

In order to solve it following configuration changes made in haproxy.cfg.

Please advise if there is any change require in the
following configuration. Does it required two nameservers or one is fine ?
If it requires two name servers then which is advisable.  I want to ensure
if there is any IP change of the ELB it should detect it immediately and
send the traffic to the ELB.


resolvers myresolver
  nameserver dns1 8.8.8.8:53
  resolve_retries   3
  timeout retry 1s
  hold valid 10s

backend mybackend
server server1 internal-testinelbtomcat-193184.ap-southeast-1.elb.
amazonaws.com:8080 check resolvers myresolver


I have some queries as well. Will above configuration slow down request -
response or site performance ?