ES shards red status after old indices removing

[iTonych]

Hi guys. We was removed old indices files and now ES dont work properly.
In ES log we find:
"failed to fetch index version after copying it over"
And we find solution - #4674
But it didnt helped:)
Some shards are red. Also ES log file growing and growing and growing.
I never worked with ES before and have no idea how to fix it.
http://localhost:9200/_refresh show
{"_shards":{"total":1192,"successful":1058,"failed":0}}

[iTonych]

[2015-09-04 11:50:48,452][WARN ][cluster.action.shard ] [Laura Dean] [logstash-2015.04.24][1] sending failed shard for [logstash-2015.04.24][1], node[O4MVugiuQg2vMrBo93wEXQ], [P], s[INITIALIZING], indexUUID [WicD5EdOTUaPy3glrY34gg], reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[logstash-2015.04.24][1] failed to fetch index version after copying it over]; nested: IndexShardGatewayRecoveryException[[logstash-2015.04.24][1] shard allocated for local recovery (post api), should exist, but doesn't, current files: [segments_1g]]; nested: FileNotFoundException[No such file [_9p6.si]]; ]]

[iTonych]

1.4.0 elasticsearch version
1.4.2 logstash verison

[clintongormley]

Hi @iTonych

The correct place to ask questions like these is in the forums: https://discuss.elastic.co/

It looks like the index is corrupt. You should delete it. Deleting via the API should work but failing that, just delete the shard on disk. I also recommend upgrading.

[iTonych]

Thanks @clintongormley ! It works)