For some reason my AWS elasticbeanstalk environment, which is using an Application Load Balancer is not balancing the traffic evenly.
All of the instances are the same instance size, but for some reason one instance's CPU is always pegged at 100%. If I delete the instance the other one will just become pegged and the newly created instance will just sit there with minimal load.
I would expect to see both of these at 100% or more evenly balanced at something like 50% and 50%.
Related
I'm setting up an OKD Cluster in a VM via oc cluster up. My VM has 6 GB of RAM and 2 CPUs. Interactions with the internal image registry are very, very slow (multiple minutes to pull or push an image, e.g. when building an application via S2I). At the same time, htop shows me a CPU utilization of 100% for both CPUs within the VM. Is there any way to avoid this issue?
I have a single GCE VM running behind an http load balancer. Its too early to have multiple VMs, saving money.
What happens is this VM seems to be deleted and reinserted randomly by GCE. My tiny web app dies for that duration. I see these in my VM logs:
compute.instances.delete
compute.instances.insert
Seems like GCE maintenance activity. Is there a way to avoid this?
I'm newbie at kubernetes and I'm having problem to understand how I can run persistent pods (Cassandras ones or mysql ones) in ubuntu servers.
Correct me if I'm wrong, kubernetes can scale up or down the pods when it sees that we need more CPU but we are not talking about static code but data that are present in other nodes. So what will do the pod when it receive the request from the balancer? Also, kubernetes has the power to destroy nodes when it sees that the traffic has reduced, so how we can not lose data and not disturb the environment?
You should use volumes to map a directory in the container to persistent disks on the host or other storage
I am running n1-standard-1 (1 vCPU, 3.75 GB memory) Compute Instance , In my android app around 80 users are online write now and cpu Utilisation of instance is 99% and my app became less responsive. Kindly suggest me the workaround and If i need to upgrade , can I do that with same instance or new instance needs to be created.
Since your app is running already and users are connecting to it, you don't want to do the following process:
shut down the VM instance, keeping the boot disk and other disks
boot a more powerful instance, using the boot disk from step (1)
attach and mount any additional disks, if applicable
Instead, you might want to do the following:
create an additional VM instance with similar software/configuration
create a load balancer and add both the original and new VM to it as a backend
change your DNS name to point to the load balancer IP instead of the original VM instance
Now, your users will be randomly sent to a VM that's least-loaded to see the application, and you can add more VMs if your traffic increases.
You did not describe your application in detail, so it's unclear if each VM has local state (e.g., runs a database) or there's a database running externally. You will still need to figure out how to manage the stateful systems such as database or user-uploaded data from all the VM instances, which is hard to advise on given the little information in your quest.
We currently utilize Microsoft Azure to host a MariaDB 10.1 Galera Cluster hosted on two VM's set with a Load Balancer. This functions well for our NORMAL operations, however, we would like to utilize Azure's autoscaling ability to spin up new nodes in the Galera Cluster when necessary. We have unscheduled excessive load at times which is too much for even our current cluster. It would be amazing if we had the ability to scale up as needed and then scale down when done.
Being that Galera is pre-configured with specific IP, is there any way to have the new instances that would be spun up, join the Load Balancer and Galera Cluster?