After ES restart I can't see the old data in kibana anymore, just the data after restart and the saved dashboards, visualizes and queries are also gone. I started elasticsearch already with debug level, but there is no error.
curl localhost:9200/_cat/indices?v show also jast the data after restart
but in the data directory are the indices there
Did you try to restart Elasticsearch without any plugin? Probably there are problems with one of them...
Are you sure, that in your network only one cluster exists? Make sure to use a unique cluster name!
thank you for your answer. The system(linux) is a standalone localhost installation ELK is installed on the same machine. ELK is default installation downloaded from elastic.co and prepared for linux (rm all dll and exe). There is no extra plugin installed only curator what I start with cron.
this is my ES config what i start
-bash-4.1$ cat /opt/elkapp/elasticsearch/config/elasticsearch.yml
################################### Cluster ###################################
# Cluster name identifies your cluster for auto-discovery. If you're running
# multiple clusters on the same network, make sure you're using unique names.
#
# cluster.name: elasticsearch
#################################### Node #####################################
# Node names are generated dynamically on startup, so you're relieved
# from configuring them manually. You can tie this node to a specific name:
#
node.name: "ELK Prod"
# Every node can be configured to allow or deny being eligible as the master,
# and to allow or deny to store the data.
#
# Allow this node to be eligible as a master node (enabled by default):
#
node.master: true
#
# Allow this node to store data (enabled by default):
#
node.data: true
# You can exploit these settings to design advanced cluster topologies.
#
# 1. You want this node to never become a master node, only to hold data.
# This will be the "workhorse" of your cluster.
#
# node.master: false
# node.data: true
#
# 2. You want this node to only serve as a master: to not store any data and
# to have free resources. This will be the "coordinator" of your cluster.
#
# node.master: true
# node.data: false
#
# 3. You want this node to be neither master nor data node, but
# to act as a "search load balancer" (fetching data from nodes,
# aggregating results, etc.)
#
# node.master: false
# node.data: false
# Use the Cluster Health API [http://localhost:9200/_cluster/health], the
# Node Info API [http://localhost:9200/_nodes] or GUI tools
# such as <http://www.elasticsearch.org/overview/marvel/>,
# <http://github.com/karmi/elasticsearch-paramedic>,
# <http://github.com/lukas-vlcek/bigdesk> and
# <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.
# A node can have generic attributes associated with it, which can later be used
# for customized shard allocation filtering, or allocation awareness. An attribute
# is a simple key value pair, similar to node.key: value, here is an example:
#
# node.rack: rack314
# By default, multiple nodes are allowed to start from the same installation location
# to disable it, set the following:
# node.max_local_storage_nodes: 1
#################################### Index ####################################
index.store.type: niofs
index.store.fs.memory.enabled: true
index.gateway.type: none
gateway.type: none
#################################### Paths ####################################
# Path to directory containing configuration (this file and logging.yml):
#
# path.conf: /path/to/conf
# Path to directory where to store index data allocated for this node.
path.data: /opt/elasticsearch
path.work: /opt/elasticsearch/tmp
path.logs: /opt/elasticsearch/logs
############################## Network And HTTP ###############################
transport.tcp.port: 9300
transport.tcp.compress: true
http.port: 9200
################################## Slow Log ##################################
# Shard level query and fetch threshold logging.
# index.search.slowlog.threshold.query.warn: 10s
# index.search.slowlog.threshold.query.info: 5s
# index.search.slowlog.threshold.query.debug: 2s
# index.search.slowlog.threshold.query.trace: 500ms
# index.search.slowlog.threshold.fetch.warn: 1s
# index.search.slowlog.threshold.fetch.info: 800ms
# index.search.slowlog.threshold.fetch.debug: 500ms
# index.search.slowlog.threshold.fetch.trace: 200ms
# index.indexing.slowlog.threshold.index.warn: 10s
# index.indexing.slowlog.threshold.index.info: 5s
# index.indexing.slowlog.threshold.index.debug: 2s
# index.indexing.slowlog.threshold.index.trace: 500ms
################################## GC Logging ################################
# monitor.jvm.gc.young.warn: 1000ms
# monitor.jvm.gc.young.info: 700ms
# monitor.jvm.gc.young.debug: 400ms
# monitor.jvm.gc.old.warn: 10s
# monitor.jvm.gc.old.info: 5s
# monitor.jvm.gc.old.debug: 2s
#
# http.jsonp.enable: true
http.cors.allow-origin: "/.*/"
http.cors.enabled: true
ok then how can it be that all of the data is in /opt/elasticsearch/elasticsearch/nodes/0 there but if i ask over localhost:9200 then ES doesn't see anything just the data what the current running process saved.
if i restart the ES the created default index pattern is gone [logstash-]YYYY.MM.DD. and if i create again after restart i cant see the old data.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.