I downloaded orientdb-community-2.1.1-20150812.003537-6-distribution.tar.gz and no longer get the IllegalStateException. Yay!
I'm wondering if the autodeploy logic should be changed also. That is, a "replica" shouldn't autodeploy to a "master". I can't think of a case where that would be desirable. I was able to make this happen by: - turn on testnode1 (master) - turn on testnode2 (replica). testnode1 (master) autodeploys db to testnode2 (replica). - turn off testnode1 - turn on testnode1 (master). testnode2 (replica) autodeploys db to testnode1 (master). On Tuesday, August 11, 2015 at 5:12:52 PM UTC-7, l.garulli wrote: > > Fixed in last "2.1.x" and "develop" branches, respectively 2.1.1-SNAPSHOT > and 2.2.0-SNAPSHOT. > > Thanks for reporting it. > > Best Regards, > > Luca Garulli > Founder & CEO > OrientDB <http://orientdb.com/> > > > On 12 August 2015 at 01:52, Luca Garulli <[email protected] > <javascript:>> wrote: > >> Ok, this is definitely a bug. Just opened >> https://github.com/orientechnologies/orientdb/issues/4775 to track it. >> >> Best Regards, >> >> Luca Garulli >> Founder & CEO >> OrientDB <http://orientdb.com/> >> >> >> On 11 August 2015 at 21:13, <[email protected] <javascript:>> wrote: >> >>> The unmodified default-distributed-db-config.json works (i.e. without >>> "replica" role enabled). >>> >>> { >>> "autoDeploy": true, >>> "hotAlignment": false, >>> "executionMode": "undefined", >>> "readQuorum": 1, >>> "writeQuorum": 2, >>> "failureAvailableNodesLessQuorum": false, >>> "readYourWrites": true, >>> "servers": { >>> "*": "master" >>> }, >>> "clusters": { >>> "internal": { >>> }, >>> "index": { >>> }, >>> "*": { >>> "servers": ["<NEW_NODE>"] >>> } >>> } >>> } >>> >>> >>> Enabling the replica role like below and shown at >>> https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Forientechnologies%2Forientdb%2Fissues%2F3772&sa=D&sntz=1&usg=AFQjCNGUPw8mYKa3GfIN3Sc5nvSXMvUZtQ >>> >>> results in java.lang.IllegalStateException on testnode2 after the db >>> autodeploys. >>> >>> { >>> "autoDeploy": true, >>> "hotAlignment": false, >>> "offlineMsgQueueSize" : 0, >>> "readQuorum": 1, >>> "writeQuorum": 2, >>> "failureAvailableNodesLessQuorum": false, >>> "readYourWrites": true, >>> "servers": { >>> "testnode1" : "master", >>> "*": "replica" >>> }, >>> "clusters": { >>> "internal": { >>> }, >>> "index": { >>> }, >>> "*": { >>> "servers" : [ "<NEW_NODE>" ] >>> } >>> } >>> } >>> >>> >>> On Tuesday, August 11, 2015 at 11:47:09 AM UTC-7, l.garulli wrote: >>>> >>>> Hi, >>>> So the problem was in default-distributed-db-config.json file? >>>> >>>> Best Regards, >>>> >>>> Luca Garulli >>>> Founder & CEO >>>> OrientDB <http://orientdb.com/> >>>> >>>> >>>> On 11 August 2015 at 19:45, <[email protected]> wrote: >>>> >>>>> I did the same process without modifying >>>>> the default-distributed-db-config.json which worked. So more specifically, >>>>> >>>>> 2 instances, ubuntu 14.04 >>>>> >>>>> - On both, install ubuntu 14.04, install Oracle Java 1.8.0_51 64bit >>>>> >>>>> - On both, >>>>> extract orientdb-community-2.1.1-20150809.182628-3-distribution.tar.gz >>>>> (which >>>>> includes GratefulDeadConcerts db). >>>>> >>>>> - On both, modify hazelcast.xml as shown in your example (i.e. 2 >>>>> manually specified ips) >>>>> >>>>> - On first instance, cd /opt/orientdb-community-2.1.1-SNAPSHOT/bin . >>>>> Then, ./dserver.sh . specify a root password. Interactively set nodename >>>>> to >>>>> "testnode1". >>>>> /opt/orientdb-community-2.1-rc6/databases/GratefulDeadConcerts/distributed-config.json >>>>> >>>>> updates to new settings and >>>>> INFO [testnode1] received updated status >>>>> testnode1.GratefulDeadConcerts=ONLINE [OHazelcastPlugin] >>>>> >>>>> - On second instance, cd /opt/orientdb-community-2.1.1-SNAPSHOT/bin . >>>>> Then, ./dserver.sh . specify a root password. Interactively set nodename >>>>> to >>>>> "testnode2". >>>>> >>>>> testnode1 creates backup of GratefulDeadConcerts and sends it to >>>>> testnode2. testnode2 installs db. Both nodes >>>>> have GratefulDeadConcerts=ONLINE with no java.lang.IllegalStateException. >>>>> >>>>> -- >>>>> >>>>> --- >>>>> 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] <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.
