Skip to content
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

Distributed sync fails because WAL file rotates #8144

Closed
aandriyc opened this issue Mar 7, 2018 · 1 comment
Closed

Distributed sync fails because WAL file rotates #8144

aandriyc opened this issue Mar 7, 2018 · 1 comment
Assignees

Comments

@aandriyc
Copy link

aandriyc commented Mar 7, 2018

OrientDB Version: 2.2.31

Java Version: 1.8.0_131-b11

OS: Amazon Linux

Expected behavior

Initial database sync completes successfully

Actual behavior

During sync WAL file name rotates, but sync looks for old file and replication fails (actual wal files that present during failure are some-db.2.wal, some-db.3.wal even though some-db.0.wal was in place when replication started):

java.lang.IllegalArgumentException: Directory /opt/orientdb/databases/some-db/some-db.0.wal not found
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.addFolder(OZIPCompressionUtil.java:145)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.addFolder(OZIPCompressionUtil.java:127)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.compressDirectory(OZIPCompressionUtil.java:57)
at com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.backup(OLocalPaginatedStorage.java:229)
at com.orientechnologies.orient.server.distributed.impl.ODistributedStorage.backup(ODistributedStorage.java:1880)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.backup(ODatabaseDocumentTx.java:3060)
at com.orientechnologies.orient.server.distributed.impl.task.OSyncDatabaseTask$1.run(OSyncDatabaseTask.java:123)
at java.lang.Thread.run(Thread.java:748)

Steps to reproduce

Do initial sync in distributed setup on large DB, so sync takes significant time

@andrii0lomakin
Copy link
Member

Duplication of #8005 will try to fix it ASAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants