- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 07:11 AM
We use a "warmup" mechanism to get our DBR instance pool into a state where it has at-least-N instances. The logic is:
- For N repetitions:
- Request a new DBR cluster in the pool (which causes the pool to request an AWS instance)
- Wait for the cluster to report as RUNNING
- If it reports as TERMINATING, abandon this iteration
- Terminating the DBR cluster (to free it up for an upcoming real request)
Normally, this works fine. Lately, however, there's a weird issue: we hit the 1.1.1 situation ("If it reports as TERMINATING, abandon this iteration") for *all* clusters. I have occasionally seen this for 1 cluster (of, say, 40), but never for ALL of them.
What could cause DBR to transition a cluster to "TERMINATING" right after it's created?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2025 07:37 AM
I see that there is some documentation on the subject; I'm exploring whether AWS is actually the culprit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2025 11:47 AM
Aha, found it. I monitored the pool status via the DBR UI, and when a cluster *started* being provisioned, I clicked into it. Then I looked at the event log, and found useful information about failed steps. The underlying error was indeed AWS related (an issue in our role configuration).
