Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can you set the minimum size for hot nodes with autoscaling enabled? #837

Open
nmaves opened this issue Aug 12, 2024 · 1 comment
Open
Labels
question Further information is requested

Comments

@nmaves
Copy link

nmaves commented Aug 12, 2024

We have our hot nodes configured to autoscale. Autoscaling is only for disk space and not other resources. We are now in a situation because we want to increase the minimum size of the cluster for CPU reasons but we can't because of the ingone_changes section. How can we increase the minimum size of the cluster's hot nodes?

    hot = {
      size       = var.size
      zone_count = var.zone_count
      autoscaling = {
        max_size          = var.max_size
        max_size_resource = "memory"
      }
    }
  }

  lifecycle {
    ignore_changes = [
      elasticsearch.hot.size
    ]
  }
@nmaves nmaves added the question Further information is requested label Aug 12, 2024
@tobio
Copy link
Member

tobio commented Sep 7, 2024

we want to increase the minimum size of the cluster for CPU reasons but we can't because of the ingone_changes section

Just to clarify a few points here first. Autoscaling will not decrease the size of data tiers. hot.size defines the current size, which may be increased by autoscaling, but not a minimum that the tier will return to automatically.

That said, it sounds like you want to increase the current deployment size? If so you should be able to remove the ignore_changes block, apply the size change and then add the ignore_changes block back to account for any autoscaling size changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants