Used 1.7.4 and with the following config change in the second folder
configuration could see the processes discovering each other atleast.
2nd server
- <port auto-increment="true">2435</port>
<join>
<multicast enabled="true">
<multicast-group>235.1.1.1</multicast-group>
<multicast-port>2434</multicast-port>
</multicast>
</join>
Thanks
On Friday, June 20, 2014 1:52:20 PM UTC-7, moksh n wrote:
>
> Trying to test the distributed configuration with in the same machine. Can
> not see the second instance joining the cluster.
>
> - C:\orientdb-community-1.7.3 *(Server1)*
> - C:\orientdb-community-1.7.3\config\Hazelcast.xml is the default
> config with no changes.
> - default-distributed-db-config.json is the default config with no
> changes.
> - orientdb-dserver-config.xml
> - <parameter value="node1403294863986" name="nodeName"/>
>
>
> - *Server2 *is the same machine as *Server1 *with different folder
> - Copied the whole OrientDB directory(1.7.3) into a new folder
> called C:\orientdb-community-1.7.3-dup
> - C:\orientdb-community-1.7.3-dup\config\Hazelcast.xml is the default
> config with no changes.
> - <port auto-increment="true">2435</port>
> <join>
> <multicast enabled="true">
> <multicast-group>235.1.1.1</multicast-group>
> <multicast-port>2435</multicast-port>
> </multicast>
> </join>
> - default-distributed-db-config.json is the default config with no
> changes.
> - orientdb-dserver-config.xml
> - <parameter value="node1403278140075" name="nodeName"/>
>
>
> Can not see the second instance joining the cluster. Any issues with the
> above configuration?
>
> Attached the server logs.
>
> Thanks
>
>
>
>
>
--
---
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.
