You can use attached hazelcast.xml for docker setup for orientdb cluster if
you do not want to use kubernetes. This SO
(https://stackoverflow.com/questions/34868686/how-to-make-hazelcast-nodes-installed-in-docker-on-different-aws-instances-inter)
helped me to find a solution.
On Thursday,
Hi Stefan,
If you want to use OrientDB in a clustered configuration with Docker, you
could leverage on Kubernates.
For Kubernates we have a working configuration. Rename the attached file as
hazelcast.xml and put in the config directory overwriting the default one.
Then you need this extra jar:
Hi,
I know this thread is long dead, but I am trying to do this exact same
thing. I was able to access the repo
https://github.com/abcum/docker-orientdb.git about a week ago, but it is
now 404-ing. Is that code gone for good, or is there any way I could grab
it from somewhere?
Thanks in
Awesome! I'm happy to see so many options now. Back when I had this
problem, couldn't find much of a solution. Glad that users will now have
multiple options where to start from when using ODB with Docker.
@Tobie thank you for your image. Haven't tried yet, but looks solid.
On Thu, Mar 5, 2015
Here is my set up: orientdb running in a docker container on an AWS server
in Frankfurt, and a similar container on AWS in Sydney. IPSEC tunneling
between them. My docker file looks like this:
FROM dockerfile/java:oracle-java8
MAINTAINER Simon Gemmell
# Update the default application
Hi Luca,
Docker differences
1. Using `centos:7` not `debian`
2. Using `java-1.7.0-openjdk-headless` instead of `java-1.7.0-openjdk`
3. The OrientDB install tar file
(https://abcum-deploy.s3.amazonaws.com/orient/orientdb-community-2.0.4.tar.gz)
is an exact copy of the one available at
Hi Tobie,
How your project compares to
https://github.com/orientechnologies/orientdb-docker ?
Lvc@
On 4 March 2015 at 14:41, Tobie Morgan Hitchcock to...@abcum.com wrote:
Hi Esen,
I've just been through the same problem, but have a solution.
Basically, Hazelcast attaches itself to the
I can successfully telnet to each server from any other server because
incoming requests are allowed. In fact, each server successfully receives a
connection request, however, there seems to be some kind of a validation.
When the host A receives a connection request from host B, host A checks
Hi Esen,
Seems OrientDB servers can't see each other. I suggest you to try if
connections are allowed between hosts with CURL.
Lvc@
On 5 January 2015 at 07:19, Esen Sagynov kadish...@gmail.com wrote:
Using ODB 2.0-SNAPSHOT (Jan 5, 2015).
My nodes in Docker containers on separate physical
Using ODB 2.0-SNAPSHOT (Jan 5, 2015).
My nodes in Docker containers on separate physical machines cannot join to
each other. The establish a connection however eventually they refuse
joining because some conditions aren't met.
The following are logs on Host 2:
2015-01-05 06:07:15:691 INFO
10 matches
Mail list logo
