Glue connections running out of IPs

0

We recently experienced an issue where our glue connection ran out of IP addresses inside the subnet that it was created in.

Error message:

AWS Glue Error: The specified subnet does not have enough free addresses to satisfy the request

This was due to too many workers/dpus being assigned to the jobs in a single subnet.

I have two questions:

  1. Since glue appears to take a list of connections, will it "roll-over" when one subnet is maxxed out and use the next connection in the list? (at least this is what it shows in Terraform module--a list argument)

  2. How many IP addresses does a G.2x worker use? Since its 2 dpu, does it use 2 IPs? Or is it variable?

已提问 1 年前499 查看次数
2 回答
2
已接受的回答
  1. No, all the cluster will be in a single subnet from a single connection.
  2. One per worker, doesn't matter if the worker is 1DPU or 8
profile pictureAWS
专家
已回答 1 年前
AWS
专家
已审核 1 年前
0

I only know the answer to #2: each DPU (or node) consumes an IP. We have a subnet dedicated to Glue has as many IPs as our Glue DPU quota.

tjtoll
已回答 1 年前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则