Commit 02fdb010 authored by Michal Wasilewski's avatar Michal Wasilewski

capitalize beginning of sentences and headlines

parent 702486c4
......@@ -34,17 +34,17 @@ PUT _cluster/settings
## Resizing cluster ##
### adding new availability zones ###
### Adding new availability zones ###
https://www.elastic.co/guide/en/cloud-enterprise/current/ece-resize-deployment.html
adding and removing availability zones was tested. elastic.co decides whether to have a dedicated VM for master or to nominate master from among the data nodes. The number of availability zones determines in how many zones there will be data nodes (you might actually end up with more VMs if elastic.co decides to run master on a dedicated node).
Adding and removing availability zones was tested. elastic.co decides whether to have a dedicated VM for master or to nominate master from among the data nodes. The number of availability zones determines in how many zones there will be data nodes (you might actually end up with more VMs if elastic.co decides to run master on a dedicated node).
### resizing instances ###
### Resizing instances ###
The way it works is new machines are created with the desired spec, they are then brought online, shards are moved across and once that is complete the old ones are taken offline and removed. This worked very smoothly.
we can scale up and down. resizing is done live.
We can scale up and down. Resizing is done live.
## Monitoring ##
......@@ -59,4 +59,4 @@ There are 3 places where you check cluster performance:
Since we cannot use our Alertmanager, Elasticsearch Watchers have to be used for alerting. They will be configured on the Elastic cluster used for storing monitoring indices.
blackbox probes cannot provide us with sufficient granularity of state reporting.
Blackbox probes cannot provide us with sufficient granularity of state reporting.
......@@ -175,9 +175,9 @@ queue = Sidekiq::Queue.new('repository_import')
queue.each { |job| job.delete if id_list.include?(job.args[0]) }
```
### Kill running jobs (as opposed to removing them from a queue) ###
### Kill running jobs (as opposed to removing jobs from a queue) ###
to get a list of jobs that you want to kill:
To get a list of jobs that you want to kill you'll need to use the rails console. Here's an example of getting a list of jobs of specific, elastic search indexer types:
```ruby
types_of_jobs_to_kill = ["elastic_indexer", "elastic_commit_indexer", "elastic_namespace_indexer"]
workers = Sidekiq::Workers.new # get an object holding references to all running jobs, see sidekiq docs for more info
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment