This message was deleted.
# troubleshooting
s
This message was deleted.
v
can you paste the overlord dynamic config here?
s
Copy code
{
  "selectStrategy": {
    "type": "fillCapacity"
  },
  "autoScaler": {
    "envConfig": {
      "numInstances": 1,
      "projectId": "gcp-druid-dev",
      "zoneName": "us-east4-c",
      "managedInstanceGroupName": "druid-middlemanagers"
    },
    "maxNumWorkers": 2,
    "minNumWorkers": 1,
    "type": "gce"
  }
}
Copy code
druid.indexer.autoscale.strategy="gce"
druid.indexer.autoscale.doAutoscale=true
druid.indexer.autoscale.workerVersion=1
druid.indexer.autoscale.originTime=2023-03-30T15:00:00Z
druid.indexer.autoscale.workerIdleTimeout=PT30M
overlord runtime.
t
Is your MIG a zonal or regional MIG?
s
zonal. scope is limited to zonal.
t
I had an issue where the extension was not able to delete instance because it was running in a regional MIG
s
it is trying to delete the instance based on hostname, instead of name.
which causing that 400.
Also this extension is keep on deleting/creating instances every few secs. I have configured the min instance to 1.
v
what are druid.indexer.autoscale.provisionPeriod and druid.indexer.autoscale.terminatePeriod? Depending on pending tasks and these configs middle managers will be created and terminated
s
These are default which is PM1M and PT5M respectively. however cluster don’t have any tasks, even an idle cluster, auto scalar will continuously adding and removing nodes.
v
Do you see any error in the middle manager logs in those nodes? I am wondering whether the issue is with middle managers not coming up properly
s
I don’t see anything unusual, middlemanagers are getting registered and shows up in console also when task is submitted, it is able to run it. however, I do see a problem after sometime, tasks goes into pending state which only runs when new node is added back to cluster by auto scalar.