lvca
commented
7 years ago Hi @mongoose666, first I don't suggest you to use 3.0.0-SNAPSHOT because it's still in development. Please retry with last 2.2.13 GA and let me know how is going. Thanks.
Closed mongoose666 closed 7 years ago
lvca
commented
7 years ago Hi @mongoose666, first I don't suggest you to use 3.0.0-SNAPSHOT because it's still in development. Please retry with last 2.2.13 GA and let me know how is going. Thanks.
mongoose666
commented
7 years ago Hi @lvca, Thanks for the prompt reply :) The same issue is in 2.2.12 as well - I went to 3.0.0-SNAPSHOT to see if it had been fixed. Also I might add there is a serious issue with getString( "@rid" ) and getObject( "@rid" ) within the JDBC Result Row where a null document check is not performed and then choosing the document.getIdentity() from the Result Row to return the @rid value. I circumvented/fixed this if you would like me to send you the fixes or information on where the problem is? This is in both 2.2.12 and 3.0.0-SNAPSHOT.
Cheers, Andy.@lvca I would also like to mention that I am running two separate JVMs but in "Embedded" mode as this is paramount for our application. As we are already running a server core and wish to be able to start and stop various portions of the application as needed via administrative interfaces of varying types (application, web etc). I am not sure if it's because I am running it in Embedded mode or not ... but this is a necessity. Is there a JVM arg, or System property maybe that is missing that the scripts/batch files set that I may not be setting?
lvca
commented
7 years ago @mongoose666 could you please open a new ticket for the JDBC issue, so I can assign it to a different developer?
About the tutorial, we're already working on updating the one in the docs. @santo-it will work on it.
About this issue, are you able to reproduce it with 2.2.17? We recently fixed a bug in the initial start that in some cases failed.
mongoose666
commented
7 years ago @lvca - Thank you for the reply, However as this took so long to get any feedback from I have gone with Apache Cassandra which provided working examples straight out of the box.
Cheers, Andy.@mongoose666 what a shame! :-) Anyway, we'll use this issue to improve the first user experience.
mongoose666
commented
7 years ago @Ivca - Sorry about that but as a lead Software Engineer on a product it must work for me within the first hour if it does not I bin it :( but your guys vision and direction is a good one so don't stop forging ahead as the design decisions you have made are good ones :)
coldfuzz
commented
7 years ago Hi Are there any improvement about this bug.
santo-it
commented
7 years ago Hi @coldfuzz ,
Since you are a Customer of us, if you need any help with running OrientDB in distributed mode, or have any other questions, please do open a support ticket - and the Support Team will help you there
Many thanks,
deepsm007
commented
7 years ago Hi I have been trying to run the OrientDB in distributed mode using the hazelcast multicast join. I am using the 2.2.18. But the cluster is not formed. Using 2 VM on local network to form the cluster.
hazelcast configuration for both the nodes are same
Have been trying this multicast for hours. Can i get some help with it?
hazelcast.xml
<?xml version="1.0" encoding="UTF-8"?>
<hazelcast xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.3.xsd" xmlns="http://www.hazelcast.com/schema/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<group>
<name>orientdb</name>
<password>orientdb</password>
</group>
<properties>
<property name="hazelcast.phone.home.enabled">false</property>
<property name="hazelcast.mancenter.enabled">false</property>
<property name="hazelcast.memcache.enabled">false</property>
<property name="hazelcast.rest.enabled">false</property>
<property name="hazelcast.wait.seconds.before.join">5</property>
<property name="hazelcast.operation.thread.count">1</property>
<property name="hazelcast.operation.generic.thread.count">1</property>
<property name="hazelcast.client.event.thread.count">1</property>
<property name="hazelcast.event.thread.count">1</property>
<property name="hazelcast.heartbeat.interval.seconds">5</property>
<property name="hazelcast.max.no.heartbeat.seconds">30</property>
<property name="hazelcast.icmp.enabled">true</property>
<property name="hazelcast.icmp.timeout">5000</property>
<property name="hazelcast.icmp.ttl">3</property>
<property name="hazelcast.merge.next.run.delay.seconds">15</property>
</properties>
<network>
<port auto-increment="true">2434</port>
<join>
<multicast enabled="true">
<multicast-group>235.1.1.1</multicast-group>
<multicast-port>2434</multicast-port>
</multicast>
</join>
</network>
<executor-service>
<pool-size>16</pool-size>
</executor-service>
</hazelcast>orientdb-server-config.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<orient-server>
<handlers>
<handler class="com.orientechnologies.orient.graph.handler.OGraphServerHandler">
<parameters>
<parameter value="true" name="enabled"/>
<parameter value="50" name="graph.pool.max"/>
</parameters>
</handler>
<handler class="com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin">
<parameters>
<parameter value="${distributed}" name="enabled"/>
<parameter value="${ORIENTDB_HOME}/config/default-distributed-db-config.json" name="configuration.db.default"/>
<parameter value="${ORIENTDB_HOME}/config/hazelcast.xml" name="configuration.hazelcast"/>
<parameter value="node1" name="nodeName"/>
</parameters>
</handler>
<handler class="com.orientechnologies.orient.server.handler.OJMXPlugin">
<parameters>
<parameter value="false" name="enabled"/>
<parameter value="true" name="profilerManaged"/>
</parameters>
</handler>
<handler class="com.orientechnologies.orient.server.handler.OAutomaticBackup">
<parameters>
<parameter value="false" name="enabled"/>
<parameter value="${ORIENTDB_HOME}/config/automatic-backup.json" name="config"/>
</parameters>
</handler>
<handler class="com.orientechnologies.orient.server.handler.OServerSideScriptInterpreter">
<parameters>
<parameter value="true" name="enabled"/>
<parameter value="SQL" name="allowedLanguages"/>
</parameters>
</handler>
</handlers>
<network>
<sockets>
<socket implementation="com.orientechnologies.orient.server.network.OServerTLSSocketFactory" name="ssl">
<parameters>
<parameter value="false" name="network.ssl.clientAuth"/>
<parameter value="config/cert/orientdb.ks" name="network.ssl.keyStore"/>
<parameter value="password" name="network.ssl.keyStorePassword"/>
<parameter value="config/cert/orientdb.ks" name="network.ssl.trustStore"/>
<parameter value="password" name="network.ssl.trustStorePassword"/>
</parameters>
</socket>
<socket implementation="com.orientechnologies.orient.server.network.OServerTLSSocketFactory" name="https">
<parameters>
<parameter value="false" name="network.ssl.clientAuth"/>
<parameter value="config/cert/orientdb.ks" name="network.ssl.keyStore"/>
<parameter value="password" name="network.ssl.keyStorePassword"/>
<parameter value="config/cert/orientdb.ks" name="network.ssl.trustStore"/>
<parameter value="password" name="network.ssl.trustStorePassword"/>
</parameters>
</socket>
</sockets>
<protocols>
<protocol implementation="com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary" name="binary"/>
<protocol implementation="com.orientechnologies.orient.server.network.protocol.http.ONetworkProtocolHttpDb" name="http"/>
</protocols>
<listeners>
<listener protocol="binary" socket="default" port-range="2424-2430" ip-address="0.0.0.0"/>
<listener protocol="http" socket="default" port-range="2480-2490" ip-address="0.0.0.0">
<commands>
<command implementation="com.orientechnologies.orient.server.network.protocol.http.command.get.OServerCommandGetStaticContent" pattern="GET|www GET|studio/ GET| GET|*.htm GET|*.html GET|*.xml GET|*.jpeg GET|*.jpg GET|*.png GET|*.gif GET|*.js GET|*.css GET|*.swf GET|*.ico GET|*.txt GET|*.otf GET|*.pjs GET|*.svg GET|*.json GET|*.woff GET|*.woff2 GET|*.ttf GET|*.svgz" stateful="false">
<parameters>
<entry value="Cache-Control: no-cache, no-store, max-age=0, must-revalidate\r\nPragma: no-cache" name="http.cache:*.htm *.html"/>
<entry value="Cache-Control: max-age=120" name="http.cache:default"/>
</parameters>
</command>
<command implementation="com.orientechnologies.orient.graph.server.command.OServerCommandGetGephi" pattern="GET|gephi/*" stateful="false"/>
</commands>
<parameters>
<parameter value="utf-8" name="network.http.charset"/>
<parameter value="true" name="network.http.jsonResponseError"/>
</parameters>
</listener>
</listeners>
</network>
<storages/>
<users>
<user resources="*" password="{PBKDF2WithHmacSHA1}9DFF3F5B0F6D4C337EB4FF7C6D93AE19582B11933DB8A82C:76A668C0E4519F7E795E75354C6BD4747BA464EAB86169C6:65536" name="root"/>
<user resources="connect,server.listDatabases,server.dblist" password="{PBKDF2WithHmacSHA1}8430483B7BD8AEC7FA648C0B64262DFE7CD9265F091A28F6:094E2CF05590EC20741D57EF97D097C5A015B0E0D08841AD:65536" name="guest"/>
</users>
<properties>
<entry value="1" name="db.pool.min"/>
<entry value="50" name="db.pool.max"/>
<entry value="false" name="profiler.enabled"/>
</properties>
<isAfterFirstTime>true</isAfterFirstTime>
</orient-server>@deepsm007 can you post also the logs of both servers?
lvca
commented
7 years ago Closing this issue because of no response after a long time.
OrientDB Version, operating system, or hardware.
Operating System
Expected behavior and actual behavior
Have been trying for hours to get the most basic 2 node distributed database cluster working with TCP-IP not MULTICAST.
It continues to timeout waiting for the other node. This is when running (in a test environment) on the same development machine but with different ports. They seem to connect with each other,
This problem seems to have been around for a while and is dismissed regularly and marked as resolved. Whereas everyone starting out seems to be getting this issue. It would be nice if the OrientDB team took it seriously and put together a proper tutorial from beginning to end with proof that it works.
I have been in the industry 32 years so am no stranger to the difficulties of software design but when something as simple as this does not work it makes me want to choose another database which would be a shame as I like the features that OrientDB has boasted about, simplicity being one of them.
Second instance (node) log:
First instance (node) log:
Steps to reproduce the problem
Instance ONE server configuration:
Instance TWO server configuration:
Instance ONE Hazlecast configuration:
Instance TWO Hazelcast configuration:
Default distributed DB config JSON: