为什么AWS Batch Jobs卡在RUNNABLE中？

Question

我在需求实例上使用0-256 m3.medium的计算环境.我的Job定义需要1个CPU和3 GB的Ram,m3.medium有.

AWS Batch Jobs陷入状态的可能原因是RUNNABLE什么？

AWS说:

A job that resides in the queue, has no outstanding dependencies, and is therefore ready to be scheduled to a host. Jobs in this state are started as soon as sufficient resources are available in one of the compute environments that are mapped to the job’s queue. However, jobs can remain in this state indefinitely when sufficient resources are unavailable.

但这不能回答我的问题

Answer 1

还有其他原因导致Job无法在RUNNABLE中陷入困境:

• 与计算环境关联的角色的权限不足
• Compute Environment实例无法访问Internet.您需要将NAT或Internet网关关联到Compute Environment子网.
  • 确保在计算环境的子网上选中"启用自动分配公共IPv4地址"设置.(@thisisbrians在评论中指出)
• 你的形象有问题.您需要使用ECS优化的AMI或确保ECS容器代理正常工作.有关aws docs的更多信息
• 您正尝试启动您的帐户限制为0个实例的实例(左侧菜单中的EC2控制台>限制).(阅读更多关于gergely-danyi的评论)
• 并且如提到的资源不足

此外,请务必阅读AWS Batch故障排除

Answer 2

至少应使用下一个策略和可信关系来定义角色。如果没有，它们将因为没有足够的特权启动而陷入“可运行”状态：

 AWSBatchServiceRole

• 附加政策： AWSBatchServiceRole

• 信任关系： batch.amazonaws.com

  {
    "Version": "2012-10-17",
    "Statement": [
      {
        "Effect": "Allow",
        "Principal": {
           "Service": "batch.amazonaws.com"
         },
        "Action": "sts:AssumeRole"
      }
    ]
  }
  

ecsInstanceRole

• 附加政策： AmazonEC2ContainerServiceforEC2Role

• 信任关系： ec2.amazonaws.com

  {
    "Version": "2012-10-17",
    "Statement": [
      {
        "Effect": "Allow",
        "Principal": {
           "Service": "ec2.amazonaws.com"
         },
        "Action": "sts:AssumeRole"
      }
    ]
  }