-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synchronization in a cluster fails #7073
Comments
@pavlop-asg do you have the log of the other server too? |
Could you please post the hazelcast.xml of both servers? |
They are the same for both <?xml version="1.0" encoding="UTF-8"?>
<hazelcast
xsi:schemaLocation="http://www.hazelcast.com/schema/config hazelcast-config-3.5.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.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>
</properties>
<network>
<port auto-increment="true">2434</port>
<join>
<multicast enabled="true">
<multicast-group>235.1.1.1</multicast-group>
<multicast-port>2494</multicast-port>
</multicast>
</join>
</network>
<executor-service>
<pool-size>16</pool-size>
</executor-service>
</hazelcast> |
Looks like your fix helped |
Hi @pavlop-asg, Glad to hear the issue has been fixed. Thanks for your patience and tests Thanks, |
Fixed by ce26174 Release notes updated No changes in the documentation required Closing |
What is the fix? Please share the details |
OrientDB Version, operating system, or hardware.
2.2.15-SNAPSHOT
Operating System
Expected behavior and actual behavior
This issue I have faced when I tested the issue #6999 after I was fixed.
There is an example. We have node-1 and after node-2, we write a value "1" to a document when node-1 and node-2 are up. We shut down node-2 and write value "2", after we shut down node-1 as well. When we start node-2 and after node-1 data is being synchronized, but we get the following issues:
Only when we restart all the cluster everything start working fine.
This are the logs from node-1:
The text was updated successfully, but these errors were encountered: