Elasticsearch:Per shard per node VS Multiple shards per node? -


most article tells me,per shard per node best practices,but,if server has more 1 hard disk,and es create new index every day,then usage of disk have great difference.

so,if create multiple shards(the number equals disks number) of node,then usage of disk balance?

edit:

here es configuration:

path.data: /data1/es1,/data2/es1,/data3/es1 

here id df -h shows:

/dev/sdb1       733g  291g  405g  42% /data1 /dev/sdc1       733g  244g  453g  35% /data2 /dev/sdd1       733g  116m  696g   1% /data3 

you still go single shard per node , use multiple disks. elasticsearch has config variable called path.data array accepts multiple locations, if define more 1 location (one per disk example) use both disks , benefit increased iops.


Comments

Popular posts from this blog

Ansible - ERROR! the field 'hosts' is required but was not set -

customize file_field button ruby on rails -

SoapUI on windows 10 - high DPI/4K scaling issue -