orientechnologies / orientechnologies/orientdb

Scheduler fails on distributed database

Open
#9,633 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

OrientDB Version: 3.0.37
Java Version: 1.8
OS: Windows

Using a distributed database (2 or 3 nodes)

Expected behavior

The scheduler should be created with the command :
INSERT INTO oschedule
SET name = 'myEvent',
function = (SELECT FROM ofunction WHERE name = 'myFunction'),
rule = "* */1 * * * ?"

Actual behavior

With a standalone database, the OScheduler record is created correctly, and the task is started normaly.
With a distributed database, I get an error :

Error when creating the scheduler
java.lang.IllegalStateException: The current database instance (com.orientechnologies.orient.server.distributed.impl.ODatabaseDocumentDistributed@bc98660) is not active on the current thread (Thread[OrientDB HTTP Connection /127.0.0.1:2480>-/127.0.0.1:63380,5,OrientDB]). Current active
database is: com.orientechnologies.orient.server.distributed.impl.ODatabaseDocumentDistributed@5866e8c8

Is the scheduler working normaly in a distributed databese ?
Thanks for your help

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

Reproduce the SQL INSERT on a two- or three-node distributed database using OrientDB 3.0.37, then compare it with the standalone behavior. Trace the scheduler creation failure reported for the distributed database and verify that the scheduler record is created and its task starts normally across nodes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.