Hi Ryan

Thanks for the response.

Below answers to your questions:-

1. Are you backing up and restoring the same keyspace on the same Scylla cluster, or is one of those variables changing? - The keyspace is same idgraph1

2. Are you running the backup and restore on all nodes of the scylla cluster (backup and restore is a per-node operation)? - Yes I am running this as mentioned at https://docs.scylladb.com/operating-scylla/procedures/backup-restore/

3. Is the data intact? - I compared the names & sizes of edgestore, graphindex & janusgraph_ids tables on source and destination machines, both are name listing & sizes are exactly the same in both source and destination clusters

Still getting the same error.

'Could not find type for id: 3597'

When I checked g.V(3597) in source cluster, it represents 'node' label in the source cluster, but g.V(3597) gives nothing.

Thanks

Saurabh Verma 
PE
 

*DISCLAIMER - This email message and any attachments to it are confidential and intended solely for the addressee(s). If you are not the intended recipient, please delete the message and notify the sender immediately. Also, you are notified that any unauthorized disclosure, use, copying, or storage of this message or its attachments is strictly prohibited. Imprint



 

On Thu, 11 Apr 2019 at 19:18, Ryan Stauffer <ry...@...> wrote:

Big picture, my understanding is that you're trying to backup and restore the underlying Scylla keyspace ("idgraph1"), right (procedure described here https://docs.scylladb.com/operating-scylla/procedures/backup-restore/)?  If that restore isn't successful, or incomplete, you can end up with some "interesting" behavior from JG.

The error you're getting implies that the underlying keyspace isn't fully intact, and rows are missing, so let's take a look at the underlying backup/restore procedure.  I'd also make sure that there are no JG instances trying to communicate with Scylla during this process.

Are you backing up and restoring the same keyspace on the same Scylla cluster, or is one of those variables changing?  Are you running the backup and restore on all nodes of the scylla cluster (backup and restore is a per-node operation)?

Thanks,

Ryan  

On Wed, Apr 10, 2019 at 10:11 AM SAURABH VERMA <saurabh...@...> wrote:

Hi all

I am trying to recover a JG cluster backed by scyllaDB using steps at https://groups.google.com/d/msg/aureliusgraphs/WyJpzZ4Wcuw/AW4-1GXRfI0J

I am always getting the error as below

Could not find type for id: 2313

I am following below steps:-

- systemctl stop scylla-server

- rm -rf /var/lib/scylla/data/*

- rm -rf /var/lib/scylla/commitlog/*

- systemctl start scylla-server

- schema registration

- systemctl stop scylla-server

- data copy

- sudo chown -R scylla:scylla /var/lib/scylla/data/idgraph1

- systemctl start scylla-server

- nodetool repair

Please guide me whats the correct sequence of steps for recovery or any other way to recover JG data?

Thank

Saurabh

--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To post to this group, send email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/82ac6954-6bc7-4ae8-a06b-e82fbd3cc091%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgr...@....
To post to this group, send email to janusgr...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/CA%2BCnsn%3DQHgDBghM9v0XowjPRB1toYV%2B1sY5W9FjWcFxDPjEyCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.