Ends in
00
hrs
00
mins
00
secs
SHOP NOW

24-Hour Extension! $2 OFF ALL AWS, Azure, Google Cloud & Kubernetes Practice Exams!

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate How do you make sure that user requests are completed before instances are termi

  • How do you make sure that user requests are completed before instances are termi

  • daaaaannn

    Member
    June 28, 2020 at 5:41 pm

    A reporting application run on EC2 behind ALB. The instances run in an EC2 Autoscaling group across multiple AZ. Some report take up to 15 minutes to respond to a request. You are concern that the user will receive 500 errors if a report request is in process during a scale in event. What can you to complete the user request before instances are terminated?

    A. Enable sticky session for the target group

    B. Enable connection draining on the ALB

    C. Increase the cooldown of the autoscaling to be > 1500 seconds

    D. Increase the deregistration delay timeout for the target group to be > 1500 seconds

    Deregistration Delay….Elastic Load Balancing stops sending requests to targets that are deregistering. By default, Elastic Load Balancing waits 300 seconds before completing the deregistration process, which can help in-flight requests to the target to complete. To change the amount of time that Elastic Load Balancing waits, update the deregistration delay value.

    The initial state of a deregistering target is draining. After the deregistration delay elapses, the deregistration process completes and the state of the target is unused. If the target is part of an Auto Scaling group, it can be terminated and replaced.

    If a deregistering target has no in-flight requests and no active connections, Elastic Load Balancing immediately completes the deregistration process, without waiting for the deregistration delay to elapse. However, even though target deregistration is complete, the status of the target will be displayed as draining until the deregistration delay elapses.

    If a deregistering target terminates the connection before the deregistration delay elapses, the client receives a 500-level error response.

    When Connection Draining is enabled and configured, the process of deregistering an instance from an Elastic Load Balancer gains an additional step. For the duration of the configured timeout, the load balancer will allow existing, in-flight requests made to an instance to complete

    so what is for you B or D?

  • TutorialsDojo-Support

    Member
    June 29, 2020 at 6:17 pm

    Hello daaaaannn,

    Since the problem is concerned with 500 errors. I think enable connection draining on the ALB is an option.

    Connection Draining – specify a maximum time for the load balancer to keep connections alive before reporting the instance as de-registered.

    Deregistration Delay – amount of time for ELB to wait before deregistering a target.

    I hope this helps.

    Thanks and Regards,

    Gerome Pagatpatan @ Tutorials Dojo

    • Revy Ramirez

      Member
      June 29, 2022 at 11:44 pm

      Thank you! looking for answer to this too

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now