The weight value is taken into consideration after the base value, if defined, is satisfied. The weight value designates the relative percentage of the total number of tasks launched that should use the specified capacity provider. The Fargate capacity providers are available to all accounts and only need to be associated with a cluster to be used in a capacity provider strategy.Ī capacity provider strategy may contain a maximum of 6 capacity providers. To use a Fargate capacity provider, specify either the FARGATE or FARGATE_SPOT capacity providers. New Auto Scaling group capacity providers can be created with the CreateCapacityProvider API operation. If specifying a capacity provider that uses an Auto Scaling group, the capacity provider must already be created. The PutClusterCapacityProviders API is used to associate a capacity provider with a cluster. Only capacity providers that are already associated with a cluster and have an ACTIVE or UPDATING status can be used in a capacity provider strategy. A capacity provider strategy can be set when using the RunTask or CreateCluster APIs or as the default capacity provider strategy for a cluster with the CreateCluster API. The details of a capacity provider strategy. See 'aws help' for descriptions of global parameters. Apply an exponential backoff algorithm starting with a couple of seconds of wait time, and increase gradually up to about five minutes of wait time. Add wait time between subsequent commands, even if the DescribeTasks command returns an accurate response.To do this, run the DescribeTasks command repeatedly, starting with a couple of seconds of wait time and increasing gradually up to five minutes of wait time. Run the DescribeTasks command using an exponential backoff algorithm to ensure that you allow enough time for the previous command to propagate through the system. Confirm the state of the resource before you run a command to modify it.To manage eventual consistency, you can do the following: Keep this in mind when you carry out an API command that immediately follows a previous API command. This means that the result of an API command you run that affects your Amazon ECS resources might not be immediately visible to all subsequent commands you run. This is because the distributed nature of the system supporting the API. The Amazon ECS API follows an eventual consistency model. Īlternatively, you can use StartTask to use your own scheduler or place tasks manually on specific container instances. For more information, see Scheduling Tasks in the Amazon Elastic Container Service Developer Guide. You can allow Amazon ECS to place tasks for you, or you can customize how Amazon ECS places tasks using placement constraints and placement strategies. Starts a new task using the specified task definition.
0 kommentar(er)
