Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64704

Clarity on EC2 nodes Termination policy

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: ec2-plugin
    • Labels:
    • Environment:
      OS: Amazon Linux AMI
      Java version: 1.8
      Jenkins version: 2.271
      EC2 plugin version: 1.56
    • Similar Issues:

      Description

      We are using EC2 plugin to distribute our builds on EC2 instances. We need clarity or an improvement on the understanding that how does Jenkins (or EC2 plugin) decides to TERMINATE nodes (or EC2 instances). How it decides what nodes need to get TERMINATES and when?

      Let's say: We have one node (Minimum number of instances: 1) always available. But, we are facing some EBS space related issue if the instance stays for long time. Can we adjust or fine-tune the plugin so that every day at a specific time-period old node gets TERMINATED and a new node would take its place? Right now, we are not able to see an such setting that helps us to specify such functionality.
      Kindly help us or navigate us to understand how actually it does work behind the scenes.
      If possible kindly mention the same in the plugin documentation.

        Attachments

          Activity

          Hide
          sahil_sharma Sahil Sharma added a comment -

          Any updates would be highly beneficial to eliminate the bottleneck. Thanks in advance.

          Show
          sahil_sharma Sahil Sharma added a comment - Any updates would be highly beneficial to eliminate the bottleneck. Thanks in advance.

            People

            Assignee:
            thoulen FABRIZIO MANFREDI
            Reporter:
            sahil_sharma Sahil Sharma
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: