autoscaling

问题 I've two EC2 instances behind an ELB and in an Auto Scaling Group. The Scale-up policy is as below: CPUUtilization >= 70 for 300 seconds (Adds one server) While Atoscaling activity is taking place, load on existing instances is already 99% and connections are being dropped. Is there any way to handle this more efficiently? 回答1: The trick to Auto Scaling is in defining an alarm that can accurately identify the load of your system. CPU Utilization is not always the right measure to use -- your

问题 We have multiple SSL certificates for a group of EC2 server (due to legacy constraints). We have multiple ELBs pointing at this group, each terminating the SSL for a specific certificate. We now want to move to auto-scaling instead of a hard-coded list of EC2 instances. Will a single auto-scaling group work with multiple ELBs? 回答1: Yes it works (we do this since some years). The autoscaling group automatically attaches new instances to each ELB. If you use the command line tools you can

问题 My understanding is that in Kubernetes, when using the Horizontal Pod Autoscaler, if the targetCPUUtilizationPercentage field is set to 50%, and the average CPU utilization across all the pod's replicas is above that value, the HPA will create more replicas. Once the average CPU drops below 50% for some time, it will lower the number of replicas. Here is the part that I am not sure about: What if the CPU utilization on a pod is 10%, not 0%?Will HPA still terminate the replica? 10% CPU isn't

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 5 years ago . Right now I am using the Auto Scaling Command Line Tool to launch a new EC2 instance once per day and run a script that terminates itself upon completion. Now I need to do the same thing with a different script, but this one requires several Python modules to be installed.

问题 Firestore has a limit of 500 writes per second to "a collection in which documents contain sequential values in an indexed field" https://cloud.google.com/firestore/quotas#writes_and_transactions What scenarios can I increase the limit to 10,000 writes per second in ONE collection? Assuming I use Best Practices of keeping Document IDs distributed relatively evenly throughout the key range. A) What if the documents do not contain any sequential values? E.g. the only fields I have in each

问题 I need to run a clean up script every time my spot instance is scheduled for termination. I have two reasons for termination: A price for spot instance exceeds my bid Downscaling caused by scaling policies of autoscaling group (based on average cluster cpu usage in 5 mins, random instance is terminated). I did like the simple script below I found on this blog. It covers first case and gives me 2 minutes to clean up before shutdown. Is there an easy way to get such 2-minute notification for

问题 I'm having a problem with scaling the number of concurrent users on my system. From my tests, scaling the number of concurrent users seems to directly increase the duration of a request in a linear relationship. I am running a Java Web Application deployed on a (virtual) Ubuntu Quad Core machine with 16Gb RAM. I am using Apache Tomcat 7 and a MySQl 5.5 Database. Tomcat and MySQL are using the default settings - I have not configured them in any way. I am using Apache Benchmark to run a number

问题 So I have an AWS CloudFormation template with 3 different instance 'types' (Server, Agent, Relay) I'm using AutoScaling to dynamically launch X number of instances of a type. My problem is that I need all of the IPs of these servers from Outputs of the template, preferably sorted into sections. i.e. Servers: x.x.x.x y.y.y.y Relays: z.z.z.z Agents: a.a.a.a How do I get just the instance Ids from the Outputs? (I can get the IPs from the IDs) Attached Template: { "AWSTemplateFormatVersion" :

问题 When I resize a replication controller using kubectl, if the cluster does not have enough resource, there will have one or more pods always in pending. Is there has any tool will auto resize GKE cluster when the resource is running out? 回答1: I had a similar requirement (for the Go build system): wanted to know when scheduled vs. available CPU or memory was > 1, and scale out nodes when that was true (or, more accurately, when it was ~.8). There's not a built-in metric, but as you suggest you

问题 I'm trying to do performance testing for my AWS auto scaling group using jmeter. Firstly, I did scale-in/out testing. I set the threshold to be 70% cpu utilization for 2 periods, each period is 2 minutes. The ELB works fine, and the requests was distributed to all EC2 instances in auto scaling group, in spite of un-equality, after the system scale-out. In next, I want to test whether the two instances' load can be twice of one instance's. I fixed the instance number of auto scaling group, I