RE: Restoring snapshot

2018-06-13 Thread Vishal1.Sharma
On altering the Keyspace, the warning disappears. I think the warning was not 
totally wrong, just slightly inaccurate.


From: Nitan Kainth [mailto:nitankai...@gmail.com]
Sent: Wednesday, June 13, 2018 4:38 PM
To: user@cassandra.apache.org
Subject: Re: Restoring snapshot

Change RF fir k2 and then see.
Sent from my iPhone

On Jun 13, 2018, at 7:05 AM, 
mailto:vishal1.sha...@ril.com>> 
mailto:vishal1.sha...@ril.com>> wrote:
For both K1 and K2, replication factor is 2 in the new cluster(although the 
number of nodes is 1). I can understand the portion of the warning which says 
that “only 1 replica could be found” but the question is, why is it giving the 
name of keyspace K2 when I was restoring only K1(It should have given warning 
for K1).

From: Nitan Kainth [mailto:nitankai...@gmail.com]
Sent: Wednesday, June 13, 2018 4:31 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Restoring snapshot

Verify dc name and replication factor in create keyspace command in new cluster.
Sent from my iPhone

On Jun 13, 2018, at 2:40 AM, 
mailto:vishal1.sha...@ril.com>> 
mailto:vishal1.sha...@ril.com>> wrote:
Dear Community,

I took a snapshot from a node which was part of a 2 node cluster. There were 2 
keyspaces in that cluster K1 and K2. I took snapshot of K1 only. Now I create 
both keyspaces in some other cluster having only one node. When I tried to 
restore the snapshot(of keyspace K1) in that cluster using sstableloader, I got 
a warning:

“WARN  11:55:48,921 Error while computing token map for keyspace K2 with 
datacenter dc1: could not achieve replication factor 2 (found 1 replicas only), 
check your keyspace replication settings.”

Like I’ve said above, the new cluster contains only one node, therefore I can 
understand the portion of the warning telling me that ‘it only found 1 replicas 
only’, but why is it computing token map for keyspace K2 when I was restoring 
sstables of keyspace K1? Also, the same warning(regarding only K2) is displayed 
whether I try to restore snapshot of K1 or K2.  Although, I’m able to get the 
complete data, but I would appreciate if someone can explain this observations.

Cassandra version: 3.11.2

Thanks and regards,
Vishal Sharma

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."
"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."


Re: Restoring snapshot

2018-06-13 Thread Nitan Kainth
Change RF fir k2 and then see.

Sent from my iPhone

> On Jun 13, 2018, at 7:05 AM,  
>  wrote:
> 
> For both K1 and K2, replication factor is 2 in the new cluster(although the 
> number of nodes is 1). I can understand the portion of the warning which says 
> that “only 1 replica could be found” but the question is, why is it giving 
> the name of keyspace K2 when I was restoring only K1(It should have given 
> warning for K1).
>  
> From: Nitan Kainth [mailto:nitankai...@gmail.com] 
> Sent: Wednesday, June 13, 2018 4:31 PM
> To: user@cassandra.apache.org
> Subject: Re: Restoring snapshot
>  
> Verify dc name and replication factor in create keyspace command in new 
> cluster.
> 
> Sent from my iPhone
> 
> On Jun 13, 2018, at 2:40 AM,  
>  wrote:
> 
> Dear Community,
>  
> I took a snapshot from a node which was part of a 2 node cluster. There were 
> 2 keyspaces in that cluster K1 and K2. I took snapshot of K1 only. Now I 
> create both keyspaces in some other cluster having only one node. When I 
> tried to restore the snapshot(of keyspace K1) in that cluster using 
> sstableloader, I got a warning:
>  
> “WARN  11:55:48,921 Error while computing token map for keyspace K2 with 
> datacenter dc1: could not achieve replication factor 2 (found 1 replicas 
> only), check your keyspace replication settings.”
>  
> Like I’ve said above, the new cluster contains only one node, therefore I can 
> understand the portion of the warning telling me that ‘it only found 1 
> replicas only’, but why is it computing token map for keyspace K2 when I was 
> restoring sstables of keyspace K1? Also, the same warning(regarding only K2) 
> is displayed whether I try to restore snapshot of K1 or K2.  Although, I’m 
> able to get the complete data, but I would appreciate if someone can explain 
> this observations.
>  
> Cassandra version: 3.11.2
>  
> Thanks and regards,
> Vishal Sharma
> 
> "Confidentiality Warning: This message and any attachments are intended only 
> for the use of the intended recipient(s), are confidential and may be 
> privileged. If you are not the intended recipient, you are hereby notified 
> that any review, re-transmission, conversion to hard copy, copying, 
> circulation or other use of this message and any attachments is strictly 
> prohibited. If you are not the intended recipient, please notify the sender 
> immediately by return email and delete this message and any attachments from 
> your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to 
> ensure no viruses are present in this email. The company cannot accept 
> responsibility for any loss or damage arising from the use of this email or 
> attachment."
> 
> 
> "Confidentiality Warning: This message and any attachments are intended only 
> for the use of the intended recipient(s), are confidential and may be 
> privileged. If you are not the intended recipient, you are hereby notified 
> that any review, re-transmission, conversion to hard copy, copying, 
> circulation or other use of this message and any attachments is strictly 
> prohibited. If you are not the intended recipient, please notify the sender 
> immediately by return email and delete this message and any attachments from 
> your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to 
> ensure no viruses are present in this email. The company cannot accept 
> responsibility for any loss or damage arising from the use of this email or 
> attachment."


