# Getting error while mapping **URL:** \ **Category:** Elasticsearch\ **Created:** [March 23, 2018, 1:21pm UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369 "2018-03-23T13:21:12Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![palash7563](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palash7563/32/29180_2.png) [@palash7563](https://discuss.elastic.co/u/palash7563)\ **Post date:** [March 23, 2018, 1:21pm UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/1 "2018-03-23T13:21:13Z")
``` 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](https://us1.discourse-cdn.com/elastic/original/3X/f/d/fdc51dc1082490f757815abee7e6dffcf544e54f.png) ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 24, 2018, 8:15am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/2 "2018-03-24T08:15:10Z")
Is your file system by any chance close to full? ---
**Author:** ![palash7563](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palash7563/32/29180_2.png) [@palash7563](https://discuss.elastic.co/u/palash7563)\ **Post date:** [March 24, 2018, 10:49am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/3 "2018-03-24T10:49:49Z")
means..?? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 24, 2018, 10:52am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/4 "2018-03-24T10:52:22Z")
I recall seeing this type of error if the file system where Elasticsearch stores data goes above 85% or 90% full. ---
**Author:** ![palash7563](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palash7563/32/29180_2.png) [@palash7563](https://discuss.elastic.co/u/palash7563)\ **Post date:** [March 24, 2018, 10:55am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/5 "2018-03-24T10:55:23Z")
yeah it is above 85% ---
**Author:** ![palash7563](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palash7563/32/29180_2.png) [@palash7563](https://discuss.elastic.co/u/palash7563)\ **Post date:** [March 24, 2018, 10:57am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/6 "2018-03-24T10:57:31Z")
is there any way to get rid of this error ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 24, 2018, 11:02am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/7 "2018-03-24T11:02:15Z")
You can add more storage, expand the cluster, delete some data or simply [override the default watermark settings in your config](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html). 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](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/tune-for-disk-usage.html) and that you do not have a loti of very small shards. ---
**Author:** ![palash7563](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palash7563/32/29180_2.png) [@palash7563](https://discuss.elastic.co/u/palash7563)\ **Post date:** [March 24, 2018, 11:40am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/8 "2018-03-24T11:40:03Z")
@Christian_Dahlqvist what if the error persist while overriding the default [Settings](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/disk-allocator.html) for the disks ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [March 24, 2018, 11:49am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/9 "2018-03-24T11:49:18Z")
I do not know. That is the main reason I have seen behind that error. Maybe someone else have seen it under other circumstances? ---
**Author:** ![palash7563](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palash7563/32/29180_2.png) [@palash7563](https://discuss.elastic.co/u/palash7563)\ **Post date:** [March 24, 2018, 11:55am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/10 "2018-03-24T11:55:19Z")
it fixes my error as there is typo error Thanks Sir ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 21, 2018, 11:56am UTC](https://discuss.elastic.co/t/getting-error-while-mapping/125369/11 "2018-04-21T11:56:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.