Hi Santosh, Have you tried with 2.0-M3? However, we've 3 remaining issues into the distributed part before to release 2.0-RC.
Lvc@ On 2 December 2014 at 20:54, Santosh M <[email protected]> wrote: > > Not sure if my question is not clear. I will try to explain what I was > trying to achieve : > > I had setup a 3 node cluster with autodeploy=true set in > the default-distributed-db-config.json file. My expectation was that with > this configuration, whenever I create a database, it will be queriable from > all 3 nodes. I used the steps mentioned in my original post to create the > database. > > Am I missing something ? > > Regards, > Santosh > > On Tuesday, November 25, 2014 10:36:36 AM UTC-8, Santosh M wrote: >> >> Hi, >> >> I have setup a three node cluster using OrientDB 2.0 M2. On host1 I run >> the below commands : >> >> create database remote:<host-IP>/testdb root root >> >> create class testclass >> >> Insert into testclass set name='test01' >> >> We checked that the class (table) got created on all three nodes. We did >> this by looking for the testclass.cpm and testclass.pcl. >> >> I could connect from host1 using console.sh and query the table. However, >> I could not connect from host2 and host3 using console.sh. The command just >> hung. Am I missing a grant or something to be able to connect from the >> other nodes: >> >> We have set autodeploy=true in our default-distributed-db-config.json >> file >> >> Regards, >> Santosh >> >> >> >> > -- > > --- > 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. > -- --- 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.