RE: Restoring snapshot

2018-06-13 Thread Vishal1.Sharma
For both K1 and K2, replication factor is 2 in the new cluster(although the 
number of nodes is 1). I can understand the portion of the warning which says 
that “only 1 replica could be found” but the question is, why is it giving the 
name of keyspace K2 when I was restoring only K1(It should have given warning 
for K1).

From: Nitan Kainth [mailto:nitankai...@gmail.com]
Sent: Wednesday, June 13, 2018 4:31 PM
To: user@cassandra.apache.org
Subject: Re: Restoring snapshot

Verify dc name and replication factor in create keyspace command in new cluster.
Sent from my iPhone

On Jun 13, 2018, at 2:40 AM, 
mailto:vishal1.sha...@ril.com>> 
mailto:vishal1.sha...@ril.com>> wrote:
Dear Community,

I took a snapshot from a node which was part of a 2 node cluster. There were 2 
keyspaces in that cluster K1 and K2. I took snapshot of K1 only. Now I create 
both keyspaces in some other cluster having only one node. When I tried to 
restore the snapshot(of keyspace K1) in that cluster using sstableloader, I got 
a warning:

“WARN  11:55:48,921 Error while computing token map for keyspace K2 with 
datacenter dc1: could not achieve replication factor 2 (found 1 replicas only), 
check your keyspace replication settings.”

Like I’ve said above, the new cluster contains only one node, therefore I can 
understand the portion of the warning telling me that ‘it only found 1 replicas 
only’, but why is it computing token map for keyspace K2 when I was restoring 
sstables of keyspace K1? Also, the same warning(regarding only K2) is displayed 
whether I try to restore snapshot of K1 or K2.  Although, I’m able to get the 
complete data, but I would appreciate if someone can explain this observations.

Cassandra version: 3.11.2

Thanks and regards,
Vishal Sharma

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."
"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."


Re: Restoring snapshot

2018-06-13 Thread Nitan Kainth
Verify dc name and replication factor in create keyspace command in new cluster.

Sent from my iPhone

> On Jun 13, 2018, at 2:40 AM,  
>  wrote:
> 
> Dear Community,
>  
> I took a snapshot from a node which was part of a 2 node cluster. There were 
> 2 keyspaces in that cluster K1 and K2. I took snapshot of K1 only. Now I 
> create both keyspaces in some other cluster having only one node. When I 
> tried to restore the snapshot(of keyspace K1) in that cluster using 
> sstableloader, I got a warning:
>  
> “WARN  11:55:48,921 Error while computing token map for keyspace K2 with 
> datacenter dc1: could not achieve replication factor 2 (found 1 replicas 
> only), check your keyspace replication settings.”
>  
> Like I’ve said above, the new cluster contains only one node, therefore I can 
> understand the portion of the warning telling me that ‘it only found 1 
> replicas only’, but why is it computing token map for keyspace K2 when I was 
> restoring sstables of keyspace K1? Also, the same warning(regarding only K2) 
> is displayed whether I try to restore snapshot of K1 or K2.  Although, I’m 
> able to get the complete data, but I would appreciate if someone can explain 
> this observations.
>  
> Cassandra version: 3.11.2
>  
> Thanks and regards,
> Vishal Sharma
> 
> "Confidentiality Warning: This message and any attachments are intended only 
> for the use of the intended recipient(s), are confidential and may be 
> privileged. If you are not the intended recipient, you are hereby notified 
> that any review, re-transmission, conversion to hard copy, copying, 
> circulation or other use of this message and any attachments is strictly 
> prohibited. If you are not the intended recipient, please notify the sender 
> immediately by return email and delete this message and any attachments from 
> your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to 
> ensure no viruses are present in this email. The company cannot accept 
> responsibility for any loss or damage arising from the use of this email or 
> attachment."


