Hi Adam, To answer your questions: 1. I see the current ES repo is for version 1.5 instead of 1.4 which is > used by arches3. Will this cause problems later? I assume I could > install 1.4 instead of 1.5 if necessary.
Taking a quick look at the ES change logs, it doesn't look like there are any breaking changes that you should be worried about, so 1.5 should be fine. 2. I have not changed any of the default elasticsearch config settings. I > see that the arches3 development installation has its own custom > elasticsearch.yml file. Would it be advisable to change any default > elasticsearch config settings on this installation to match those in the > arches3 elasticsearch.yml file? The default settings that Arches uses are one primary shard for each index with no replicas. It's really set up for testing only. You might want to add at least one replica. It's really up to you. Check this out: http://www.elastic.co/guide/en/elasticsearch/guide/master/capacity-planning.html Cheers, Alexei Director of Web Development - Farallon Geographics, Inc. - 971.227.3173 On Mon, May 11, 2015 at 11:42 PM, Van Daele, Koen < koen.vanda...@rwo.vlaanderen.be> wrote: > Hi Adam, > > not sure about 1. Generally the ES development team gives ample warning > when they make backwards incompatible fixes. > > From what I can see, most of the settings in the elasticsearch.yml file > make sure that ES is running locally and with only one "leg". ES is a very > powerful system, but to use it to the fullest of it's capabilities, you > will need to learn how to configure it a bit. We eg. have several ES nodes > running (on different machines, separated froom the webservers) as a high > availability cluster. That does involve some more configuration work. One > thing to be wary of, with the default ES config (unless that has been > changed by now), the nodes have a tendency to go and look for each other. I > remember when my ES instance started syncing with a colleagues (without us > realising). Easiest way to prevent that is to give your cluster a dedicated > name (cluster.name in the config). > > You might also want to install the elasticsearch-head plugin that Arches > also installs. I don't think any other plugins are needed at this moment. > > Anyway, in my opinion, running ES from within Arches is fine for > development purposes. But for production I'd prefer to separate the two. > > Cheers, > Koen > ________________________________________ > Van: archesproject@googlegroups.com [archesproject@googlegroups.com] > namens Adam Cox [mr.adam...@gmail.com] > Verzonden: maandag 11 mei 2015 18:39 > Aan: archesproject@googlegroups.com > Onderwerp: [Arches] ElasticSearch in Production > > Hello all. I have successfully installed ElasticSearch on Ubuntu outside > of the arches environment so it will run as a service, and it was far > easier than I was expecting... a pleasant surprise that makes me wary. > > To do so I began with a fresh Amazon EC2 instance, and I followed the > normal arches3 installation steps. However, instead of running > > python manage.py packages -o setup_elasticsearch > > (which installs elasticsearch within the app itself) I followed these > steps< > http://www.elastic.co/guide/en/elasticsearch/reference/current/setup-repositories.html> > from the ElasticSearch webpage to install the current APT distribution of > ElasticSearch on Ubuntu. After that installation, I was able to run ES as > a service, and after finishing the arches-hip installation, was able to use > the database and add/search resources (it works!). > > I have two questions: > 1. I see the current ES repo is for version 1.5 instead of 1.4 which is > used by arches3. Will this cause problems later? I assume I could > install 1.4 instead of 1.5 if necessary. > 2. I have not changed any of the default elasticsearch config settings. I > see that the arches3 development installation has its own custom > elasticsearch.yml file. Would it be advisable to change any default > elasticsearch config settings on this installation to match those in the > arches3 elasticsearch.yml file? > > > -- > -- To post, send email to archesproject@googlegroups.com. To unsubscribe, > send email to archesproject+unsubscr...@googlegroups.com. For more > information, visit https://groups.google.com/d/forum/archesproject?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Arches Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to archesproject+unsubscr...@googlegroups.com<mailto: > archesproject+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. > > -- > -- To post, send email to archesproject@googlegroups.com. To unsubscribe, > send email to archesproject+unsubscr...@googlegroups.com. For more > information, visit https://groups.google.com/d/forum/archesproject?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Arches Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to archesproject+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- To post, send email to archesproject@googlegroups.com. To unsubscribe, send email to archesproject+unsubscr...@googlegroups.com. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to archesproject+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
