Why can't I build AWS OpenSearch/ElasticSearch index, which I could do that before?

  • One of the reason when you used to build AWS OS/ES index, and you can't do that now, is that there is a maximum shard default setting in AWS, which is 1000 shards.
  • If you continuously build index, yet you did not remove old indices, there will be an increasing number of shards that occupied OS/ES.
  • Until when a new index is built, and new shard is created that exceed the number of maximum shard, you got an error.
  • Solution: Remove old/existing OS/ES indices.
  • While it works for AWS, if you are using on-premise, it should be applied as well.
Hope it helps someone.

Comments

Popular posts from this blog

TCPDF How to show/display Chinese Character?

How to fix fancy box/Easy Fancybox scroll not work in mobile

Wordpress Load balancing: 2 web servers 1 MySQL without any Cloud services