recovery issues when using multiple entries in path.data #18217
Labels
discuss
:Distributed Indexing/Recovery
Anything around constructing a new shard, either from a local or a remote source.
Elasticsearch version: 2.3.2
JVM version: 1.8.0_74
OS version: OSX 10.11.4
Description of the problem including expected versus actual behavior:
When using multiple entries for
path.data
on a node and then simulating removing a drive from the node, the node does not mark the shards that were on that shard as unavailable so re-assignment can happen. I would expect to see some initial errors get thrown, but after a little bit of time, see the shards that were assigned to the missing or timing out filesystem to be allocated elsewhere in the cluster (or the same node but a different data path).Steps to reproduce:
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: