Best ElasticSearch configuration mode

Years ago I configured a server* with Elasticsearch, however, until today my knowledge to configure, manage, define nodes, is totally 0. I don't have nodes for ingest, digest, etc, as I have no idea what they do.
Even my server until today only has one cluster, and it is always yellow because of the status I see.

What's the best way for me to set up a redundant Elasticsearch server that has few failures?
My GC log is showing errors every minute and my server sometimes goes down for a minute that ends up messing up all the resources, or would the best option be to migrate my server to ElasticStack?

What is the output from the _cluster/stats?pretty&human API?

This is the API return.
The server has 8GB of RAM.

{
  "_nodes" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "cluster_name" : "**************",
  "cluster_uuid" : "**************",
  "timestamp" : 1649122791968,
  "status" : "yellow",
  "indices" : {
    "count" : 6,
    "shards" : {
      "total" : 6,
      "primaries" : 6,
      "replication" : 0.0,
      "index" : {
        "shards" : {
          "min" : 1,
          "max" : 1,
          "avg" : 1.0
        },
        "primaries" : {
          "min" : 1,
          "max" : 1,
          "avg" : 1.0
        },
        "replication" : {
          "min" : 0.0,
          "max" : 0.0,
          "avg" : 0.0
        }
      }
    },
    "docs" : {
      "count" : 232129878,
      "deleted" : 61646427
    },
    "store" : {
      "size" : "71.7gb",
      "size_in_bytes" : 77092837845
    },
    "fielddata" : {
      "memory_size" : "2.5kb",
      "memory_size_in_bytes" : 2632,
      "evictions" : 0
    },
    "query_cache" : {
      "memory_size" : "398.7mb",
      "memory_size_in_bytes" : 418170376,
      "total_count" : 80258860,
      "hit_count" : 29966091,
      "miss_count" : 50292769,
      "cache_size" : 14154,
      "cache_count" : 154741,
      "evictions" : 140587
    },
    "completion" : {
      "size" : "0b",
      "size_in_bytes" : 0
    },
    "segments" : {
      "count" : 107,
      "memory" : "82mb",
      "memory_in_bytes" : 86012113,
      "terms_memory" : "42.5mb",
      "terms_memory_in_bytes" : 44607913,
      "stored_fields_memory" : "29.6mb",
      "stored_fields_memory_in_bytes" : 31076896,
      "term_vectors_memory" : "0b",
      "term_vectors_memory_in_bytes" : 0,
      "norms_memory" : "93.1kb",
      "norms_memory_in_bytes" : 95424,
      "points_memory" : "8.9mb",
      "points_memory_in_bytes" : 9404132,
      "doc_values_memory" : "808.3kb",
      "doc_values_memory_in_bytes" : 827748,
      "index_writer_memory" : "0b",
      "index_writer_memory_in_bytes" : 0,
      "version_map_memory" : "0b",
      "version_map_memory_in_bytes" : 0,
      "fixed_bit_set" : "35mb",
      "fixed_bit_set_memory_in_bytes" : 36714416,
      "max_unsafe_auto_id_timestamp" : -1,
      "file_sizes" : { }
    }
  },
  "nodes" : {
    "count" : {
      "total" : 1,
      "data" : 1,
      "coordinating_only" : 0,
      "master" : 1,
      "ingest" : 1
    },
    "versions" : [
      "6.8.23"
    ],
    "os" : {
      "available_processors" : 4,
      "allocated_processors" : 4,
      "names" : [
        {
          "name" : "Linux",
          "count" : 1
        }
      ],
      "pretty_names" : [
        {
          "pretty_name" : "***********",
          "count" : 1
        }
      ],
      "mem" : {
        "total" : "7.7gb",
        "total_in_bytes" : 8363552768,
        "free" : "179.6mb",
        "free_in_bytes" : 188375040,
        "used" : "7.6gb",
        "used_in_bytes" : 8175177728,
        "free_percent" : 2,
        "used_percent" : 98
      }
    },
    "process" : {
      "cpu" : {
        "percent" : 1
      },
      "open_file_descriptors" : {
        "min" : 339,
        "max" : 339,
        "avg" : 339
      }
    },
    "jvm" : {
      "max_uptime" : "5d",
      "max_uptime_in_millis" : 432088395,
      "versions" : [
        {
          "version" : "1.8.0_201",
          "vm_name" : "Java HotSpot(TM) 64-Bit Server VM",
          "vm_version" : "25.201-b09",
          "vm_vendor" : "Oracle Corporation",
          "count" : 1
        }
      ],
      "mem" : {
        "heap_used" : "2.8gb",
        "heap_used_in_bytes" : 3023483984,
        "heap_max" : "3.9gb",
        "heap_max_in_bytes" : 4260102144
      },
      "threads" : 100
    },
    "fs" : {
      "total" : "154.8gb",
      "total_in_bytes" : 166318571520,
      "free" : "66.2gb",
      "free_in_bytes" : 71139254272,
      "available" : "66.2gb",
      "available_in_bytes" : 71122477056
    },
    "plugins" : [ ],
    "network_types" : {
      "transport_types" : {
        "security4" : 1
      },
      "http_types" : {
        "security4" : 1
      }
    }
  }
}

Normally you'd have 3 nodes for a fault tolerant cluster.

You don't have a tonne of data there to really warrant a larger cluster however. You might find better use of your resources if you upgraded to 8.X, 6.X is a few years old now.

I can't migrate from 6.8 to 8.X as there are so many differences between platforms that it just breaks my application.
Even from 6.8 to 7.X since something that generates a lot of problems, mainly in the scripts part.

Fair enough, just be aware that 6.8 is EOL and no longer supported.

Because of the EOL of 6.8 and the difficulty of maintaining a server of our own, we are considering using an Elasticsearch IaaS, but we don't know if ElasticStack offers this, as we saw a lot of security-oriented features and things that we don't use (eg.: Kibana ), and what we need today is just Elasticsearch and its API to insert and query documents.

The Elasticsearch Service does include nearly everything we offer, however you don't need to use it if you'd just like Elasticsearch for the API.

Our biggest problem today is actually maintaining our Elasticsearch server, so we considered using an IaaS.

Does Elasticsearch have any material on how to create and configure a "perfect" server from scratch?

Perfect is inherently relative, so it's a bit hard to cover everything.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.