Failed to write index state due to incorrect syntax in directory name

[MikeZuehlke]

I tried to run elasticsearch 1.3.2 under Windows (7 Enterprise) but it failed due to an invalid directory name "localhost:9200" which contains a colon.

The version 1.3.0, 1.3.1 are also effected. Version 1.2.4 works. On Linux the problem does not exist because colons can be used in directory and file names.

Here is the full stacktrace

[2014-09-19 14:12:17,210][WARN ][gateway.local.state.meta ] [Wolf] [localhost:9200]: failed to write index state
java.io.FileNotFoundException: D:\dev\elasticsearch-1.3.2\data\elasticsearch\nodes\0\indices\localhost:9200\_state\state
-1 (The filename, directory name, or volume label syntax is incorrect)
        at java.io.FileOutputStream.open(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:212)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:165)
        at org.elasticsearch.gateway.local.state.meta.LocalGatewayMetaState.writeIndex(LocalGatewayMetaState.java:359)
        at org.elasticsearch.gateway.local.state.meta.LocalGatewayMetaState.clusterChanged(LocalGatewayMetaState.java:21
7)
        at org.elasticsearch.gateway.local.LocalGateway.clusterChanged(LocalGateway.java:207)
        at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:450)
        at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(P
rioritizedEsThreadPoolExecutor.java:153)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:722)

[MikeZuehlke]

After playing with version 1.2.4 I faced the same error. Deleting the data directory helped to resolve the issue. I tried again the versions 1.3.* after deleting the data directory and IT WORKS.

[clintongormley]

OK - so looks like this was caused by an invalid file name. Did you move the data directory from a linux box? How did that directory come to exist?

I'm going to close this in favour of #6736