Shard distribution using multiple path.data locations


#1

We have just added additional storage to our single node elasticsearch "cluster". I noticed that elasticsearch did not relocated some of the existing shards to the new location to use the storage evenly... thats not perfect but it's ok.

But i also noticed that every newly created index and all of it's shards are now also allocated to the new storage, which is kind of bad cause i have no advantages regarding search and index performance if elasticsearch is doing so... Although it's creating the folders in both paths (can't understand why) - we are using 2 shards and 0 replicas.

new storage:

user@host:~# ll /logdata2/nodes/0/indices/11bkYN0fQlaJ8Oc2qXBPmA/
drwxr-xr-x 5 elasticsearch elasticsearch 4.0K Apr 27 00:00 1
drwxr-xr-x 5 elasticsearch elasticsearch 4.0K Apr 27 00:00 0
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Apr 27 08:00 _state

vs. old storage:

user@host:~# ll /logdata/logging/nodes/0/indices/11bkYN0fQlaJ8Oc2qXBPmA
drwxr-xr-x 2 elasticsearch elasticsearch 4.0K Apr 27 08:00 _state

Is there a way to influence the shard allocation on different path.data locations?


(Mark Walkom) #2

Nope, it'll auto-balance but I am not sure on if that is a shard or space type balance.


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.