autoscaling

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 of tests which ultimately create a SQL query to return one row of data, where the response size is

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 second case? May be the warning will be available via same url? #!/bin/bash while true do if [ -z $(curl

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? 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 can do it with a custom metric. This was all done in Go, but it will give you the basic idea: Create the

I set up a k8s cluster on microk8s and I ported my application to it. I also added a horizontal auto-scaler which adds pods based on the cpu load. The auto-scaler works fine and it adds pods when there is load beyond the target and when I remove the load after some time it will kill the pods. The problem is I noticed at the exact same moments that the auto-scaler is creating new pods some of the requests fail: POST Response Code : 200 POST Response Code : 200 POST Response Code : 200 POST Response Code : 200 POST Response Code : 200 POST Response Code : 502 java.io.IOException: Server returned

So I've been using Boto in Python to try and configure autoscaling based on CPUUtilization, more or less exactly as specified in this example: http://boto.readthedocs.org/en/latest/autoscale_tut.html However both alarms in CloudWatch just report: State Details: State changed to 'INSUFFICIENT_DATA' at 2012/11/12 16:30 UTC. Reason: Unchecked: Initial alarm creation Auto scaling is working fine but the alarms aren't picking up any CPUUtilization data at all. Any ideas for things I can try? Edit: The instance itself reports CPU utilisation data, just not when I try and create an alarm in

I have a Node.js app that provides a service which cannot be interrupted. However the load to the app varies overtime and to save cost I would like the vm instance machine type to autoscale in function of the load (ie when over 80% CPU utilisation, scale up from 1 vCPU(3.75 GB memory, n1-standard-1) to 2vCPU(7.5 GB memory, n1-standard-2)) Is this possible? PS: I have looked at using the container engine and kubernetes but due to how the app operates, the app cannot be replicated to multiple pods and continue working You can only change the machine type of a stopped instance and an instance is