# Elasticsearch 8.1.0 Cluster Issue **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security\ **Created:** [April 13, 2022, 7:56am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300 "2022-04-13T07:56:34Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Mohsin\_Ashraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohsin_ashraf/32/104333_2.png) [@Mohsin\_Ashraf](https://discuss.elastic.co/u/Mohsin_Ashraf)\ **Post date:** [April 13, 2022, 7:56am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/1 "2022-04-13T07:56:34Z")
Hi. I trying to build an Elasticsearch cluster. But after generating the enrollment token and making some changes to the configuration file and assigning the role for different nodes it gives me the following error when I want to change the password of elastic user and try to access Elasticsearch from URL it does not accept the credentials. here from error: ```auto [2022-04-13T12:41:55,419][INFO][o.e.x.s.s.SecurityIndexManager] [master-siemitry] security index does not exist, creating [.security-7] with alias [.security] [2022-04-13T12:41:55,546][INFO][o.e.c.m.MetadataCreateIndexService] [master-siemitry] [.security-7] creating index, cause [api], templates [], shards [1]/[0] [2022-04-13T12:41:55,569][INFO][o.e.c.r.a.AllocationService] [master-siemitry] current.health="RED" message="Cluster health status changed from [YELLOW] to [RED] (reason: [index [.security-7] created])." previous.health="YELLOW" reason="index [.security-7] created" [2022-04-13T12:42:30,532][INFO][o.e.x.s.a.f.FileUserPasswdStore] [master-siemitry] users file [/etc/elasticsearch/users] changed. updating users... ``` ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [April 13, 2022, 2:50pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/2 "2022-04-13T14:50:09Z")
Hi there, you need to give us a bit more information than what you have added above, otherwise it's highly improbable someone will be able to assist you. Can you explain in more details the steps you have executed so far ? ---
**Author:** ![Mohsin\_Ashraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohsin_ashraf/32/104333_2.png) [@Mohsin\_Ashraf](https://discuss.elastic.co/u/Mohsin_Ashraf)\ **Post date:** [April 14, 2022, 7:44am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/3 "2022-04-14T07:44:39Z")
I install Elasticsearch on 3 nodes after that from one node 1 generate an enrollment token and build a cluster of Elasticsearch and also kibana on one node cluster is running normal but when I want to specify the role of nodes like 1 master and other two data it gives me an error. ```auto [2022-04-14T12:38:22,702][INFO][o.e.n.Node] [m1] node name [m1], node ID [D_BnbObUQyWIxi1YFhnhiQ], cluster name [cluster-1], roles [data_cold, data, remote_cluster_client, master, data_warm, data_content, transform, data_hot, ml, data_frozen, ingest] [2022-04-14T12:38:33,484][ERROR][o.e.b.Bootstrap] [m1] Exception java.lang.IllegalArgumentException: unknown setting [node.master] please check that any required plugins are installed, or check the breaking changes documentation for removed settings at org.elasticsearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:563) ~[elasticsearch-8.1.0.jar:8.1.0] ``` and this. ```auto [2022-04-14T12:38:33,496][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [m1] uncaught exception in thread [main] org.elasticsearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [node.master] please check that any required plugins are installed, or check the breaking changes documentation for removed settings ``` ---
**Author:** ![Mohsin\_Ashraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohsin_ashraf/32/104333_2.png) [@Mohsin\_Ashraf](https://discuss.elastic.co/u/Mohsin_Ashraf)\ **Post date:** [April 14, 2022, 8:39am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/4 "2022-04-14T08:39:23Z")
and these are my yml file configuration: ```auto # ======================== Elasticsearch Configuration = # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # cluster.name: cluster-1 # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # node.name: m1 node.master: true node.data: false node.ingest: false # # Add custom attributes to the node: # #node.attr.rack: r1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # path.data: /var/lib/elasticsearch # # Path to log files: # path.logs: /var/log/elasticsearch # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # #bootstrap.memory_lock: true # # Make sure that the heap size is set to about half the memory available # on the system and that the owner of the process is allowed to use this # limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # By default Elasticsearch is only accessible on localhost. Set a different # address here to expose this node on the network: # network.host: 0.0.0.0 # # By default Elasticsearch listens for HTTP traffic on the first free port it # finds starting at 9200. Set a specific HTTP port here: # #http.port: 9200 # # For more information, consult the network module documentation. # # --------------------------------- Discovery ---------------------------------- # # Pass an initial list of hosts to perform discovery when this node is started: # The default list of hosts is ["127.0.0.1", "[::1]"] # discovery.seed_hosts: ["172.16.3.152", "172.16.3.149","172.16.3.151"] # # Bootstrap the cluster using an initial set of master-eligible nodes: # cluster.initial_master_nodes: ["172.16.3.152"] # # For more information, consult the discovery and cluster formation module documentation. # # ---------------------------------- Various ----------------------------------- # # Allow wildcard deletion of indices: # #action.destructive_requires_name: false #----------------------- BEGIN SECURITY AUTO CONFIGURATION ----------------------- # # The following settings, TLS certificates, and keys have been automatically # generated to configure Elasticsearch security features on 13-04-2022 08:18:19 # # -------------------------------------------------------------------------------- # Enable security features xpack.security.enabled: true xpack.security.enrollment.enabled: true # Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents xpack.security.http.ssl: enabled: true keystore.path: certs/http.p12 # Enable encryption and mutual authentication between cluster nodes xpack.security.transport.ssl: enabled: true verification_mode: certificate keystore.path: certs/transport.p12 truststore.path: certs/transport.p12 # Create a new cluster with the current node only # Additional nodes can still join the cluster later #cluster.initial_master_nodes: ["mohsin-virtual-machine"] # Allow HTTP API connections from localhost and local networks # Connections are encrypted and require user authentication http.host: [_local_, _site_] # Allow other nodes to join the cluster from localhost and local networks # Connections are encrypted and mutually authenticated transport.host: [_local_, _site_] #----------------------- END SECURITY AUTO CONFIGURATION ------------------------- ``` ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [April 14, 2022, 10:13am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/5 "2022-04-14T10:13:38Z")
The error is self explanatory, you are using settings that do not exist. See [Node | Elasticsearch Guide [8.1] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html) ---
**Author:** ![Mohsin\_Ashraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohsin_ashraf/32/104333_2.png) [@Mohsin\_Ashraf](https://discuss.elastic.co/u/Mohsin_Ashraf)\ **Post date:** [April 14, 2022, 3:41pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/6 "2022-04-14T15:41:32Z")
I tried but still, the error is not solved. ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [April 15, 2022, 5:32pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/7 "2022-04-15T17:32:14Z")
You have to tell us _what_ you tried and _what_ error persisted ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 15, 2022, 5:39pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/8 "2022-04-15T17:39:20Z")
See Here > **[Node | Elasticsearch Guide \[8.1\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html)** This ```auto node.master: true node.data: false node.ingest: false ``` is incorrect syntax please look at the docs You need to use `node.roles` setting > **[Node | Elasticsearch Guide \[8.1\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#node-roles)** Master only looks like this per the docs `node.roles: [master]` ---
**Author:** ![Mohsin\_Ashraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohsin_ashraf/32/104333_2.png) [@Mohsin\_Ashraf](https://discuss.elastic.co/u/Mohsin_Ashraf)\ **Post date:** [April 18, 2022, 5:45am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/9 "2022-04-18T05:45:32Z")
yes, I sign node.roles: [master] after that it's said to me that I need to run the Elasticsearch-node repurpose command but when I run this command it affects my security indices. I enter my password for elastic it did not accept. ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/2/22a4a346d8c99df8fe8020317a1d6781cb092321.png) ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 18, 2022, 6:10am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/10 "2022-04-18T06:10:40Z")
That's because a master has no data on it. But going back to what you're trying to accomplish why are you trying to create one master in two data nodes that's actually less resilient than just three nodes that are both master and data roles. If you lose the single master you lose your whole cluster. But if have three nodes that are both data and master nodes you could lose a node and the cluster will survive. ---
**Author:** ![Mohsin\_Ashraf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohsin_ashraf/32/104333_2.png) [@Mohsin\_Ashraf](https://discuss.elastic.co/u/Mohsin_Ashraf)\ **Post date:** [April 27, 2022, 8:08am UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/11 "2022-04-27T08:08:21Z")
Okay, I understand thank you for your help. can you help me on this topic? > [@How i can store hot, warm and cold indices on serval disk partition?](https://discuss.elastic.co/t/how-i-can-store-hot-warm-and-cold-indices-on-serval-disk-partition/303356): > > Hi, I want to store hot, warm and cold indices in different disk partitions on the same node. for example, I have different partitions on the same node like 100GB, 250GB and 300GB. So, how can I store indices across different disks? Thanks ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 27, 2022, 2:03pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/12 "2022-04-27T14:03:08Z")
As answered in the thread that is not possible hot warm cold need to be on separate nodes. ---
**Author:** ![INS](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ins/32/92827_2.png) [@INS](https://discuss.elastic.co/u/INS)\ **Post date:** [April 28, 2022, 12:16pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/13 "2022-04-28T12:16:08Z")
> [@How i can store hot, warm and cold indices on serval disk partition?](https://discuss.elastic.co/t/how-i-can-store-hot-warm-and-cold-indices-on-serval-disk-partition/303356/1): > > want to store hot, warm and cold indices in different disk partitions on the same node. for example I ha different partitions on the same node like 100GB, 250GB and 300GB. So, how can I store indices across different disks? Thanks You can do such things only in host terms. So particular node will be involved in particular node.role. But please remember if You will be provisioned over docker service/yml coordinator node has an issue with definition. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 26, 2022, 12:16pm UTC](https://discuss.elastic.co/t/elasticsearch-8-1-0-cluster-issue/302300/14 "2022-05-26T12:16:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.