我有一个集群ES，从2天前开始出现此错误:
[2016-03-14 15:08:48,342][WARN ][cluster.action.shard] [node-01] [logstash-2016.03.14][2] received shard failed for [logstash-2016.03.14][2], node[72oHnFiXTVqgXaUYKTAu2Q], [P], s[INITIALIZING], indexUUID [AKybrAEZRXebyRxcmzTqJQ], reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[logstash-2016.03.14][2] failed recovery]; nested: EngineCreationFailureException[[logstash-2016.03.14][2] failed to open reader on writer]; nested: FileSystemException[/var/lib/elasticsearch/elasticsearch/nodes/0/indices/logstash-2016.03.14/2/index/_lg_Lucene410_0.dvm: Too many open files]; ]]
如果我运行
curl -XGET 'http://localhost:9200/_nodes?os=true&process=true&pretty=true' | grep "max_file_descriptors"，则输出如下:"max_file_descriptors" : 65535,
"max_file_descriptors" : 65535,
对于文件/etc/security/limit.conf我已经拥有:
elasticsearch - nofile 65535
elasticsearch - memlock unlimited
如果我检查索引的状态，我有一些索引为红色...。因此，logstash出错并崩溃了
最佳答案
只需将elasticsearch-nofile设置为无限制即可。
并确保您与正确的用户一起运行。
关于elasticsearch - Elasticsearch上的“Too many open files”，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/35990055/