Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Heya, Trying To Setup A Gcp Autoscaler For General-Purpose Cpu Instances (

Heya, trying to setup a GCP autoscaler for general-purpose CPU instances ( e2-standard-4 ) but I get into that error: googleapiclient.errors.HttpError: <HttpError 400 when requesting https://compute.googleapis.com/compute/v1/projects/instant-gaming/zones/europe-west1-b/instances?alt=json returned "e2 instances do not support onHostMaintenance=TERMINATE unless they are preemptible.". Details: "[{'message': 'e2 instances do not support onHostMaintenance=TERMINATE unless they are preemptible.', 'domain': 'global', 'reason': 'badRequest'}]">

And I do not wish to use premptible instance since my tasks are not robust enough to support potential termination at any time, here's the full backtrace FYI:

Traceback (most recent call last): File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/auto_scaler.py", line 343, in launch_one instance_id = self.driver.spin_up_worker(resource_conf, worker_prefix, queue, task_id=task_id) File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/cloud_driver.py", line 229, in spin_up_worker instance_id, region = self._spin_up_worker(resource_conf, worker_prefix, queue_name, task_id) File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/gcp_driver.py", line 169, in _spin_up_worker exc, response = f(*args) File "/root/.clearml/venvs-builds/3/task_repository/clearml-apps.git/apps/auto_scaler/gcp_driver.py", line 112, in attempt_launch response = spin_up_client.instances().insert( File "/root/venv/lib/python3.8/site-packages/googleapiclient/_helpers.py", line 131, in positional_wrapper return wrapped(*args, **kwargs) File "/root/venv/lib/python3.8/site-packages/googleapiclient/http.py", line 937, in execute raise HttpError(resp, content, uri=self.uri) googleapiclient.errors.HttpError: <HttpError 400 when requesting returned "e2 instances do not support onHostMaintenance=TERMINATE unless they are preemptible.". Details: "[{'message': 'e2 instances do not support onHostMaintenance=TERMINATE unless they are preemptible.', 'domain': 'global', 'reason': 'badRequest'}]">

  
  
Posted one year ago
Votes Newest

Answers 15


Hi FierceHamster54 , I'll check it out

  
  
Posted one year ago

Perhaps it has something to do with the instance type?

  
  
Posted one year ago

AnxiousSeal95 Okay it seems to work with a compute optimized c2-standard-4 instance

  
  
Posted one year ago

Ohwow, okay Ill test it with another type

  
  
Posted one year ago

As specified in the initial message, the instance type used is e2-standard-4

  
  
Posted one year ago

Hmm, interesting

  
  
Posted one year ago

And this is a standard pro saas deployment, the autoscaler scale up was triggered by the remote execution attempt of a pipeline

  
  
Posted one year ago

FierceHamster54 so it seems the GCP documentation is somewhat misleading... See https://cloud.google.com/compute/docs/instances/setting-vm-host-options#limitations

  
  
Posted one year ago

This is funny cause the auto-scaler on GPU instances is working fine, but as the backtrace suggests it seems to be linked to this instance family

  
  
Posted one year ago

Hi FierceHamster54 can you try another instance type? I just tried with n1 and it works. We are looking to see if it's instance type related

  
  
Posted one year ago

I checked the 'CPU-only' option in the auto-scaler config but that's seemed logic at the time

  
  
Posted one year ago

FierceHamster54 that's super-strange, we tested that some time ago (possibly with different account setting?) and got no error (and the instance was launched) - do you have any additional information that might help us reproduce it?

  
  
Posted one year ago

It sounds like you can create the instance with onHostMaintenance can be set to TERMINATE but can't be changed once you start it, but in actuality it fails creating with this value set...

  
  
Posted one year ago

FierceHamster54 we'll fix it so that this option will be turned off if you choose E2

  
  
Posted one year ago

Nice, thank you for the reactivity ❤

  
  
Posted one year ago
596 Views
15 Answers
one year ago
one year ago
Tags