Chris; I also saw what you described. I didn't change port on node 2 to 2435 though. I know for sure multicast-port needs to stay the same for both nodes, but I am not sure about <port>. It maybe not needed to be set because of "auto-increment" ???? And exactly the same - it seems like they are talking to each other , but nothing gets replicated. What strange is that I tried replication in much earlier versions and it worked. Maybe I am doing something wrong and I would appreciate if someone would send detail tutorial how to make it work. In some tutorial pages it says that database MUST to be copied from one node to another prior replication. In other places someone was showing that when 2 nodes been set up for replication creating database on one node created it in another node. It doesn't work for me. Luca? Artem? Andrey? - need help!!!
-Galina On Thursday, July 3, 2014 2:30:51 PM UTC-7, Chris Wilper wrote: > > Another data point: > > I just tried configuring replication with two nodes on the same host with > a fresh install of 1.7.4 on Windows and OSX, and I was also not successful. > But I saw different problems than you did. > > Steps I followed: > 1) Unpack the official distribution in two separate directories on the > same host, one for node1 and one for node2 > 2) Start node1 immediately by going into bin and running the dserver > script > 3) Modify node2's config/hazelcast.xml file, changing the port element's > value from 2434 to 2435 > 4) Start node2 > > After this, from the console output I could see that both nodes recognized > that they were part of the cluster and could see the other one. > > But then I ran console.sh: > > orientdb> connect remote:localhost/GratefulDeadConcerts admin admin > > On Windows: > ------------------- > > It successfully connected, then showed me the DISTRIBUTED CONFIGURATION, > which looked correct. Then I ran a simple query (SELECT COUNT(*) FROM V) > successfully. Next, I tried stopping node2 to simulate node failure. > Queries still worked fine. Then I restarted node2, and queries still worked > as expected. Next, I tried stopping node1 and suddenly queries from the > console failed with messages about not being able to connect. Then I exited > and restarted the console. Same problem. Finally, I decided to stop the > other node, restart both nodes, and restart the console. Immediately upon > attempting to connect, I got the following: > > Connecting to database [remote:localhost/GratefulDeadConcerts] with user > 'admin'... > Error: > com.orientechnologies.orient.core.exception.OConfigurationException: > Database 'GratefulDeadConcerts' is not configured on server > (home=C:\Users\user > \Downloads\cluster\node1/databases/) > > Next I looked in the databases\GratefulDeadConcerts\ directory and saw > there was a single file in there, distributed-config.json, but no data > files. For either node. Uh oh... > > On OS X: > -------------- > > It successfully connected, then said: > DISTRIBUTED CONFIGURATION: none (OrientDB is running in standalone mode) > > ...even though the nodes seem to think they're running in distributed mode. > > -- > > Can anyone else reproduce these behaviors with a fresh 1.7.4 install? > > Thanks, > Chris > > > > On Thu, Jul 3, 2014 at 2:05 PM, galina manashirova <[email protected] > <javascript:>> wrote: > >> Can anybody please help me with this or at least come up with a better >> tutorial in regards of replication. >> >> -Galina >> >> >> >> >> On Wednesday, July 2, 2014 12:44:22 PM UTC-7, galina manashirova wrote: >>> >>> Started from scratch: >>> 1. Downloaded version 1.7.4 >>> 2. Started server node1 in distributed mode (dserver) >>> 3. Copied node1 directory as node2 >>> 4. changed nodeName in orientdb-dserver-config.xml on both nodes giving >>> different names. >>> 5. Started node2 >>> Both nodes see each other. I see in the console for one node: >>> >>> >>> >>> *Members [2] { Member [10.32.10.72]:2434 this Member >>> [10.32.10.72]:2435 }* >>> >>> And on the console of another node: >>> >>> >>> >>> *Members [2] { Member [10.32.10.72]:2434 Member >>> [10.32.10.72]:2435 this }* >>> >>> they are definitely talk to each other. Except one of the nodes gave me >>> an error: >>> >>> 2014-07-02 12:12:56:234 WARN [node2]->[[node1]] requesting deploy of >>> database 'GratefulDeadConcerts' on local server... [OHazelcastPlugin] >>> 2014-07-02 12:32:56:266 WARN [node2] timeout (1200001ms) on waiting for >>> synchronous responses from nodes=[node1] responsesSoFar=[] request=id=0 >>> from=n >>> ode2 task=deploy_db [OHazelcastDistributedDatabase] >>> *Exception in thread "main" >>> com.orientechnologies.orient.server.distributed.ODistributedException: E >>> rror on sending distributed request against database 'GratefulDeadConcerts' >>> to nodes [node1]* >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastDistributedDatabase.send2Nodes(OHazelcastDistributedDatabase. >>> java:194) >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastPlugin.sendRequest(OHazelcastPlugin.java:364) >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastPlugin.installDatabase(OHazelcastPlugin.java:813) >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastPlugin.installNewDatabases(OHazelcastPlugin.java:767) >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastPlugin.startup(OHazelcastPlugin.java:191) >>> at com.orientechnologies.orient.server.OServer. >>> registerPlugins(OServer.java:720) >>> at com.orientechnologies.orient.server.OServer.activate( >>> OServer.java:241) >>> at com.orientechnologies.orient.server.OServerMain.main( >>> OServerMain.java:32) >>> Caused by: >>> com.orientechnologies.orient.server.distributed.ODistributedException: >>> No response received from any of nodes [node1] for request id=0 from >>> =node2 task=deploy_db >>> at com.orientechnologies.orient.server.distributed. >>> ODistributedResponseManager.getFinalResponse( >>> ODistributedResponseManager.java:395) >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastDistributedDatabase.waitForResponse( >>> OHazelcastDistributedDatabase.java:422) >>> at com.orientechnologies.orient.server.hazelcast. >>> OHazelcastDistributedDatabase.send2Nodes(OHazelcastDistributedDatabase. >>> java:191) >>> ... 7 more >>> >>> >>> Even though right above that I see a log message saying that >>> GratefulDatabase distributed configuration sees 2 nodes: >>> >>> 2014-07-02 12:12:56:216 INFO updated distributed configuration for >>> database: GratefulDeadConcerts: >>> ---------- >>> { >>> "version":2, >>> "autoDeploy":true, >>> "hotAlignment":false, >>> "readQuorum":1, >>> "writeQuorum":2, >>> "failureAvailableNodesLessQuorum":false, >>> "readYourWrites":true,"clusters":{ >>> "internal":null, >>> "index":null, >>> "*":{ >>> "servers":["<NEW_NODE>","node1","node2"] >>> } >>> } >>> } >>> When I try to add or remove something from one node on that database >>> nothing happens to another one. >>> Nothing gets replicated on database level. >>> Can someone please tell me what I am doing wrong? >>> I am not trying anything fancy with replication. This is just a basic >>> replication task. >>> I tried replication in some earlier versions (don't remember now which >>> one ) and it worked. Now I can't make it work. >>> We are trying to implement OrientDb for the one of our company product >>> and if replication is not going to work we would have to look for something >>> else. >>> Please let me know if I am doing something wrong. >>> >>> Thank you. >>> -galina >>> >>> >> -- >> >> --- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- 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.
