Indices Created in New Node after Disk Extend

Hi, we recently ran out of volume space on one of our
cluster servers, we extended the diLVM volume as normal but now we notice that
after the extend (plus a reboot) that any new indices are now created under
/nodes/1/indices and not /nodes/0/indices and such are not loaded into ES.

Is there a way to change back to the previous node or
migrate the data across to the new one so it’s searchable via KB?


Anyone believe they may be able to help with this? Since then our cluster has been unstable and noted a number of issues like below:

Caused by: java.nio.file.FileSystemException: /var/lib/elasticsearch/elasticsearch/nodes/0/indices/devicename-2016.02.21/4/index: Too many open files

TranslogException[failed to create new translog file]; nested: FileAlreadyExistsException[/var/lib/elasticsearch/elasticsearch/nodes/0/indices/devicename-2016.03.21/1/translog/translog-17.tlog]