AWS autoscaling ELB forward requests to instance not yet ready to take requests
I have setup auto-scaling on AWS. I noticed, whenever I add a new instance to my auto scaling group my load balancer starts sending traffic to new instance even if its not yet ready to handle traffic and result is 502 Bad Gateway.
I have set Health Check Grace Period to 300 but I feel ELB doesn't wait for this time and starts forwarding traffic to newly added instance.
Can you please guide me how I can ensure ELB waits for my instance to be ready to handle requests.
Thanks
amazon-web-services amazon-ec2 amazon-elb
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
|
show 1 more comment
I have setup auto-scaling on AWS. I noticed, whenever I add a new instance to my auto scaling group my load balancer starts sending traffic to new instance even if its not yet ready to handle traffic and result is 502 Bad Gateway.
I have set Health Check Grace Period to 300 but I feel ELB doesn't wait for this time and starts forwarding traffic to newly added instance.
Can you please guide me how I can ensure ELB waits for my instance to be ready to handle requests.
Thanks
amazon-web-services amazon-ec2 amazon-elb
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
Your health check URL may be returning 200 too early.
– titogeo
Nov 15 '18 at 13:17
@titogeo- please see attached image above - what do you suggest?
– Irfan DANISH
Nov 15 '18 at 13:25
is 300 enough for your application to be fully up? Is your health check waiting for your application to load?
– titogeo
Nov 15 '18 at 13:30
Are you doing some processing on startup? If so you must wait for all those processes to finish before letting your heartbeat.php return a 200.
– Bob
Nov 15 '18 at 20:15
@Bob - no, new instance is booting from an AMI which contains per-configured LAMP setup with PHP and Laravel code mounted from EFS.
– Irfan DANISH
Dec 6 '18 at 8:20
|
show 1 more comment
I have setup auto-scaling on AWS. I noticed, whenever I add a new instance to my auto scaling group my load balancer starts sending traffic to new instance even if its not yet ready to handle traffic and result is 502 Bad Gateway.
I have set Health Check Grace Period to 300 but I feel ELB doesn't wait for this time and starts forwarding traffic to newly added instance.
Can you please guide me how I can ensure ELB waits for my instance to be ready to handle requests.
Thanks
amazon-web-services amazon-ec2 amazon-elb
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
I have setup auto-scaling on AWS. I noticed, whenever I add a new instance to my auto scaling group my load balancer starts sending traffic to new instance even if its not yet ready to handle traffic and result is 502 Bad Gateway.
I have set Health Check Grace Period to 300 but I feel ELB doesn't wait for this time and starts forwarding traffic to newly added instance.
Can you please guide me how I can ensure ELB waits for my instance to be ready to handle requests.
Thanks
amazon-web-services amazon-ec2 amazon-elb
amazon-web-services amazon-ec2 amazon-elb
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
edited Nov 15 '18 at 13:25
Irfan DANISH
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
asked Nov 15 '18 at 13:14
Irfan DANISHIrfan DANISH
4,92283156
4,92283156
Your health check URL may be returning 200 too early.
– titogeo
Nov 15 '18 at 13:17
@titogeo- please see attached image above - what do you suggest?
– Irfan DANISH
Nov 15 '18 at 13:25
is 300 enough for your application to be fully up? Is your health check waiting for your application to load?
– titogeo
Nov 15 '18 at 13:30
Are you doing some processing on startup? If so you must wait for all those processes to finish before letting your heartbeat.php return a 200.
– Bob
Nov 15 '18 at 20:15
@Bob - no, new instance is booting from an AMI which contains per-configured LAMP setup with PHP and Laravel code mounted from EFS.
– Irfan DANISH
Dec 6 '18 at 8:20
|
show 1 more comment
Your health check URL may be returning 200 too early.
– titogeo
Nov 15 '18 at 13:17
@titogeo- please see attached image above - what do you suggest?
– Irfan DANISH
Nov 15 '18 at 13:25
is 300 enough for your application to be fully up? Is your health check waiting for your application to load?
– titogeo
Nov 15 '18 at 13:30
Are you doing some processing on startup? If so you must wait for all those processes to finish before letting your heartbeat.php return a 200.
– Bob
Nov 15 '18 at 20:15
@Bob - no, new instance is booting from an AMI which contains per-configured LAMP setup with PHP and Laravel code mounted from EFS.
– Irfan DANISH
Dec 6 '18 at 8:20
Your health check URL may be returning 200 too early.
– titogeo
Nov 15 '18 at 13:17
Your health check URL may be returning 200 too early.
– titogeo
Nov 15 '18 at 13:17
@titogeo- please see attached image above - what do you suggest?
– Irfan DANISH
Nov 15 '18 at 13:25
@titogeo- please see attached image above - what do you suggest?
– Irfan DANISH
Nov 15 '18 at 13:25
is 300 enough for your application to be fully up? Is your health check waiting for your application to load?
– titogeo
Nov 15 '18 at 13:30
is 300 enough for your application to be fully up? Is your health check waiting for your application to load?
– titogeo
Nov 15 '18 at 13:30
Are you doing some processing on startup? If so you must wait for all those processes to finish before letting your heartbeat.php return a 200.
– Bob
Nov 15 '18 at 20:15
Are you doing some processing on startup? If so you must wait for all those processes to finish before letting your heartbeat.php return a 200.
– Bob
Nov 15 '18 at 20:15
@Bob - no, new instance is booting from an AMI which contains per-configured LAMP setup with PHP and Laravel code mounted from EFS.
– Irfan DANISH
Dec 6 '18 at 8:20
@Bob - no, new instance is booting from an AMI which contains per-configured LAMP setup with PHP and Laravel code mounted from EFS.
– Irfan DANISH
Dec 6 '18 at 8:20
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53320329%2faws-autoscaling-elb-forward-requests-to-instance-not-yet-ready-to-take-requests%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53320329%2faws-autoscaling-elb-forward-requests-to-instance-not-yet-ready-to-take-requests%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Your health check URL may be returning 200 too early.
– titogeo
Nov 15 '18 at 13:17
@titogeo- please see attached image above - what do you suggest?
– Irfan DANISH
Nov 15 '18 at 13:25
is 300 enough for your application to be fully up? Is your health check waiting for your application to load?
– titogeo
Nov 15 '18 at 13:30
Are you doing some processing on startup? If so you must wait for all those processes to finish before letting your heartbeat.php return a 200.
– Bob
Nov 15 '18 at 20:15
@Bob - no, new instance is booting from an AMI which contains per-configured LAMP setup with PHP and Laravel code mounted from EFS.
– Irfan DANISH
Dec 6 '18 at 8:20