janusgraph-dev@lists.lfaidata.foundation | JG recovery is not working with a 2 node scyllaDB cluster as backend

Home Messages Hashtags Subgroups Calendar

Date Date 1 - 12 of 12

JG recovery is not working with a 2 node scyllaDB cluster as backend

Ryan Stauffer <ry...@...> #1070 No problem at all, glad it worked out! A good reference as well is the Scylla community slack channel - the engineers on there are very helpful in troubleshooting, and anyone using open source is welcome to join the conversation. toggle quoted message Show quoted text On Fri, Apr 12, 2019 at 4:31 AM Saurabh Verma <saurab...@...> wrote: Hi Ryan The above method works successfully for JG recovery, thank you so much Ryan for the timely assistance, and sharing this crucial & fundamental information. Thanks a lot once again 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 Fri, 12 Apr 2019 at 02:03, Ryan Stauffer <ry...@...> wrote: For terminology, I'm going to call your 2 clusters "source" and "replica". "Source" is the Scylla cluster that you want to backup, and "replica" is the cluster that you want to copy the data to. For this to work, you need a mapping of "source" node to exactly one "replica" node. Ex: Source cluster = 3 Nodes (source1, source2, source3) Replica cluster = 3 Nodes (replica1, replica2, replica3) Where we have a mapping: source1 -> replica1 source2 -> replica2 source3 -> replica3 The end result of this process will be that the replica cluster tokens mirror those of the source cluster. 1. Start with the replica cluster shutdown. ($ sudo systemctl stop scylla-server) 2. On each node of the source cluster, run the following: HOST_IP=`grep -e '^listen_address' /etc/scylla/scylla.yaml \| awk '{ print $NF }'`* nodetool ring \| grep $HOST_IP \| awk '{print $NF ","}' \| xargs \| sed 's/,$//g' This produces a comma-separated list of tokens for that particular node... 3. Take this list of tokens and plug it into the corresponding replica node's scylla.yaml file under the initial_token: property. Now finish the normal restore procedure on the replica cluster (replacing the keyspace data w/ the back-upped data from the source cluster) 4. Start up the replica cluster, run nodetool repair, and once everything's up, you should be good to go... Good luck! On Thu, Apr 11, 2019 at 1:06 PM Saurabh Verma <saurab...@...> wrote: Hi Ryan Please send me the commands whenever possible Thanks a lot On Thu, 11 Apr 2019 at 11:29 PM, Saurabh Verma <saurab...@...> wrote: Hey Ryan It would be really great if you could guide me along these lines you mentioned above. I would be available if you need any more information. 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 23:25, Ryan Stauffer <ry...@...> wrote: Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the same token distribution as the source cluster. If you need help doing this let me know and I can send over some commands later once I get back to my computer. On Thu, Apr 11, 2019 at 10:51 AM Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- 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%2BCnsnnQUpTOL%3DoUMuM7mKJLoFnDHSZ2GghGNM9xtqbDdRsoLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Saurabh Verma Inline images Principal Engineer m: +917976984604 skype: saurabh.verma-zeotap -- 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/CAPW2RUJedHuifED30Uv9LEsqxyjOomfKHvNe_10bStb5LcJOMg%40mail.gmail.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%3DpcutXXi4WA9Rnh4kM090pxQqUGw8pzpf8GjbqjX%3DH9A%40mail.gmail.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/CAPW2RUK4edwJJyfrQumx7xFkb2tp5GgX-QTbAmv5qUQeTmEn6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855*
More
Saurabh Verma <saurab...@...> #1071 Hi Ryan The above method works successfully for JG recovery, thank you so much Ryan for the timely assistance, and sharing this crucial & fundamental information. Thanks a lot once again 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 toggle quoted message Show quoted text On Fri, 12 Apr 2019 at 02:03, Ryan Stauffer <ry...@...> wrote: For terminology, I'm going to call your 2 clusters "source" and "replica". "Source" is the Scylla cluster that you want to backup, and "replica" is the cluster that you want to copy the data to. For this to work, you need a mapping of "source" node to exactly one "replica" node. Ex: Source cluster = 3 Nodes (source1, source2, source3) Replica cluster = 3 Nodes (replica1, replica2, replica3) Where we have a mapping: source1 -> replica1 source2 -> replica2 source3 -> replica3 The end result of this process will be that the replica cluster tokens mirror those of the source cluster. 1. Start with the replica cluster shutdown. ($ sudo systemctl stop scylla-server) 2. On each node of the source cluster, run the following: HOST_IP=`grep -e '^listen_address' /etc/scylla/scylla.yaml \| awk '{ print $NF }'`* nodetool ring \| grep $HOST_IP \| awk '{print $NF ","}' \| xargs \| sed 's/,$//g' This produces a comma-separated list of tokens for that particular node... 3. Take this list of tokens and plug it into the corresponding replica node's scylla.yaml file under the initial_token: property. Now finish the normal restore procedure on the replica cluster (replacing the keyspace data w/ the back-upped data from the source cluster) 4. Start up the replica cluster, run nodetool repair, and once everything's up, you should be good to go... Good luck! On Thu, Apr 11, 2019 at 1:06 PM Saurabh Verma <saurab...@...> wrote: Hi Ryan Please send me the commands whenever possible Thanks a lot On Thu, 11 Apr 2019 at 11:29 PM, Saurabh Verma <saurab...@...> wrote: Hey Ryan It would be really great if you could guide me along these lines you mentioned above. I would be available if you need any more information. 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 23:25, Ryan Stauffer <ry...@...> wrote: Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the same token distribution as the source cluster. If you need help doing this let me know and I can send over some commands later once I get back to my computer. On Thu, Apr 11, 2019 at 10:51 AM Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- 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%2BCnsnnQUpTOL%3DoUMuM7mKJLoFnDHSZ2GghGNM9xtqbDdRsoLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Saurabh Verma Inline images Principal Engineer   m: +917976984604 skype: saurabh.verma-zeotap -- 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/CAPW2RUJedHuifED30Uv9LEsqxyjOomfKHvNe_10bStb5LcJOMg%40mail.gmail.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%3DpcutXXi4WA9Rnh4kM090pxQqUGw8pzpf8GjbqjX%3DH9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
More
Ryan Stauffer <ry...@...> #1064 For terminology, I'm going to call your 2 clusters "source" and "replica". "Source" is the Scylla cluster that you want to backup, and "replica" is the cluster that you want to copy the data to. For this to work, you need a mapping of "source" node to exactly one "replica" node. Ex: Source cluster = 3 Nodes (source1, source2, source3) Replica cluster = 3 Nodes (replica1, replica2, replica3) Where we have a mapping: source1 -> replica1 source2 -> replica2 source3 -> replica3 The end result of this process will be that the replica cluster tokens mirror those of the source cluster. 1. Start with the replica cluster shutdown. ($ sudo systemctl stop scylla-server) 2. On each node of the source cluster, run the following: HOST_IP=`grep -e '^listen_address' /etc/scylla/scylla.yaml \| awk '{ print $NF }'` nodetool ring \| grep $HOST_IP \| awk '{print $NF ","}' \| xargs \| sed 's/,$//g' This produces a comma-separated list of tokens for that particular node... 3. Take this list of tokens and plug it into the corresponding replica node's scylla.yaml file under the initial_token: property. Now finish the normal restore procedure on the replica cluster (replacing the keyspace data w/ the back-upped data from the source cluster) 4. Start up the replica cluster, run nodetool repair, and once everything's up, you should be good to go... Good luck! toggle quoted message Show quoted text On Thu, Apr 11, 2019 at 1:06 PM Saurabh Verma <saurab...@...> wrote: Hi Ryan Please send me the commands whenever possible Thanks a lot On Thu, 11 Apr 2019 at 11:29 PM, Saurabh Verma <saurab...@...> wrote: Hey Ryan It would be really great if you could guide me along these lines you mentioned above. I would be available if you need any more information. 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 23:25, Ryan Stauffer <ry...@...> wrote: Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the same token distribution as the source cluster. If you need help doing this let me know and I can send over some commands later once I get back to my computer. On Thu, Apr 11, 2019 at 10:51 AM Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- 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%2BCnsnnQUpTOL%3DoUMuM7mKJLoFnDHSZ2GghGNM9xtqbDdRsoLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Saurabh Verma Inline images Principal Engineer   m: +917976984604 skype: saurabh.verma-zeotap -- 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/CAPW2RUJedHuifED30Uv9LEsqxyjOomfKHvNe_10bStb5LcJOMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
More
Saurabh Verma <saurab...@...> #1069 Hi Ryan Please send me the commands whenever possible Thanks a lot toggle quoted message Show quoted text On Thu, 11 Apr 2019 at 11:29 PM, Saurabh Verma <saurab...@...> wrote: Hey Ryan It would be really great if you could guide me along these lines you mentioned above. I would be available if you need any more information. 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 23:25, Ryan Stauffer <ry...@...> wrote: Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the same token distribution as the source cluster. If you need help doing this let me know and I can send over some commands later once I get back to my computer. On Thu, Apr 11, 2019 at 10:51 AM Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- 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%2BCnsnnQUpTOL%3DoUMuM7mKJLoFnDHSZ2GghGNM9xtqbDdRsoLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Saurabh Verma Inline images Principal Engineer   m: +917976984604 skype: saurabh.verma-zeotap
More
Saurabh Verma <saurab...@...> #1068 Hey Ryan It would be really great if you could guide me along these lines you mentioned above. I would be available if you need any more information. 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 toggle quoted message Show quoted text On Thu, 11 Apr 2019 at 23:25, Ryan Stauffer <ry...@...> wrote: Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the same token distribution as the source cluster. If you need help doing this let me know and I can send over some commands later once I get back to my computer. On Thu, Apr 11, 2019 at 10:51 AM Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- 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%2BCnsnnQUpTOL%3DoUMuM7mKJLoFnDHSZ2GghGNM9xtqbDdRsoLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
More
Ryan Stauffer <ry...@...> #1061 Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the same token distribution as the source cluster. If you need help doing this let me know and I can send over some commands later once I get back to my computer. toggle quoted message Show quoted text On Thu, Apr 11, 2019 at 10:51 AM Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855*
More
SAURABH VERMA <saurabh...@...> #1067 Hey Ryan I backed up data on each node of “cluster1”, and then restored data on each node of “cluster2” Thanks toggle quoted message Show quoted text On Thu, 11 Apr 2019 at 11:21 PM, Ryan Stauffer <ry...@...> wrote: So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855* -- 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%3DHBZGGaeojp-VXY9uow4Opd0rhqN84b7DCeJ6xQQcm_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- Thanks & Regards, Saurabh Verma, India
More
Ryan Stauffer <ry...@...> #1060 So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? toggle quoted message Show quoted text On Thu, Apr 11, 2019 at 10:03 AM Saurabh Verma <saurab...@...> wrote: 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. -- 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/CAPW2RUJcfEffszhXiQrbzPNK1cTPNUGyKu4sQ76r3_nWjacQ7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- *Ryan Stauffer* *Founder, Enharmonic, Inc.* *enharmonic.ai* *415-684-3855*
More
Saurabh Verma <saurab...@...> #1066 Hey Ryan Point 2, I missed the question around same scylla cluster, I am moving it to a different scylla cluster the IPs are changed. Does that matter? 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 toggle quoted message Show quoted text On Thu, 11 Apr 2019 at 21:13, Saurabh Verma <saurab...@...> wrote: 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.
More
Saurabh Verma <saurab...@...> #1065 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 toggle quoted message Show quoted text 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.
More
Ryan Stauffer <ry...@...> #1056 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 toggle quoted message Show quoted text 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.
More
SAURABH VERMA <saurabh...@...> #1054 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
More

1 - 12 of 12

Previous Topic Next Topic

Home Hashtags Subgroups Calendar Terms