# Elasticsearch on AWS + raspberry pi **URL:** \ **Category:** Elasticsearch\ **Created:** [December 3, 2020, 10:16am UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485 "2020-12-03T10:16:49Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Ettore\_Ciarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ettore_ciarcia/32/80160_2.png) [@Ettore\_Ciarcia](https://discuss.elastic.co/u/Ettore_Ciarcia)\ **Post date:** [December 3, 2020, 10:16am UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/1 "2020-12-03T10:16:49Z")
Hello everyone. I intend to send the weather data collected by a raspberry pie on ec2 instances hosting elasticsearch to view the temperature graphs on kibana. My idea is to make a comparison between the internal temperature recorded periodically by the raspberry and the external one recorded via API to the weather site and draw the relative graphs. I currently have a master node to which I would like to add two data nodes. I have followed several guides but every time I restart the elasticsearch service with a different configuration than the initial one, elasticsearch crashes. Do you have any guides to recommend? Which data shippers do you recommend to install on the raspberry pi? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 4, 2020, 1:54am UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/2 "2020-12-04T01:54:58Z")
Welcome to our community! πŸ˜ƒ What version are you running? > [@Ettore\_Ciarcia](#): > > Which data shippers do you recommend to install on the raspberry pi? Definitely Filebeat if you are using ARM64. ---
**Author:** ![Ettore\_Ciarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ettore_ciarcia/32/80160_2.png) [@Ettore\_Ciarcia](https://discuss.elastic.co/u/Ettore_Ciarcia)\ **Post date:** [December 5, 2020, 9:10am UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/3 "2020-12-05T09:10:04Z")
Thank you! I'm running Elastcisearch 7.10.0 ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 5, 2020, 9:22am UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/4 "2020-12-05T09:22:46Z")
> [@Ettore\_Ciarcia](#): > > every time I restart the elasticsearch service with a different configuration than the initial one, elasticsearch crashes. "Elasticsearch crashes" could mean any of a number of different things, so it's hard to help you get past this. Can you be more precise? In particular, what does it log before "crashing"? ---
**Author:** ![Ettore\_Ciarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ettore_ciarcia/32/80160_2.png) [@Ettore\_Ciarcia](https://discuss.elastic.co/u/Ettore_Ciarcia)\ **Post date:** [December 6, 2020, 2:51pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/5 "2020-12-06T14:51:51Z")
Sorry, I did not properly configure the elasticsearch.yml file Now i am able to run elasticsearch service but i can't add a node in my cluster. Below the configurations of the master node and the slave node, I hope someone can help me: Both nodes are running on AWS, in the same VPC. They can ping each other and i can use curl [http://indirizzoIPv4:9200](http://indirizzoIPv4:9200) to get information about master node on the slave node. Master node configuration IP:172.31.36.3 cluster.name: my-cluster node.name: master network.host : "172.31.36.3" http.port: 9200 discovery.seed\_hosts: ["172.31.36.3", "172.31.32.226"] cluster.initial\_master\_nodes: ["172.31.36.3"] node.master: true Slave node configuration IP:172.31.32.226 cluster.name: my-cluster node.name: data1 network.host : "172.31.32.226" http.port: 9200 discovery.seed\_hosts: ["172.31.36.3", "172.31.32.226"] cluster.initial\_master\_nodes: ["172.31.36.3"] node.data: true curl -X GET [http://172.31.36.3:9200/\_cluster/health?pretty](http://172.31.36.3:9200/_cluster/health?pretty) and i got { "cluster\_name" : "my-cluster", "status" : "green", "timed\_out" : false, "number\_of\_nodes" : 1, "number\_of\_data\_nodes" : 1, "active\_primary\_shards" : 0, "active\_shards" : 0, "relocating\_shards" : 0, "initializing\_shards" : 0, "unassigned\_shards" : 0, "delayed\_unassigned\_shards" : 0, "number\_of\_pending\_tasks" : 0, "number\_of\_in\_flight\_fetch" : 0, "task\_max\_waiting\_in\_queue\_millis" : 0, "active\_shards\_percent\_as\_number" : 100.0 } ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 6, 2020, 2:55pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/6 "2020-12-06T14:55:23Z")
> [@Ettore\_Ciarcia](#): > > Below the configurations of the master node and the slave node, I hope someone can help me: Please don't call them "slave" nodes, that's not a meaningful word in terms of Elasticsearch and is a bit offensive. What does `GET /` return on each node? I.e. please share the output of both `curl http://172.31.36.3:9200/` and `curl http://172.31.32.226:9200/`. ---
**Author:** ![Ettore\_Ciarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ettore_ciarcia/32/80160_2.png) [@Ettore\_Ciarcia](https://discuss.elastic.co/u/Ettore_Ciarcia)\ **Post date:** [December 6, 2020, 3:00pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/7 "2020-12-06T15:00:10Z")
> [@DavidTurner](#): > > `curl http://172.31.36.3:9200/` Sorry, I won't call them that anymore πŸ™‚ curl [http://172.31.36.3:9200/](http://172.31.36.3:9200/) { "name" : "master", "cluster\_name" : "my-cluster", "cluster\_uuid" : "PvDRqvxVTEyYBjbeJtULog", "version" : { "number" : "7.10.0", "build\_flavor" : "default", "build\_type" : "rpm", "build\_hash" : "51e9d6f22758d0374a0f3f5c6e8f3a7997850f96", "build\_date" : "2020-11-09T21:30:33.964949Z", "build\_snapshot" : false, "lucene\_version" : "8.7.0", "minimum\_wire\_compatibility\_version" : "6.8.0", "minimum\_index\_compatibility\_version" : "6.0.0-beta1" }, "tagline" : "You Know, for Search" } curl [http://172.31.32.226:9200/](http://172.31.32.226:9200/) { "name" : "data1", "cluster\_name" : "my-cluster", "cluster\_uuid" : "pWMAOOpQRY-vdDBTv7eOYA", "version" : { "number" : "7.10.0", "build\_flavor" : "default", "build\_type" : "rpm", "build\_hash" : "51e9d6f22758d0374a0f3f5c6e8f3a7997850f96", "build\_date" : "2020-11-09T21:30:33.964949Z", "build\_snapshot" : false, "lucene\_version" : "8.7.0", "minimum\_wire\_compatibility\_version" : "6.8.0", "minimum\_index\_compatibility\_version" : "6.0.0-beta1" }, "tagline" : "You Know, for Search" } ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 6, 2020, 3:05pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/8 "2020-12-06T15:05:06Z")
> [@Ettore\_Ciarcia](#): > > Sorry, I won't call them that anymore πŸ™‚ Thanks πŸ™‚ > [@Ettore\_Ciarcia](#): > > ```auto > "cluster_uuid" : "PvDRqvxVTEyYBjbeJtULog", > ... > "cluster_uuid" : "pWMAOOpQRY-vdDBTv7eOYA", > > ``` The mismatched cluster UUIDs means you didn't set `cluster.initial_master_nodes` before starting these nodes up for the first time, so you've generated two independent clusters. There's [more details in the manual](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-bootstrap-cluster.html#modules-discovery-bootstrap-cluster-joining) but the solution is to wipe both these nodes and start again from scratch with `cluster.initial_master_nodes` set. Also note that `cluster.initial_master_nodes` should be the `node.name` of the master, not its IP address. ---
**Author:** ![Ettore\_Ciarcia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ettore_ciarcia/32/80160_2.png) [@Ettore\_Ciarcia](https://discuss.elastic.co/u/Ettore_Ciarcia)\ **Post date:** [December 6, 2020, 4:13pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/9 "2020-12-06T16:13:31Z")
I really thank you, without your help I would never have found the mistake. I did as you told me and created my first cluster on Elasticsearch! ![Cluster](https://us1.discourse-cdn.com/elastic/original/3X/0/1/01d2470102362d2506313846f661e1bbb50f7878.png) ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [December 6, 2020, 5:26pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/10 "2020-12-06T17:26:24Z")
Congratulations! You are very welcome to experiment with all sorts of different cluster setups, but you might like to read the [advice in the reference manual regarding two-node clusters](https://www.elastic.co/guide/en/elasticsearch/reference/current/high-availability-cluster-small-clusters.html#high-availability-cluster-design-two-nodes). In particular: > If you have two nodes, we recommend they both be data nodes. and > Because it’s not resilient to failures, we do not recommend deploying a two-node cluster in production. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 3, 2021, 5:26pm UTC](https://discuss.elastic.co/t/elasticsearch-on-aws-raspberry-pi/257485/11 "2021-01-03T17:26:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.