horizontal-scaling

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 years ago . Improve this question How can I create a large number of rq worker processes in a VPS easily? Right now I'm manually opening a terminal and running python3 worker.py in it, and then repeating this until I get a satisfying number of worker instances running. I know this is not a

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 years ago . Improve this question How can I create a large number of rq worker processes in a VPS easily? Right now I'm manually opening a terminal and running python3 worker.py in it, and then repeating this until I get a satisfying number of worker instances running. I know this is not a

问题 Is their a configuration in Kubernetes horizontal pod autoscaling to specify a minimum delay for a pod to be running or created before scaling up/down? For example with something like: # I am looking for a flag like this --horizontal-pod-autoscale-initial-upscale-delay=5m0s # Similar to these existing flags --horizontal-pod-autoscaler-downscale-delay=2m0s --horizontal-pod-autoscaler-upscale-delay=2m0s Having as a result: Wait for 5 min before any upscale occur After 5 min, perform a downscale

问题 I have a running GKE cluster with an HPA using a target CPU utilisation metric. This is OK but CPU utilisation is not the best scaling metric for us. Analysis suggests that active connection count is a good indicator of general platform load and thus, we'd like to look into this as our primary scaling metric. To this end I have enabled custom metrics for the NGINX ingress that we use. From here we can see active connection counts, request rates, etc. Here is the HPA specification using the

问题 I am trying to set up an horizontal pod auto scaling in GKE. No proper documentation found to reduce the --horizontal-pod-autoscaler-sync-period to 5 sec using kube-controller-manager. In the below link it says there is a possibility of changing the flags: https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/ Is there any proper implementation steps to this? 回答1: You are not able do this on GKE, EKS and other managed clusters. In order to change/add flags

问题 After some googling I have found: Note from mysql docs: MySQL Cluster automatically shards (partitions) tables across nodes, enabling databases to scale horizontally on low cost, commodity hardware to serve read and write-intensive workloads, accessed both from SQL and directly via NoSQL APIs. Can relational database be horizontal scaling? Will it be somehow based on NoSQL database? Do someone have any real world example? How can I manage sql requests, transactions, and so on in such database

问题 I built an app on node.js using Docker and I'm not sure how to scale it on a Kubernetes cluster so that I take the most out of my cluster hardware. From a performance perspective which of the following is better: clusterize my node app and run as many containers as needed or just run as many containers as needed without clustering ? When I say clustering I mean this https://nodejs.org/api/cluster.html My app is a simple CRUD Api backed by mongoDB. We estimate that it will have 1000 concurrent

问题 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

问题 Given that JavaServer Faces is inherently stateful on the server side, what methods are recommended for horizontally scaling a JSF 2.0 application? If an application runs multiple JSF servers, I can imagine the following scenarios: Sticky Sessions: send all requests matching a given session to the same server. Question: what technology is commonly used to achieve this? Problem: server failure results in lost sessions... and generally seems like fragile architecture, especially when starting

问题 I am currently exploring solutions in order to archive and provide a web search engine for enormous documentation data. I have firstly started my search looking for search engine solution and I end up with the conclusion that Elasticsearch was one of the best one when you have to deal with huge amount of data. I have read that it scale easily and out of the box and i was convinced. Then I looked about No SQL database and because of the number of actors, i spent more time on my searching and I