Chef Ideas

We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.

We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.

Thanks for collaborating with us!

In an A2 with embedded single node elasticsearch make sure to start out with green status

In order to present a green status when there is a single node and no chance for replicas, the following config should be set on all newly created, single node embedded Elasticsearch systems


1. Set the following in elasticsearch.yml before any indices are created, during initial installation of the system. This will ensure the system stays in green status with only a single node.

number_of_replicas: 0


For completeness. Here is how we change all existing indices in a system that has already created indices and become yellow through lack of available nodes on which to create replica shards. Elasticsearch' default stance is that the first node is the initial cluster node and that two more nodes will be added soon after the cluster start. In A2 systems with a single embedded ES node, this is not true, and leads to a permanent yellow status of the single node.


curl -X PUT -H "Content-Type: application/json" -H "Cache-Control: no-cache" -d '{
"index" : {
}' 'http://localhost:10144/_settings'


  • Guest
  • Jan 27 2020
  • Already Possible
  • Attach files
  • Guest commented
    16 Aug, 2022 05:12pm

    It's not already possible that a single node system is configured properly from the start in any Automate system.

    A single node Automate system install should have a green OpenSearch when all of its shards are open and started.

    Is that the case today?

  • Ankur Mundhra commented
    1 Feb, 2021 05:19am

    The PR mentioned in the above comment is merged. Hence, am assuming that it is already possible. Am marking it as already possible.

  • Guest commented
    18 Feb, 2020 04:58pm

    Cool, looks like that will be in the wild soon

    Would still need to do these activities for a system with existing indices.

  • Guest commented
    18 Feb, 2020 04:56pm

    Adding auto_expand_replicas set to 0 might be prudent too, to make sure the system doesn't try to expand and create replicas it cannot use.

     "index" : {
      "auto_expand_replicas": false