Not able to create index logstash-* in elasticsearch 6.2.2

Elastic Stack Elasticsearch
1

I have re insatlled elasticsearch 6.2.2 and now i am not able to create index for logstash-*.

GET _cluster/health
{
"cluster_name": "Development",
"status": "red",
"timed_out": false,
"number_of_nodes": 3,
"number_of_data_nodes": 1,
"active_primary_shards": 17,
"active_shards": 17,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 36,
"delayed_unassigned_shards": 0,
"number_of_pending_tasks": 0,
"number_of_in_flight_fetch": 0,
"task_max_waiting_in_queue_millis": 0,
"active_shards_percent_as_number": 32.075471698113205
}
// cant understand how to proceed with it.Please guide me.

2

Why do you have 3 nodes, but only 1 data node? If you are starting out with Elasticsearch, I would recommend starting with a single node with default configuration. Just because you can have dedicated node types does not mean you should.

3

As of now data are flowing in only 1 node

4

What are the other nodes for?

5

Ideally its suppose to be if any one node goes down the other node can replace it.I am new to this area.If I am wrong please guide me.Previously with elasticsearch 5.6.3 it was working fine.

6

If you are looking for high availability you should set up 3 nodes with default configuration (are master eligible and can hold data). Make sure they can connect to each other and set minimum_master_nodes to 2 according to these guidelines to avoid split-brain scenarios. Configure indices to have at least 1 replica so you have a copy of each shard even if one node is lost.

7

I have alreay given that

8

Can you show the content of the elasticsearch.yml files for the three nodes?

9

my doubt is like why I cant create any index pattern.and why the status is red?

10

The issue is that the status is red, which prevents you from making any changes. If we can see the configuration files we may be able to identify why it is red in the first place.

11

======================== Elasticsearch Configuration =========================

NOTE: Elasticsearch comes with reasonable defaults for most settings.

Before you set out to tweak and tune the configuration, make sure you

understand what are you trying to accomplish and the consequences.

The primary way of configuring a node is via this file. This template lists

the most important settings you may want to configure for a production cluster.

Please consult the documentation for further information on configuration options:

https://www.elastic.co/guide/en/elasticsearch/reference/index.html

---------------------------------- Cluster -----------------------------------

Use a descriptive name for your cluster:

cluster.name: Development

------------------------------------ Node ------------------------------------

Use a descriptive name for the node:

node.name: ${HOSTNAME}
node.master: false
node.data: true
#node.name: node-1

Add custom attributes to the node:

#node.attr.rack: r1

----------------------------------- Paths ------------------------------------

Path to directory where to store the data (separate multiple locations by comma):

#path.data: /path/to/data

Path to log files:

path.logs: /var/log/elasticsearch

----------------------------------- Memory -----------------------------------

Lock the memory on startup:

#bootstrap.memory_lock: true

Make sure that the heap size is set to about half the memory available

on the system and that the owner of the process is allowed to use this

limit.

Elasticsearch performs poorly when the system is swapping the memory.

---------------------------------- Network -----------------------------------

Set the bind address to a specific IP (IPv4 or IPv6):

network.host: [*]

Set a custom port for HTTP:

http.port: 9200

For more information, consult the network module documentation.

--------------------------------- Discovery ----------------------------------

Pass an initial list of hosts to perform discovery when new node is started:

The default list of hosts is ["127.0.0.1", "[::1]"]

discovery.zen.ping.unicast.hosts: ["","**","","*"]

Prevent the "split brain" by configuring the majority of nodes (total number of master-eligible nodes / 2 + 1):

discovery.zen.minimum_master_nodes: 2

For more information, consult the zen discovery module documentation.

---------------------------------- Gateway -----------------------------------

Block initial recovery after a full cluster restart until N nodes are started:

gateway.recover_after_nodes: 2

For more information, consult the gateway module documentation.

---------------------------------- Various -----------------------------------

Require explicit names when deleting indices:

#action.destructive_requires_name: true

12

I am able to make status green

13

Excellent. That should allow you to make the changes you wanted. When posting config, please use the formatting tools in the UI so it is readable.

14

Still i am not able to craete logstash index
PUT /logstash-2015.05.18
{
"mappings": {
"log": {
"properties": {
"geo": {
"properties": {
"coordinates": {
"type": "geo_point"
}
}
}
}
}
}
}

response
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "[include_in_all] is not allowed for indices created on or after version 6.0.0 as [_all] is deprecated. As a replacement, you can use an [copy_to] on mapping fields to create your own catch all field."
}
],
"type": "mapper_parsing_exception",
"reason": "Failed to parse mapping [default]: [include_in_all] is not allowed for indices created on or after version 6.0.0 as [_all] is deprecated. As a replacement, you can use an [copy_to] on mapping fields to create your own catch all field.",
"caused_by": {
"type": "mapper_parsing_exception",
"reason": "[include_in_all] is not allowed for indices created on or after version 6.0.0 as [_all] is deprecated. As a replacement, you can use an [copy_to] on mapping fields to create your own catch all field."
}
},
"status": 400
}

15

What is this? Is this what is in the config or have you altered it to hide the IP addresses?

How many of the nodes are master eligible?

16

I have hidden it

17

Can anyone help me in creating logstash index in elasticsearch 6.2.2?

18

Is there anything in the Elasticsearch logs? Is the cluster state green with all nodes being part of the cluster?

19

yes we are getting but we are not able to able to create logstash index

20

What error message are you getting when you try to create it? Is there any errors in the logs?

Please describe exactly what you are doing and any errors you see.