Moreover, when I do insert a record in a database on 'orient-a', I get a
message like this in the logs:
> 2014-05-27 11:26:00:560 WARN [orient-a] overridden quorum (2) for request
> id=1 from=orient-a task=record_create(#9:-1 v.0) because available nodes
> (1) are less than quorum, received responses: {orient-a=#9:0 v.1,
> orient-b=waiting-for-response} ODistributedResponseManager]
What also strikes me as odd is that I am able to connect with both
instances via studio. However, connecting with the instances via the
console (e.g. with connect remote:localhost:2434 username password
or connect remote:localhost:2435 username password) results in the console
displaying:
> Connecting to remote Server instance [remote:localhost:2435] with user
> 'username'...
Note that I witness this behaviour for both instances.
Again, any help would be much appreciated ... I'll probably slap myself in
the face because of my stupidity ... but I'm not able to find out where I'm
going wrong.
Cheers,
Frens
On Tuesday, May 27, 2014 11:13:27 AM UTC+2, Frens Jan Rumph wrote:
>
> Dear all,
>
> I am trying to move to a distributed setup of an OrientDB graph database.
> I'm tinkering around in a local setup:
>
> - version 1.7 from
>
> https://oss.sonatype.org/content/repositories/releases/com/orientechnologies/orientdb-community/1.7/orientdb-community-1.7-distribution.zip
> - two copies of the distribution in folders 'a' and 'b'
> - named the nodes 'orient-a' and 'orient-b' in the
> com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin section of
> orientdb-dserver-config.xml
> - configured nodes a and b to find each other through the static ip
> address option in hazelcast.xml (each on their own port 2434 and 2435)
> - mentioned 'orient-a' and 'orient-b'
> in default-distributed-db-config.json
>
> The two instances connect, the node which starts second (I always start
> 'orient-b' after 'orient-a') drops the GratefulDeadConcerts database in
> order to replicate from the first node ('orient-a' in this case). However
> after this I see the following message on the second instance ('orient-b')
>
>> 2014-05-27 10:57:28:473 WARN [orient-b]->[[orient-a]] requesting deploy
>> of database 'GratefulDeadConcerts' on local server... [OHazelcastPlugin]
>
>
> On 'orient-a' (the instances started first) I see the messages:
>
>> 2014-05-27 10:57:26:415 INFO [orient-a]<-[orient-b] added node
>> configuration id=Member [localhost]:2435 name=orient-b, now 2 nodes are
>> configured [OHazelcastPlugin][orient-a]<-[orient-b] error on reading
>> distributed request: deploy_db Distributed storage was not installed for
>> database 'GratefulDeadConcerts'
>> ->
>> com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.executeOnLocalNode(OHazelcastPlugin.java:644)
>> ->
>> com.orientechnologies.orient.server.hazelcast.OHazelcastDistributedDatabase.onMessage(OHazelcastDistributedDataba
>> se.java:477)
>> ->
>> com.orientechnologies.orient.server.hazelcast.OHazelcastDistributedDatabase$1.run(OHazelcastDistributedDatabase.j
>> ava:243)
>> -> java.lang.Thread.run(Thread.java:744)
>
>
> Anyone have an idea of what I might be doing wrong?
>
> Any help would be much appreciated,
> Frens
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" 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.