Automatic master node election. HTH -- David ;-) Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 25 juil. 2014 à 20:07, Anthony Oleary <anthony.ole...@kweekweek.com> a écrit : hi David May I ask, if i want to use opsworks, copy my ec2 image onto opswork , and auto scale, how can i specify a master node or is it automatic? anthony > On Thursday, July 24, 2014 5:36:51 PM UTC+1, David Pilato wrote: > It's a matter of EC2 configuration. Elasticsearch does not really care to > know. > > I'd probably start with local disks if possible. Replication is done by > elasticsearch. So if you have more than one node, your data could be > replicated on another machine. > > -- > David Pilato | Technical Advocate | Elasticsearch.com > @dadoonet | @elasticsearchfr > > >> Le 24 juillet 2014 à 17:23:08, Anthony Oleary (anthony...@kweekweek.com) a >> écrit: >> >> Thanks again David, >> One last question, how would i tell elasticsearch to use the EBS? or is it >> when i create a EC2 to link it to EBS and it works away without telling >> eleasticsearch. >> >> would you recommend EBS in order for the data not to be lost. >> >> >> >>> On Thursday, July 24, 2014 3:48:53 PM UTC+1, David Pilato wrote: >>> Just use local disk or EBS with provisioned IOs. >>> You don't need to store your indices on S3. If you want to do that for >>> backup purpose, have a look at snapshot and restore API. >>> >>> Basically, in elasticsearch.yml file, remove: >>> >>> gateway.type: s3 >>> gateway.s3.bucket: codetest >>> >>> Gateway has been removed since 1.2.0: >>> http://www.elasticsearch.org/blog/elasticsearch-1-2-0-released/ >>> >>> -- >>> David Pilato | Technical Advocate | Elasticsearch.com >>> @dadoonet | @elasticsearchfr >>> >>> >>>> Le 24 juillet 2014 à 16:27:27, Anthony Oleary (anthony...@kweekweek.com) a >>>> écrit: >>>> >>>> thanks David >>>> I got the link about gateways from >>>> http://www.elasticsearch.org/tutorials/elasticsearch-on-ec2/ >>>> >>>> >>>> what would you recommend i use for clustering on EC2 instead of gateways >>>> or how to configure the config.yml ? >>>> >>>> Anthony >>>> >>>> >>>>> On Thursday, July 24, 2014 2:47:32 PM UTC+1, David Pilato wrote: >>>>> Gateways have been removed. You can't use that anymore. >>>>> >>>>> -- >>>>> David Pilato | Technical Advocate | Elasticsearch.com >>>>> @dadoonet | @elasticsearchfr >>>>> >>>>> >>>>>> Le 24 juillet 2014 à 14:47:48, Anthony Oleary (anthony...@kweekweek.com) >>>>>> a écrit: >>>>>> >>>>>> Hello, >>>>>> in EC@,i installed elasticsearch with >>>>>> wget >>>>>> http://download.elasticsearch.org/elasticsearch/elasticsearch/elasticsearch-1.3.0.zip >>>>>> sudo unzip elasticsearch-1.3.0.zip -d /usr/local/elasticsearch >>>>>> cd /usr/local/elasticsearch/elasticsearch-1.3.0 >>>>>> sudo bin/plugin -install elasticsearch/elasticsearch-cloud-aws/2.1.1 >>>>>> >>>>>> config.yml is >>>>>> >>>>>> cluster.name: elasticsearch-demo-js >>>>>> cloud.aws.access_key: xxx.. >>>>>> cloud.aws.secret_key: yyy... >>>>>> cloud.aws.discovery.type: ec2 >>>>>> gateway.type: s3 >>>>>> gateway.s3.bucket: codetest >>>>>> >>>>>> but i get this error as soon as i add the gateway configuration >>>>>> {1.3.0}: Initialization Failed ... >>>>>> >>>>>> NoClassDefFoundError[org/elasticsearch/gateway/blobstore/BlobStoreGatewayModule] >>>>>> >>>>>> ClassNotFoundException[org.elasticsearch.gateway.blobstore.BlobStoreGatewayModule] >>>>>> any ideas ? >>>>>> i then tried: sudo bin/plugin -install >>>>>> elasticsearch/elasticsearch-cloud-aws/2.2.0 but got >>>>>> - NoClassSettingsException[Failed to load class setting [gateway.type] >>>>>> with value [s3]] >>>>>> >>>>>> ClassNotFoundException[org.elasticsearch.gateway.s3.S3GatewayModule] >>>>>> >>>>>> >>>>>> >>>>>> bit lost now!!! >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "elasticsearch" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>>> an email to elasticsearc...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/elasticsearch/c46bf6f1-ac0d-4437-810a-d2900252d52a%40googlegroups.com. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "elasticsearch" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to elasticsearc...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/elasticsearch/be1a74ed-cb2d-4f04-b600-be0014034d38%40googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elasticsearc...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/7647fca6-877c-4822-a1b6-f4c58e4230be%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1b2f1047-c22b-4ec7-8e92-50fa8d40ecaf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/06F09A51-ED0D-4644-B676-71A4AE8C7533%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
