orientechnologies / orientechnologies/orientdb

Migration from single node to distributed cluster

Open
#9,822 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
5k
Forks
868
Avg merge
15h 6m
Merged PRs (30d)
18

Description

I am trying to migrate from single orientdb node to distributed cluster. So i've dumped db from single instance

> EXPORT DATABASE /temp/something.export

After I am trying import it in distributed orientdb cluster:

orientdb {db=something}> IMPORT DATABASE /something.export.gz -preserveClusterIDs=true        

Importing database DATABASE /something.export.gz -preserveClusterIDs=true...
Error: com.orientechnologies.orient.core.exception.OStorageException: Error sending import request
    DB name="something"

Error: com.orientechnologies.orient.core.db.tool.ODatabaseExportException: Error on importing database 'something' from file: /tmp/import5802832137826087861something.export.gz

Error: com.orientechnologies.orient.core.exception.OStorageException: Cannot route TX operation against distributed node
    DB name="something"

Error: java.lang.NullPointerException

What I am doing wrong? What does mean Cannot route TX operation against distributed node?

Single instance is on 3.0.34 version and distributed - on 3.2.5.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the reported EXPORT DATABASE and IMPORT DATABASE commands, the full exception chain, and the version difference between 3.0.34 and 3.2.5. Reproduce the migration if possible and trace the distributed import path around “Cannot route TX operation against distributed node”; done means identifying the cause and documenting a supported migration procedure or required version alignment.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli, databases, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.