# Indices deleted and cluster in read only mode \[ES 2.3.4 on AWS\] **URL:** \ **Category:** Elasticsearch\ **Created:** [August 9, 2016, 3:08pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608 "2016-08-09T15:08:34Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Claudio\_Comandini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/claudio_comandini/32/11281_2.png) [@Claudio\_Comandini](https://discuss.elastic.co/u/Claudio_Comandini)\ **Post date:** [August 9, 2016, 3:08pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/1 "2016-08-09T15:08:34Z")
Something happened during the night to my ES cluster (version 2.3.4 on AWS), I have no idea what happened but all the indices and data were deleted and the cluster entered a "read only" mode. What happened and why? I've lost all data and my cluster entered a read-only mode. Another guy had my same issue: ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 9, 2016, 9:22pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/2 "2016-08-09T21:22:25Z")
Are you talking about [https://aws.amazon.com/elasticsearch-service/](https://aws.amazon.com/elasticsearch-service/), or [https://www.elastic.co/cloud](https://www.elastic.co/cloud)? ---
**Author:** ![Claudio\_Comandini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/claudio_comandini/32/11281_2.png) [@Claudio\_Comandini](https://discuss.elastic.co/u/Claudio_Comandini)\ **Post date:** [August 9, 2016, 9:47pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/3 "2016-08-09T21:47:03Z")
neither, we launched 2 AWS instaces and setup elasticsearch by hand ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 9, 2016, 10:25pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/4 "2016-08-09T22:25:49Z")
Check your logs, a cluster shouldn't just switch to red only magically. ---
**Author:** ![Claudio\_Comandini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/claudio_comandini/32/11281_2.png) [@Claudio\_Comandini](https://discuss.elastic.co/u/Claudio_Comandini)\ **Post date:** [August 9, 2016, 10:46pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/5 "2016-08-09T22:46:38Z")
can you give me an example of log entries to be searched? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 9, 2016, 11:15pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/6 "2016-08-09T23:15:48Z")
Look for `cluster.blocks.read_only` maybe? Otherwise, put some of it up on gist/pastebin/etc and link here and we can take a look. ---
**Author:** ![Claudio\_Comandini](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/claudio_comandini/32/11281_2.png) [@Claudio\_Comandini](https://discuss.elastic.co/u/Claudio_Comandini)\ **Post date:** [August 10, 2016, 3:22pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/7 "2016-08-10T15:22:14Z")
no entries in logs for that type of search (cluster.blocks.read\_only / cluster.blocks / read\_only ). i found sometimes entries like this: [2016-08-10 13:03:24,148][WARN][transport.netty] [assist-production-node-1] exception caught on transport layer [[id: 0x92f09b88, /87.20.245.104:55911 =\> /172.31.39.183:9300]], closing connection java.io.IOException: Connessione scaduta at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) at sun.nio.ch.IOUtil.read(IOUtil.java:192) at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:64) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:28pm UTC](https://discuss.elastic.co/t/indices-deleted-and-cluster-in-read-only-mode-es-2-3-4-on-aws/57608/8 "2017-07-05T22:28:44Z")