can't get GratefulDeadConcerts demo to work distributed

[alexpmorris]

I feel almost silly asking this, since I figure I must be missing something really simple.  I am trying this with the latest 1.7 snapshot, and I've also tried with 1.7-RC2.

I created two cloned subdirs of 1.7 snapshot on windows:

c:\nosql\orientdb1\

c:\nosql\orientdb2\

then, for each instance I run  "  dserver  "

I can access both in the browser, one at port :2480, the other at :2481

I change the name "MONA" (class V, #9:2) to "MONA lisa" on either instance.

While the version increases, and the new data reflects on the same instance, it never gets propagated to the other node.  They basically act like two separate servers.  I try changing the value on both instances several times, and nothing ever gets propagated.

I've included a log from the first instance.  Appreciate any ideas on why this isn't working for me.

Thanks!

---------- [OHazelcastPlugin]

2014-04-23 13:32:25:617 INFO Saving distributed configuration file for database

'GratefulDeadConcerts' to: C:\nosql\orientdb1\databases\GratefulDeadConcerts\distributed-config.json [OHazelcastPlugin]

2014-04-23 13:32:31:117 INFO [192.168.242.1]:2434 [orientdb]

Members [2] {

        Member [192.168.242.1]:2434 this

        Member [192.168.242.1]:2435

}

 [ClusterService]

2014-04-23 13:32:31:117 WARN [node1398272538742] added new node id=Member [192.168.242.1]:2435 name=null [OHazelcastPlugin]

2014-04-23 13:32:31:149 INFO [192.168.242.1]:2434 [orientdb] Re-partitioning cluster data... Migration queue size: 135 [PartitionService]

2014-04-23 13:32:32:805 INFO [node1398272538742] added node configuration id=Member [192.168.242.1]:2435 name=node1398272538742, now 1 nodes are configured [OHazelcastPlugin]

2014-04-23 13:32:32:820 INFO [node1398272538742] received updated status node1398272538742.GratefulDeadConcerts=OFFLINE [OHazelcastPlugin]

2014-04-23 13:32:32:820 INFO [node1398272538742] update configuration db=GratefulDeadConcerts from=node1398272538742 [OHazelcastPlugin]

2014-04-23 13:32:32:836 INFO updated distributed configuration for database: GratefulDeadConcerts:

----------

{

  "version":3,

  "replication":true,

  "autoDeploy":true,

  "hotAlignment":false,

  "offlineMsgQueueSize":0,"clusters":{

    "internal":{

  "replication":false

},

    "index":{

  "replication":false

},

    "*":{

  "replication":true,

  "readQuorum":1,

  "writeQuorum":2,

  "failureAvailableNodesLessQuorum":false,

  "readYourWrites":true,"partitioning":{

    "strategy":"round-robin",

    "default":0,

    "partitions":[["<NEW_NODE>","node1398272538742"]]

    }

}

    }

}

---------- [OHazelcastPlugin]

2014-04-23 13:32:32:836 INFO Saving distributed configuration file for database 'GratefulDeadConcerts' to: C:\nosql\orientdb1\databases\GratefulDeadConcerts\dis

tributed-config.json [OHazelcastPlugin]

2014-04-23 13:32:33:008 INFO [192.168.242.1]:2434 [orientdb] All migration tasks has been completed, queues are empty. [PartitionService]

2014-04-23 13:32:33:820 INFO [node1398272538742] received updated status node1398272538742.GratefulDeadConcerts=ONLINE [OHazelcastPlugin]

2014-04-23 13:32:46:774 INFO [192.168.242.1]:2434 [orientdb] memory.used=31.2M,memory.free=37.6M, memory.total=68.9M, memory.max=910.3M, memory.used/total=45.34%, memory.used/max=3.43%, load.process=0.00%, load.system=100.00%, load.systemAverage=-100.00%, thread.count=42,thread.peakCount=46, event.q.size=0, executor.

q.async.size=0, executor.q.client.size=0, executor.q.operation.size=0, executor.

q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.system.size=0, executor.q.operation.size=0, executor.q.response.size=0, operations.remote.size=0, operations.running.size=0, proxy.count=5, clientEndpoint.count=0, connection.active.count=1, connection.count=1 [HealthMonitor]

[Luca Garulli]

Seems both nodes have the same id: node1398272538742. Edit one of 2 orientdb-dserver-config.xml and change it.

Lvc@

Sent from Mobile device

--

---
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 orient-databa...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[alexpmorris]

Ah thank you, I think I did that by accident, since I was trying to resolve another issue, so I had just started again and copied one dir over the other and forgot to double-check that.  I started again with a completely fresh install, and this is what I get.  First node comes up fine, second one gets this:

---------- [OHazelcastPlugin]

2014-04-24 18:10:14:668 INFO [node1398377404356] adding node 'node1398377404356' in partition: db=GratefulDeadConcerts [*.0] [OHazelcastDistributedDatabase]

2014-04-24 18:10:14:668 INFO [node1398377404356] received added status node1398377404356.GratefulDeadConcerts=OFFLINE [OHazelcastPlugin]

2014-04-24 18:10:14:668 INFO updated distributed configuration for database: GratefulDeadConcerts:

----------

{

  "version":2,

  "replication":true,

  "autoDeploy":true,

  "hotAlignment":false,

  "offlineMsgQueueSize":0,"clusters":{

    "internal":{

  "replication":false

},

    "index":{

  "replication":false

},

    "*":{

  "replication":true,

  "readQuorum":1,

  "writeQuorum":2,

  "failureAvailableNodesLessQuorum":false,

  "readYourWrites":true,"partitioning":{

    "strategy":"round-robin",

    "default":0,

    "partitions":[["<NEW_NODE>","node1398377394043","node1398377404356"]]

    }

}

    }

}

---------- [OHazelcastPlugin]

2014-04-24 18:10:14:668 INFO Saving distributed configuration file for database 'GratefulDeadConcerts' to: C:\nosql\orientdb2\databases\GratefulDeadConcerts\distributed-config.json [OHazelcastPlugin]

2014-04-24 18:10:14:699 INFO [node1398377404356] found no previous messages in queue orientdb.node.node1398377404356.GratefulDeadConcerts.request [OHazelcastDistributedMessageService][node1398377404356]<-[node1398377394043] error on installing database GratefulDeadConcerts in C:\nosql\orientdb2/databases/GratefulDeadCo

ncerts com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage cannot be cast to com.orientechnologies.orient.server.distributed.ODistributedStorage

-> com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.executeOnLocal

Node(OHazelcastPlugin.java:647)

-> com.orientechnologies.orient.server.hazelcast.OHazelcastDistributedDatabase.onMessage(OHazelcastDistributedDatabase.java:454)

-> com.orientechnologies.orient.server.hazelcast.OHazelcastDistributedDatabase$1.run(OHazelcastDistributedDatabase.java:248)

-> java.lang.Thread.run(Thread.java:722)Exception in thread "main" com.orientechnologies.orient.server.distributed.ODistributedException: No response received from remote nodes for auto-deploy of database

        at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.installNewDatabases(OHazelcastPlugin.java:848)

        at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.startup(OHazelcastPlugin.java:193)

        at com.orientechnologies.orient.server.OServer.registerPlugins(OServer.java:718)

        at com.orientechnologies.orient.server.OServer.activate(OServer.java:239

)

        at com.orientechnologies.orient.server.OServerMain.main(OServerMain.java

:32)

2014-04-24 18:10:42:621 INFO [192.168.242.1]:2435 [orientdb] memory.used=30.3M,memory.free=47.1M, memory.total=77.4M, memory.max=910.3M, memory.used/total=39.18%, memory.used/max=3.33%, load.process=0.00%, load.system=100.00%, load.systemA

verage=-100.00%, thread.count=38, thread.peakCount=39, event.q.size=0, executor.q.async.size=0, executor.q.client.size=0, executor.q.operation.size=0, executor.q.query.size=0, executor.q.scheduled.size=0, executor.q.io.size=0, executor.q.sy

stem.size=0, executor.q.operation.size=0, executor.q.response.size=0, operations.remote.size=1, operations.running.size=0, proxy.count=9, clientEndpoint.count=0, connection.active.count=1, connection.count=1 [HealthMonitor]

and this comes up each time I try and browse to the node 2 studio:

2014-04-24 18:10:49:371 INFO Node is not online yet (status=STARTING), blocking the command until it's online 1/20 [ONetworkProtocolHttpDb]2014-04-24 18:10:49:684 INFO Node is not online yet (status=STARTING), blocking

the command until it's online 2/20 [ONetworkProtocolHttpDb]

2014-04-24 18:10:49:981 INFO Node is not online yet (status=STARTING), blocking the command until it's online 3/20 [ONetworkProtocolHttpDb]

2014-04-24 18:10:50:278 INFO Node is not online yet (status=STARTING), blocking the command until it's online 4/20 [ONetworkProtocolHttpDb]

2014-04-24 18:10:50:574 INFO Node is not online yet (status=STARTING), blocking the command until it's online 5/20 [ONetworkProtocolHttpDb]

...

[Luca Garulli]

Hi,

these problems were fixed in current OrientDB 1.7-SNAPSHOT. May you try with this version please? (it will be released as final in a couple of weeks).

Lvc@

[alexpmorris]

The version I was using for my previous post was this: orientdb-community-1.7-20140423.210035-155-distribution.zip

I also just tried the latest snapshot:  orientdb-community-1.7-20140425.142925-163-distribution.zip

Still the same problem!  :(

[Tyler Dinh]

I don't think this specific problem was fixed unless I'm looking at the wrong branch. This issue occurs on Windows because of the db path comparison.

I checked the develop branch and didn't see the fix. Am I looking at the wrong branch?

Tyler

[Tyler Dinh]

Alex,

It seemed you have the encountered the same problem I had seen.  You're running the two instances on windows. Is this correct?

You need to look at my other post for how to fix the code to get it to work.

Tyler

[alexpmorris]

That's correct, just running for two separate command prompts on Windows, starting in dirs orientdb1 and orientdb2.  That definitely sounds like it could be the problem.  It probably hasn't been caught sooner since most people are likely working with orientdb on linux instead of windows.

[alexpmorris]

I just tried the same thing in a ubuntu VM I had set up, and it worked perfectly!  So it's very likely a windows path issue like you suggested Tyler.  Thanks for that, I was going batty over this wondering what I was missing and why no one else seemed to have come across this problem yet! lol 

[galina manashirova]

Tyler,
I think I have the same issue , running on Windows and can't make replication work.
Could you please point me to your "other post"  where you describing how to fix it. Link would be nice.

thank you.
-galina