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

Graph not updating index #4907

Closed
sajid2045 opened this issue Sep 2, 2015 · 15 comments
Closed

Graph not updating index #4907

sajid2045 opened this issue Sep 2, 2015 · 15 comments
Assignees
Labels
Milestone

Comments

@sajid2045
Copy link

On version 2.1.1,

I create a fresh cluster of 3 nodes,

I run the following script on 1 of the node (via studio):

CREATE class Topic extends V
CREATE PROPERTY Topic.name STRING
CREATE PROPERTY Topic.created DATETIME


CREATE class Root extends Topic
CREATE INDEX Root.name NOTUNIQUE
CREATE class Event extends Topic
CREATE INDEX Event.name NOTUNIQUE

CREATE class Subscriber extends V
CREATE PROPERTY Subscriber.subscriptionId STRING
CREATE PROPERTY Subscriber.subscriberType STRING
CREATE PROPERTY Subscriber.name STRING
CREATE PROPERTY Subscriber.created DATETIME




CREATE class Device extends Subscriber
CREATE PROPERTY Device.deviceId STRING
CREATE PROPERTY Device.type STRING
CREATE PROPERTY Device.vendor STRING
CREATE INDEX Device.subscriptionId UNIQUE


CREATE class User extends Subscriber
CREATE PROPERTY User.login STRING
CREATE INDEX User.subscriptionId UNIQUE
CREATE INDEX User.login UNIQUE


CREATE class SubscriptionsJson extends V
CREATE PROPERTY SubscriptionsJson.uniqueDocumentId STRING
CREATE INDEX SubscriptionsJson.uniqueDocumentId UNIQUE

Now, I create some Entries like Device & User

But when I do select from User where subscriptionId = 'xxx', it does not return anything, but once I rebuild the index, it returns the record. This I need to do everytime I add a new Entity.

Any pointers?

@sajid2045
Copy link
Author

@lvca
Copy link
Member

lvca commented Sep 2, 2015

Are you using synchronous replication?

@sajid2045
Copy link
Author

Yes,

Also, it looks like a cluster problem, when running in standalone mode, everything works fine!

@lvca
Copy link
Member

lvca commented Sep 2, 2015

By reading the logs I found something could be the problem. I'll keep you posted soon.

@sajid2045
Copy link
Author

Hi ,

Although this issue is tagged as Medium, It is a blocker from us running in clustered mode. Can you reproduce this issue on your side? I am just wondering if its a bug or setup / index creation issue on our side. Either way, one would hope the system to behave same in clustered vs standalone mode.

@lvca
Copy link
Member

lvca commented Sep 3, 2015

This problem could be related to: #4913. Working to reproduce it.

@lvca lvca self-assigned this Sep 3, 2015
@lvca lvca added this to the 2.1.x (next hotfix) milestone Sep 3, 2015
@lvca
Copy link
Member

lvca commented Sep 3, 2015

With synchronous replication I'm not able to reproduce it. Trying with async.

@lvca
Copy link
Member

lvca commented Sep 3, 2015

With synchronous replication I'm not able to reproduce it. Trying with asynch.

@sajid2045
Copy link
Author

That is strange. What process are you following to add the schema.sql?

I tried creating a fresh 3 node synchronous cluster.

Then on one of the workbench , I run the sql scripts one by one. Not sure if thats the right way of doing it.

@lvca
Copy link
Member

lvca commented Sep 3, 2015

Tried with async replication and works. How can I reproduce it? Do you have any logs? Please could you send them to support@ ?

@sajid2045
Copy link
Author

which log you are after?

@lvca
Copy link
Member

lvca commented Sep 3, 2015

I started 3 nodes and executed your exact commands to create the schema, the I've create 3 User and query from other nodes by using the index and result was returned.

@sajid2045
Copy link
Author

This looks like working after I completely removed orientdb instances directory and did a fresh install. I think the DB entered a corrupted state somehow.

What is a proper way of deleting the data directories of orient so it becomes a clean install?

@lvca
Copy link
Member

lvca commented Sep 7, 2015

Just delete the database directory and OrientDB will ask a fresh copy to the existent server cluster.

@lvca lvca modified the milestones: 2.1.x (next hotfix), 2.1.2 Sep 9, 2015
@lvca lvca modified the milestones: 2.1.2, 2.1.x (next hotfix) Sep 9, 2015
@coldfuzz
Copy link

Hi Luca;
I also get the same problem about index at version 2.1.1
This problem is solved with 2.1.2 or you offer another solution.
Best Regards.

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

No branches or pull requests

4 participants