I have an autoscaling group and the EC2 & ELB health check grace period is set to 10 minutes.
But i also have a target group where the health check is set to mark instances unhealthy after 5 minutes.
What is each health check checking to determine if the instance is unhealthy? What is the difference between the 2 checks
As the instances attached the the target group and autoscaling group are the same, is it going to be the target group health check that will see that an instance is unhealthy first due to the shorter time interval?
Related
Context: I'm using Elasticsearch to record jaeger spans coming from 3 services
Issue: For an unknown reason, everyday from 3pm to midnight the next day, no spans are recorded except for one of those services
Here is the count of record, on a 5 days period, for the service that have no elasticsearch recording issue:
And here, the count of record for the other 2, on the same period:
Question: Does something could periodically happen on ES cluster that could explain this ? What could I check to assert there is no issue on my ES cluster ?
I have a 10 node Elasticsearch cluster, and I would like to know the uptime of the cluster.
I used the cluster stats API and saw a parameter,named "max_uptime" under the jvm object.
Our team observed the cluster for one week and there was no downtime for one week. But the jvm.max_uptime parameter returns only 72 hours. So what does this parameter tells us?.
Also, what would be a good idea to monitor the uptime of an Elasticsearch Cluster?.
I need to move data from google bigquery to elasticsearch instances, For that I have created python dataflow job to copy bigquery table to elasticsearch. But problem is recently they have added IP based restriction on elastic search instances so that it will allow only for specific IP ranges only.
So How can I identify or assign IP ranges of my dataflow workers when I using "DataflowRunner" option?
In the pipeline options you can set the network and the subnetwork you want to use. Each VPC network contains subnets, each with a defined IP range. By defining the subnet to the ip range needed and setting that subnet in the pipeline options you can assign a ip range to your workers.
I have set up Cassandra cluster with 3 nodes in 3 different ec2 instances. each instance is in different availability zone though the datacenter is same.
I am using EC2MultiRegionSnitch, below are my yaml configuration detail
listen address : private ip
broadcast address : publicip
seeds : public of 1 node
While querying networkTopologyKeyspace query I am getting below error "not enough replicas available for query at consistency ONE" . RF for this key space is 3.
Queries on simpleclass keyspace are working perfectly fine.
I started two clusters of ElasticSearch with different names but the other one won't show up either in Marvel or querying for health manually.
curl 'http://127.0.0.1:9200/_cat/health?v'
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1501062768 15:22:48 Cove_dev_cluster yellow 1 1 8 8 0 0 8 0 - 50.0%
But it's running on my screen.
I am assuming you are running both clusters (single nodes I believe in this case) on the same machine... In this case the nodes have a default port range setting of 9200-9300 and they are configured to bind to first available port in the specified range. More details available in Network Settings documentation.
So in your case the other cluster is running on port 9201 most likely. If you check for Marvel or query the health manually on port 9201 you should find the other cluster.
However, if you want to have two nodes participating in the same cluster, then make sure that the cluster name matches in the configuration of both instances of elasticsearch you have running.
Hope this helps.