Re: Restoring snapshot

2018-06-11 Thread @Nandan@
Before restoring check version od sstables which you are using to import
data into your schema.  , as you remove and add age, due to this, already
there will be no data for that column.
now if you want that your old data should be shown here, then you have to
use proper sstable for dumping the data.

On Tue, Jun 12, 2018 at 12:58 PM, Joseph Arriola 
wrote:

>
> Hi Vishal!
>
> Did you copy the sstables into data directory?
>
> another thing is, check the id of the table that is the same as casaandra
> has in the metadata with the directory.
>
> https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/
> useCreateTableCollisionFix.html
>
>
>
>
>
> El El lun, 11 de jun. de 2018 a las 12:24 p. m., Elliott Sims <
> elli...@backblaze.com> escribió:
>
>> It's possible that it's something more subtle, but keep in mind that
>> sstables don't include the schema.  If you've made schema changes, you need
>> to apply/revert those first or C* probably doesn't know what to do with
>> those columns in the sstable.
>>
>> On Sun, Jun 10, 2018 at 11:38 PM,  wrote:
>>
>>> Dear Community,
>>>
>>>
>>>
>>> I’ll appreciate if I can get some responses to the observation below:
>>>
>>>
>>>
>>> https://stackoverflow.com/q/50763067/5701173
>>>
>>>
>>>
>>> Thanks and regards,
>>>
>>> Vishal Sharma
>>>
>>>
>>> "*Confidentiality Warning*: This message and any attachments are
>>> intended only for the use of the intended recipient(s), are confidential
>>> and may be privileged. If you are not the intended recipient, you are
>>> hereby notified that any review, re-transmission, conversion to hard copy,
>>> copying, circulation or other use of this message and any attachments is
>>> strictly prohibited. If you are not the intended recipient, please notify
>>> the sender immediately by return email and delete this message and any
>>> attachments from your system.
>>>
>>> *Virus Warning:* Although the company has taken reasonable precautions
>>> to ensure no viruses are present in this email. The company cannot accept
>>> responsibility for any loss or damage arising from the use of this email or
>>> attachment."
>>>
>>
>>


Re: Restoring snapshot

2018-06-11 Thread Joseph Arriola
Hi Vishal!

Did you copy the sstables into data directory?

another thing is, check the id of the table that is the same as casaandra
has in the metadata with the directory.

https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/useCreateTableCollisionFix.html





El El lun, 11 de jun. de 2018 a las 12:24 p. m., Elliott Sims <
elli...@backblaze.com> escribió:

> It's possible that it's something more subtle, but keep in mind that
> sstables don't include the schema.  If you've made schema changes, you need
> to apply/revert those first or C* probably doesn't know what to do with
> those columns in the sstable.
>
> On Sun, Jun 10, 2018 at 11:38 PM,  wrote:
>
>> Dear Community,
>>
>>
>>
>> I’ll appreciate if I can get some responses to the observation below:
>>
>>
>>
>> https://stackoverflow.com/q/50763067/5701173
>>
>>
>>
>> Thanks and regards,
>>
>> Vishal Sharma
>>
>>
>> "*Confidentiality Warning*: This message and any attachments are
>> intended only for the use of the intended recipient(s), are confidential
>> and may be privileged. If you are not the intended recipient, you are
>> hereby notified that any review, re-transmission, conversion to hard copy,
>> copying, circulation or other use of this message and any attachments is
>> strictly prohibited. If you are not the intended recipient, please notify
>> the sender immediately by return email and delete this message and any
>> attachments from your system.
>>
>> *Virus Warning:* Although the company has taken reasonable precautions
>> to ensure no viruses are present in this email. The company cannot accept
>> responsibility for any loss or damage arising from the use of this email or
>> attachment."
>>
>
>


Re: Restoring snapshot

2018-06-11 Thread Elliott Sims
It's possible that it's something more subtle, but keep in mind that
sstables don't include the schema.  If you've made schema changes, you need
to apply/revert those first or C* probably doesn't know what to do with
those columns in the sstable.

On Sun, Jun 10, 2018 at 11:38 PM,  wrote:

> Dear Community,
>
>
>
> I’ll appreciate if I can get some responses to the observation below:
>
>
>
> https://stackoverflow.com/q/50763067/5701173
>
>
>
> Thanks and regards,
>
> Vishal Sharma
>
>
> "*Confidentiality Warning*: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, re-transmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return email and delete this message and any attachments
> from your system.
>
> *Virus Warning:* Although the company has taken reasonable precautions to
> ensure no viruses are present in this email. The company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachment."
>