Docker ContainerでのElasticsearch - 単純な再起動後に "データディレクトリに書き込めませんでした"

Question

数週間前ログファイルの負荷をより良く処理するためにelkスタック（elasticsearch、logstash、kibana）を作成しました。

すべてが完全に機能しました。今日私はいくつかの新しいパターンをlogstashに呼び出しました。何らかの理由でdocker-compose down && docker-compose up -dで再起動しました。

これ以上elasticsearchは起動しません。

root@xyz:/srv/elk# docker-compose logs elasticsearch 
Attaching to elk_elasticsearch_1 
elasticsearch_1 | [2017-07-01T07:34:36,859][INFO ][o.e.n.Node    ] [lw-e01] initializing ... 
elasticsearch_1 | [2017-07-01T07:34:36,999][INFO ][o.e.e.NodeEnvironment ] [lw-e01] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/mapper/HDD-ELK)]], net usable_space [19.1gb], net total_space [49gb], spins? [possibly], types [ext4] 
elasticsearch_1 | [2017-07-01T07:34:36,999][INFO ][o.e.e.NodeEnvironment ] [lw-e01] heap size [3.9gb], compressed ordinary object pointers [true] 
elasticsearch_1 | [2017-07-01T07:34:37,635][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [lw-e01] uncaught exception in thread [main] 
elasticsearch_1 | org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Failed to created node environment 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:127) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:114) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:67) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.cli.Command.main(Command.java:88) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:91) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:84) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 | Caused by: java.lang.IllegalStateException: Failed to created node environment 
elasticsearch_1 |  at org.elasticsearch.node.Node.<init>(Node.java:265) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.node.Node.<init>(Node.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap$6.<init>(Bootstrap.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:360) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  ... 6 more 
elasticsearch_1 | Caused by: java.io.IOException: failed to write in data directory [/usr/share/elasticsearch/data/nodes/0/indices/a94kXbSER2CE97qdPhgVLA/_state] write permission is required 
elasticsearch_1 |  at org.elasticsearch.env.NodeEnvironment.tryWriteTempFile(NodeEnvironment.java:1075) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.env.NodeEnvironment.assertCanWrite(NodeEnvironment.java:1047) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:277) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.node.Node.<init>(Node.java:262) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.node.Node.<init>(Node.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap$6.<init>(Bootstrap.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:360) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  ... 6 more 
elasticsearch_1 | Caused by: java.nio.file.FileAlreadyExistsException: /usr/share/elasticsearch/data/nodes/0/indices/a94kXbSER2CE97qdPhgVLA/_state/.es_temp_file 
elasticsearch_1 |  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:88) ~[?:?] 
elasticsearch_1 |  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:?] 
elasticsearch_1 |  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:?] 
elasticsearch_1 |  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) ~[?:?] 
elasticsearch_1 |  at java.nio.file.Files.newByteChannel(Files.java:361) ~[?:1.8.0_131] 
elasticsearch_1 |  at java.nio.file.Files.createFile(Files.java:632) ~[?:1.8.0_131] 
elasticsearch_1 |  at org.elasticsearch.env.NodeEnvironment.tryWriteTempFile(NodeEnvironment.java:1072) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.env.NodeEnvironment.assertCanWrite(NodeEnvironment.java:1047) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:277) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.node.Node.<init>(Node.java:262) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.node.Node.<init>(Node.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap$6.<init>(Bootstrap.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:360) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:123) ~[elasticsearch-5.4.0.jar:5.4.0] 
elasticsearch_1 |  ... 6 more 

OK、それは簡単なアクセス許可、問題のように見えますが、また、chown -R 1000.1000 elasticsearch/後にそれがクラッシュ（およびその他の所有権を設定します）。

セットアップ：I docker-composeプロジェクト用のLVMを備えたサーバーをセットアップします。 docker-compose.ymlでは、私は3つのサービスについて説明しました。あなたは、私が直接、私はあまりにもXPack（現時点では）インストールの公式画像を使用していない見ることができるように

version: '3' 

