Let me know if you have questions ;)

On Mar 25, 2017 8:37 PM, "Darcy Christ" <[email protected]> wrote:

> Thank you, Vincent. I’ve been meaning to start working with Docker. This
> sounds like a good opportunity.
>
>
> On Mar 25, 2017, at 4:50 AM, Vincent Meijer <[email protected]>
> wrote:
>
> Hey Darcy,
>
> I think Adam might be able to tell you more about why running one
> Elasticsearch server for two Arches instances is not a good idea (even
> though it seems inefficient).
>
> Here is a thought you may or may not find interesting:
> If you want full standardization / repeatable ES installs, I suggest you
> look into Docker (https://www.docker.com/).
>
> With Docker you could run any number of Elasticsearch instances in
> isolation of each other, without having to install them on your server
> manually.
> The official Elasticsearch Docker image can be found here:
> https://hub.docker.com/_/elasticsearch/ (ignore the deprecation message
> for now).
>
> After installing Docker on your server, you create a docker-compose.yml
> file that looks like this:
> version: '2'
> services:
>     elasticsearch:
>       container_name: elasticsearch
>       image: elasticsearch:1.5.2
>       restart: unless-stopped
>       volumes:
>         - elasticsearch-data:/var/lib/elasticsearch/data
>         - elasticsearch-log:/var/log/elasticsearch
>       ports:
>         - "9200:9200"
>
> volumes:
>     elasticsearch-data:
>     elasticsearch-log:
>
>
> Then you can run your ES container like this:
> docker-compose up -d
>
>
> And you will have a clean, isolated Elasticsearch instance running, which
> listens on port 9200.
> Create another docker-compose.yml with a different port for your second
> Elasticsearch instance.
>
>
> Be aware that Docker does add an extra level of complexity to your work,
> but once you know how to use it, it makes life earlier.
>
> Vincent
>
>
> On Friday, 10 March 2017 00:26:26 UTC-5, Darcy Christ wrote:
>>
>> Hi,
>>
>> I'm running into an issue where certain resources are failing until I
>> rebuild the elasticsearch index. I'm not sure what is happening.
>>
>> I'm running two arches installations and I want to be able to use a
>> standard install of elasticsearch so that I can better control its booting
>> and rebooting. I'm not sure I understand why there needs to be two
>> elasticsearches, but in my present setup I am running two on different
>> ports. Is it possible to run just one (or am I misunderstanding how
>> elasticsearch works)?
>>
>> Any advise from people on how to improve the stability of this, so that
>> it doesn't have such problems.
>>
>> Darcy
>>
>
> --
> -- To post, send email to [email protected]. To unsubscribe,
> send email to [email protected]. For more
> information, visit https://groups.google.com/d/forum/archesproject?hl=en
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "Arches Project" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/archesproject/bPQ74wn_IMI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to