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 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南