Replication not working with OrientDB 1.5.0

[edalorzo]

I have been struggling with making replication work with OrientDB 1.5.0.

Following the description of the failing simple scenario. Attached you can see configuration of every one of my two servers and their corresponding log files.

System Information

• OrientDB Version.......: 1.5.0
• Operating System......: Windows 7 Enterprise
• Installed RAM............: 4 GB
• Processor.................: Intel Core i5/2.6Ghz
• System Type.............: 64/bit
• Java Version..............: JDK-1.7.0_25-b17

  Scenario Step by Step:

  1. Downloaded the latest version of OrientDB 1.5.0
  2. Unzip into my local software directory.
  3. Make two exact copies of the folder (orient-graph-1.5.0, orient-graph-1.5.0-rep)
  4. Opened two Windows consoles for every installed copy (i.e. command prompt).
  5. Set the ORIENTDB_HOME in every console.
  6. Change the hazelcast.xml configuration settings to assign a manual port to every instance (although the scenario also fails with automatic port assignment).
  7. Change the orientdb-dserver-config.xml so that every instance used different port settings (again the scenario fails even if I use automatic port assignment).
  8. Enable FINER log statistics in the orientdb-server-log.properties file.
  9. Start dserver.bat in instance 1.
  10. Start dserver.bat in instance 2.
  11. After instances are up and running I open a console.bat for every instance.
  12. Connect to the tinkerpop database in every console.
  13. Run the simple command: insert into v set name = 'Tinkerbell' in the first instance console.
  14. In both consoles run the command: select from v where name = 'Tinkerbell'.
  15. The record appears in the first instance where it was inserted. Nothing got replicated on the second instance.
  16. Restart both the servers and reopen consoles.
  17. In both consoles run the command: select from v where name = 'Tinkerbell'.
  18. The record was clearly persisted in the first server, and still not replicated onto the second.

      Additional Notes:

• The exact same scenario works fine with OrientDB 1.4.1.
• The scenario fails whether I ran the servers in the same machine or in two different machines.
• There are no firewalls in place in my current network environment.

  Log Files and Configuration

• Instance 1
• Instance 2

[lvca]

Seems databases are not aligned at the start. Where you placed the database directory? It needs to stay under each $ORIENTDB_HOME/databases and MUST have the same name.

[edalorzo]

The two database installations were two exact copies. In the databases folder there was only the tinkerpop database that comes by default with the product.

The orientdb installations and their corresponding databases folders were placed under:

+--- C:
       \--- Software
             \--- orientdb-graph-1.5.0
                   \--- databases
                         \--- tinkerpop
             \--- orientdb-graph-1.5.0-rep
                   \-- databases
                        \--- tinkerpop

Since I was running the two instances in the same machine I did not set the ORIENTDB_HOME globally, but in the terminal session by doing SET ORIENTDB_HOME=C:\Software\orientdb-graph-1.5.0 and SET ORIENTDB_HOME=C:\Software\orientdb-graph-1.5.0-rep respectively in every terminal.

Issuing an echo %ORIENTDB_HOME% confirmed in every case that the variable was present in every corresponding terminal session.

After setting the variables I ran the ORIENTDB_HOME\bin\dserver.bat in every terminal.

To test the insert I used another set of terminals in which, once again, I set the ORIENTDB_HOME variable locally and then opened the ORIENTDB_HOME\bin\console.bat program.

As I mentioned in the post I also tested all this using two different machines with the same results.

[lvca]

Seems all perfect. Maybe it doesn't get the env variable. Try to modify the dserver.bat adding -DORIENTDB_HOME= but don't use backslash \ but slash /

[edalorzo]

Man Lucca, you are the best!

That was it! I tested first in a Linux box and it worked like a charm, then I retested the Windows scenario and it worked too.

Still, I believe the application should handle the ORIENTDB_HOME variable according to the operating system, but at least I now can make this work.

Thanks a million, Lucca!

[lvca]

Great! ;-)

[lvca]

The / works on all the OS, so use always /.

[edalorzo]

As a matter of fact, I feel this case should not be closed until the problem has been properly addressed. Paths should be specified according to the user's operating system. This is customary of other Java-related paths like JAVA_HOME, ANT_HOME or CATALINA_HOME.

To this day, I have never had to specify any of those paths using forward slashes in Windows. They all can be specified using the path separator supported by the operating system.

I believe the ORIENTDB_HOME should be the same.

[lvca]

We convert ORIENTDB_HOME path once loaded.