Indexing is not working (super noob question)

Elastic Stack Elasticsearch
1

I recently inherited a search system that runs on ES. I'm able to spin
off nodes on EC2 with an S3 storage. I simply then attempt to index
some data in there, the world famous twitter example amongst other
things. As soon as I do this I have been getting the following error

{"error":"ClusterBlockException[blocked by: [1/not recovered from
gateway];]"}

I been checking cluster health and it seems to be stuck on red which
makes no sense to me since there is no data in there. This has been
the case for .14.3 and 14.4. The info I found about this error is
pretty scarce and I'm not sure which direction to take to begin to try
and solve it.

Any help is much appreciated

Thanks

2

Are you using the s3 gateway? If so, there is a bug where if you did not create any index, shutdown the cluster, and start it back up, it will not exit the "not recovered from gateway" cluster block. Once you create even a single index (on a clean data, clear it form s3 as well), then it will be able to recover.
On Friday, February 11, 2011 at 2:55 AM, invaderZYM wrote:

I recently inherited a search system that runs on ES. I'm able to spin
off nodes on EC2 with an S3 storage. I simply then attempt to index
some data in there, the world famous twitter example amongst other
things. As soon as I do this I have been getting the following error

{"error":"ClusterBlockException[blocked by: [1/not recovered from
gateway];]"}

I been checking cluster health and it seems to be stuck on red which
makes no sense to me since there is no data in there. This has been
the case for .14.3 and 14.4. The info I found about this error is
pretty scarce and I'm not sure which direction to take to begin to try
and solve it.

Any help is much appreciated

Thanks

3

That was the ticket :slight_smile:

Thanks Shay

On Feb 10, 4:57 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Are you using the s3 gateway? If so, there is a bug where if you did not create any index, shutdown the cluster, and start it back up, it will not exit the "not recovered from gateway" cluster block. Once you create even a single index (on a clean data, clear it form s3 as well), then it will be able to recover.

On Friday, February 11, 2011 at 2:55 AM, invaderZYM wrote:

I recently inherited a search system that runs on ES. I'm able to spin
off nodes on EC2 with an S3 storage. I simply then attempt to index
some data in there, the world famous twitter example amongst other
things. As soon as I do this I have been getting the following error

{"error":"ClusterBlockException[blocked by: [1/not recovered from
gateway];]"}

I been checking cluster health and it seems to be stuck on red which
makes no sense to me since there is no data in there. This has been
the case for .14.3 and 14.4. The info I found about this error is
pretty scarce and I'm not sure which direction to take to begin to try
and solve it.

Any help is much appreciated

Thanks