autoscaling

Afaik, y-axis cant be made to auto scale when using x-range sliders. Y range is chosen with respect to the y values of the whole x range and does not change after zooming-in. This is especially annoying with candlestick charts in volatile periods. When you zoom-in using x-range slider, you essentially get flat candlesticks as their fluctuations only cover a very small part of the initial range. After doing some research it seems that some progress has been made here: https://github.com/plotly/plotly.js/pull/2364 . Anyone knows if there is a working solution for plotly.py ? Thanks for your time

I'm running servers in a AWS auto scale group. The running servers are behind a load balancer. I'm using the ELB to mange the auto scaling groups healthchecks. When servers are been started and join the auto scale group they are currently immediately join to the load balancer. How much time (i.e. the healthcheck grace period) do I need to wait until I let them join to the load balancer? Should it be only after the servers are in a state of running? Should it be only after the servers passed the system and the instance status checks? There are two types of Health Check available for Auto

I was trying to fetch auto scaling groups with Application tag value as 'CCC'. The list is as below, gweb prd-dcc-eap-w2 gweb prd-dcc-emc gweb prd-dcc-ems CCC dev-ccc-wer CCC dev-ccc-gbg CCC dev-ccc-wer The script I coded below gives output which includes one ASG without CCC tag. #!/usr/bin/python import boto3 client = boto3.client('autoscaling',region_name='us-west-2') response = client.describe_auto_scaling_groups() ccc_asg = [] all_asg = response['AutoScalingGroups'] for i in range(len(all_asg)): all_tags = all_asg[i]['Tags'] for j in range(len(all_tags)): if all_tags[j]['Key'] == 'Name':

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 much, but since it's not 0%, some task is currently running on that pod. If it's a long lasting task

Using Solr version 7.3.1 Starting with 3 nodes: I have created a collection like this: wget "localhost:8983/solr/admin/collections?action=CREATE&autoAddReplicas=true&collection.configName=my_col_config&maxShardsPerNode=1&name=my_col&numShards=1&replicationFactor=3&router.name=compositeId&wt=json" -O /dev/null In this way I have a replica on each node. GOAL: Each shard should add a replica to new nodes joining the cluster. When a node are shoot down. It should just go away. Only one replica for each shard on each node. I know that it should be possible with the new AutoScalling API but I am