-
Notifications
You must be signed in to change notification settings - Fork 872
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
A fresh node announces ONLINE status for a database before completing full sync #10386
Comments
ikysil
changed the title
A fresh node announces ONLINE status for database before completing full sync
A fresh node announces ONLINE status for a database before completing full sync
Jan 17, 2025
Logs from live node:
|
Logs from fresh node:
|
hi @cschockaert Thank you, the same functional area seems to be affected. |
tglman
added a commit
that referenced
this issue
Jan 17, 2025
tglman
added a commit
that referenced
this issue
Jan 17, 2025
The issue is still present in 3.2.38-SNAPSHOT (3.2.38-20250117.191042-3). See the logs attached. fresh-node-orientdb-3.2.38-SNAPSHOT.txt |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OrientDB Version: 3.2.36, reproduced with 3.2.26 and 3.2.37
Java Version: Amazon Corretto 21.0.5
OS: Linux
Actual behavior
The fresh node announces ONLINE status for a database BEFORE completing full sync.
The
OrientDBRemote
clients connecting to this node and querying the synchronizing database are blocked waiting until full sync finishes.Expected behavior
The fresh node announces ONLINE status for a database AFTER completing full sync.
The
OrientDBRemote
clients connecting to this node and querying the synchronizing database should receive an error.The text was updated successfully, but these errors were encountered: