不爲也 比不能也

In prior versions of Elasticsearch, the path.data directory included a folder for the cluster name, so that data was in a folder such as $DATA_DIR/$CLUSTER_NAME/nodes/$nodeOrdinal. In 5.0 the cluster name as a directory is deprecated. Data will now be stored in $DATA_DIR/nodes/$nodeOrdinal if there is no existing data. Upon startup, Elasticsearch will check to see if the cluster folder exists an..

Previously, if the path.data setting listed multiple data paths, then a shard would be “striped” across all paths by writing a whole file to each path in turn (in accordance with the index.store.distributorsetting). The result was that files from a single segment in a shard could be spread across multiple disks, and the failure of any one disk could corrupt multiple shards.이전 버전에서는, path.data 설정..

Symbolic links and pathseditElasticsearch 2.0 runs with the Java security manager enabled and is much more restrictive about which paths it is allowed to access. Various paths can be configured, e.g. path.data, path.scripts, path.repo. A configured path may itself be a symbolic link, but no symlinks under that path will be followed.Elasticsearch 2.0은 java security manager가 활성화된 채로 동작한다. 그리고, 어떤 ..