services: 
    elasticsearch: 
    image: my/elasticsearch/image:5.4.0 
    volumes: 
     - ./elasticsearch/data:/usr/share/elasticsearch/data 
     - ./elasticsearch/config:/usr/share/elasticsearch/config 
     - /etc/localtime:/etc/localtime:ro 
    environment: 
     ES_JAVA_OPTS: "-Xmx4g -Xms1g" 
    ulimits: 
     memlock: 
     soft: -1 
     hard: -1 
    networks: 
     - nginx_net 

    logstash: 
    image: my/logstash/image:5.4.0 
    command: ["logstash", "-f", "/etc/logstash.conf"] 
    volumes: 
     - ./logstash.conf:/etc/logstash.conf:ro 
     - ./logstash.yml:/etc/logstash/logstash.yml:ro 
     - ./GeoDb/GeoLite2-City.mmdb:/GeoLite2-City.mmdb:ro 
     - ./patterns:/etc/logstash/patterns:ro 
     - /etc/localtime:/etc/localtime:ro 
    ports: 
     - "5044:5044" 
    environment: 
     LS_JAVA_OPTS: "-Xmx1g -Xms512m" 
    depends_on: 
     - elasticsearch 
    networks: 
     - nginx_net 

    kibana: 
    image: my/kibana/image:5.4.0 
    volumes: 
     - ./kibana/config/:/usr/share/kibana/config 
     - ./kibana/config/kibana.yml:/etc/kibana/kibana.yml 
     - /etc/localtime:/etc/localtime:ro 
    depends_on: 
     - elasticsearch 
    networks: 
     - nginx_net 

networks: 
    nginx_net: 
    external: true 

、3枚のすべての画像は私が異なるやるこの

FROM elasticsearch:5.4.0 

RUN bin/elasticsearch-plugin install x-pack --batch 

scondの事のように見えます私は名前付きボリュームを使用していないのですか？これは、Project全体を含む1つのフォルダと、LVM Managementのための方が良いという理由からです。

root@xyz:/srv/elk# ls -l 
insgesamt 43488 
-rw-r--r-- 1 root root  1514 Jul 1 09:34 docker-compose.yml 
drwxr-xr-x 4 1000 1000  4096 Mai 18 17:43 elasticsearch 
drwxr-xr-x 3 root root  4096 Mai 21 12:49 GeoDb 
-rw-r--r-- 1 root root 25398754 Mai 21 12:49 GeoLite2-City.tar.gz 
-rw-r--r-- 1 root root 19074950 Mai 21 12:03 GeoLiteCity.dat 
drwxr-xr-x 3 root root  4096 Mai 14 16:20 kibana 
-rw-r--r-- 1 root root  5523 Jul 1 09:02 logstash.conf 
-rw-r--r-- 1 root root  4708 Jun 3 11:25 logstash.yml 
drwx------ 2 root root 16384 Mai 17 23:40 lost+found 
drwxr-xr-x 2 root root  4096 Jun 7 22:08 patterns 
-rwxr-xr-x 1 root root  168 Mai 21 12:49 update-geoip.sh 
root@xyz:/srv/elk# du -hs elasticsearch/ 
28G  elasticsearch/ 

私は名前のボリュームを使用するだけでなく、にファイルを保存するためにDIRを指定するlocal-persistのようなプラグインについて読みました。しかし、ドッカーはプロダクションでプラグインを使用しないことをお勧めします。

私はどんなアイデア/リンクでも大変うれしいです。

Answer 1

OKシンプル：（私の場合）の実行ドッキングウィンドウ-構成するプロジェクトのメインフォルダ内rm elasticsearch/data/nodes/0/indices/a94kXbSER2CE97qdPhgVLA/_s‌​tate/.es_temp_fileは私がjava.nio.file.FileAlreadyExistsException

Answer 2

以上に正確にパスの外観を把握するには...もう一度

をELを開始助けました答えは私のために働かなかった。それはDockerの記憶上の問題に終わった。 Boosting Dockerのメモリ割り当てがそれを解決しました。