x
/
fuel-plugin-elasticsearch-kibana
Code Issues Proposed changes

Fix the documentation rendering for PDF 

Change-Id: I3cdeede972e6fb2e8b3456ff790be44fe2585f38
This commit is contained in:
Simon Pasquier 2016-04-27 10:47:55 +02:00
parent 03c5edeaee
commit 6d955e5c82
2 changed files with 22 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
doc/source/cluster_operations.rst
View File

@ -39,25 +39,26 @@ want the old indices to be replicated on the new node(s), you need to adjust the
The output below shows that the replication factor of the indices created before the scale-up is
zero. Here, a scale-up was performed on the 3rd of February, so the indices created after that date
(*log-2016.02.04* here) are automatically updated with the correct number of replicas
(number of cluster nodes - 1).
(number of cluster nodes - 1). ::
[root@node-1 ~]# curl <VIP>:9200/_cat/indices?v
health status index pri rep docs.count docs.deleted store.size pri.store.size
green open log-2016.02.03 5 0 270405 0 48.7mb 48.7mb
green open log-2016.02.04 5 2 1934581 0 1gb 384.6mb
health status index pri rep docs.count docs.deleted ....
green open log-2016.02.03 5 0 270405 0 ....
green open log-2016.02.04 5 2 1934581 0 ....
Then, if you want the *log-2016.02.03* index to be replicated, you need to update the
*number_of_replicas* parameter of that index as shown below::
[root@node-1 ~]# curl -XPUT <VIP>:9200/log-2016.02.03/_settings -d '{ "index": { "number_of_replicas": 2 } }'
[root@node-1 ~]# curl -XPUT <VIP>:9200/log-2016.02.03/_settings \
-d '{ "index": {"number_of_replicas": 2}}'
{"acknowledged":true}
[root@node-1 ~]# curl <VIP>:9200/_cat/indices?v
health status index pri rep docs.count docs.deleted store.size pri.store.size
green open log-2016.02.03 5 2 270405 0 146.3mb 48.7mb
green open log-2016.02.04 5 2 1934581 0 1gb 384.6mb
health status index pri rep docs.count docs.deleted ....
green open log-2016.02.03 5 2 270405 0 ....
green open log-2016.02.04 5 2 1934581 0 ....
Note that replicating the old indices on the new node(s) will increase the load on the
cluster as well as the size required to store the data.
@ -71,13 +72,14 @@ status for the Elasticsearch cluster::
[root@node-1 ~]# # the current index health is 'red' after the scale-down
[root@node-1 ~]# curl <VIP>:9200/_cat/indices?v
health status index pri rep docs.count docs.deleted store.size pri.store.size
red open log-2016.02.04 5 2 1934581 0 1gb 384.6mb
health status index pri rep docs.count ....
red open log-2016.02.04 5 2 1934581 ....
[root@node-1 ~]# curl -XPUT <VIP>:9200/log-2016.02.04/_settings -d '{ "index": { "number_of_replicas": 0 } }'
[root@node-1 ~]# curl -XPUT <VIP>:9200/log-2016.02.04/_settings \
-d '{"index": {"number_of_replicas": 0}}'
{"acknowledged":true}
[root@node-1 ~]# # the cluster health is now 'green'
[root@node-1 ~]# curl <VIP>:9200/_cat/indices?v
health status index pri rep docs.count docs.deleted store.size pri.store.size
green open log-2016.02.04 5 0 1934581 0 384.6mb 384.6mb
health status index pri rep docs.count ....
green open log-2016.02.04 5 2 1934581 ....

10
doc/source/user.rst
View File

@ -106,11 +106,11 @@ Here is how to proceed.
server is installed using the following command::
[root@fuel ~]# fuel nodes
id | status | name | cluster | ip | mac | roles |
---|----------|------------------|---------|------------|-------------------|---------------------------|
1 | ready | Untitled (fa:87) | 1 | 10.109.0.8 | 64:18:ef:86:fa:87 | elasticsearch_kibana, ... |
2 | ready | Untitled (12:aa) | 1 | 10.109.0.3 | 64:5f:c6:88:12:aa | elasticsearch_kibana, ... |
3 | ready | Untitled (4e:6e) | 1 | 10.109.0.7 | 64:ca:bf:a4:4e:6e | elasticsearch_kibana, ... |
id | status | name | cluster | ip | mac | roles |
---|----------|------------------|---------|-----|----------------------------|
1 | ready | Untitled (fa:87) | 1 | ... | ... | elasticsearch_kibana |
2 | ready | Untitled (12:aa) | 1 | ... | ... | elasticsearch_kibana |
3 | ready | Untitled (4e:6e) | 1 | ... | ... | elasticsearch_kibana |
#. Then `ssh` to anyone of these nodes (ex. *node-1*) and type the command::