Getting error while mapping

Elastic Stack Elasticsearch
1 
PUT /product/default/_mapping
{
  "properties": {
    "created":{
      "type": "date",
      "format": "yyyy/MM/dd HH:mm:ss||yyyy/MM/dd"
    }
  }
}

response is like
{ "error": { "root_cause": [ { "type": "cluster_block_exception", "reason": "blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];" } ], "type": "cluster_block_exception", "reason": "blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];" }, "status": 403 }

health status
epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent 1521811101 18:48:21 _dev yellow 1 1 6 6 0 0 5 0 - 54.5%

node status
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name 127.0.0.1 30 96 12 0.33 0.73 0.61 mdi * pt1Yzqk

stuck for days can anyone please help me out

Screenshot%20from%202018-03-20%2002-44-21
Screenshot from 2018-03-20 02-44-21.png1366×768 290 KB

2

Is your file system by any chance close to full?

3

means..??

4

I recall seeing this type of error if the file system where Elasticsearch stores data goes above 85% or 90% full.

5

yeah it is above 85%

6

is there any way to get rid of this error

7

You can add more storage, expand the cluster, delete some data or simply override the default watermark settings in your config. While indexing Elasticsearch need extra disk space for merging, so try to not be overly aggressive if you go with the last option as this could cause severe problems down the line.

You can also try to make sure your data is compressed as well as possible by making sure you mappings are optimized and that you do not have a loti of very small shards.

8

@Christian_Dahlqvist what if the error persist while overriding the default Settings for the disks

9

I do not know. That is the main reason I have seen behind that error. Maybe someone else have seen it under other circumstances?

10

it fixes my error as there is typo error

Thanks Sir

11

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.