example, P30 disks are capped at 200MB/s.
>
> Do I need to copy anything from system*
>
>
> No, system tables are local to a node. Only ever copy the application
> keyspaces. Cheers!
>
--
*Thanks & Regards,*
*Ankit Gadhiya*
happening on new cluster2.
>
> Michael
>
> On 2/6/20 8:09 AM, Ankit Gadhiya wrote:
> > Hi Folks,
> >
> > I recently migrated Cassandra keyspace data from one Azure cluster (3
> > Nodes) to another (3 nodes different region) using simple sstable copy.
> &
need to copy anything from system*
Anything wrt statistics/cache ?
Your time and responses on this are much appreciated.
Thanks & Regards,
Ankit
--
*Thanks & Regards,*
*Ankit Gadhiya*
on whether data for same keyspace/table names can be merged
between A and B. So 2 cases - 1. If merge is not an issue - I guess DSBulk
or SSTableloader would be an option? 2. If merge is an issue - I am
guessing without app code change - this wont be possible ,right?
*Thanks & Regards,*
*Ankit Gad
have fresh data.
>
>
>
>
> On Fri, Jan 17, 2020, 6:59 PM Ankit Gadhiya
> wrote:
>
>> Thanks but there’s no DSE License.
>> Wondering how sstableloader will help as some oh the Keyspace and tables
>> names are same. Also how do i sync few system keyspaces.
&g
st, use copy command or sstableloader to
>>> merge data. If data volume it too big, consider spark or a custom java
>>> program
>>>
>>>
>>> Regards,
>>>
>>> Nitan
>>>
>>> Cell: 510 449 9629
>>>
>>> On Ja
Any leads on this ?
— Ankit
On Thu, Jan 16, 2020 at 8:51 PM Ankit Gadhiya
wrote:
> Hi Arvinder,
>
> Thanks for your response.
>
> Yes - Cluster B already has some data. Tables/KS names are identical ; for
> data - I still haven't got the clarity if it has identical data or no
tables?
>
>
> -Arvi
>
> On Thu, Jan 16, 2020, 5:27 PM Ankit Gadhiya
> wrote:
>
>> Hello Group,
>>
>> I have a requirement in one of the production systems where I need to be
>> able to migrate entire dataset from Cluster A (Azure Region A) to Cluster B
>
to hear ideas from all of you based on your experiences.
Cassandra Version - Cassandra 3.0.13 on both sides.
Total Data size - Cluster A: 70 GB, Cluster B: 15 GB
*Thanks & Regards,*
*Ankit Gadhiya*
Thanks Paul. This is interesting.
So, anything I need to do after cp? - nodetool repair?
Also I am assuming I need to be doing this exercise on all the nodes of the
cluster - right?
Any suggestion to automate this or do it just from a single node?
— Ankit Gadhiya
On Tue, Oct 29, 2019 at 11:21
Thanks folks for your responses but still haven't found concrete solution
for this.
*Thanks & Regards,*
*Ankit Gadhiya*
On Tue, Oct 29, 2019 at 2:15 PM Sergio Bilello
wrote:
> Rolling bounce = Rolling repair per node? Would not it be easy to be
> scheduled with Cassandra Reaper?
&g
Thanks Paul.
Copy SSTable - How? Using SSTableLoader or some other mechanism.
*Thanks & Regards,*
*Ankit Gadhiya*
On Tue, Oct 29, 2019 at 11:36 AM Paul Carlucci
wrote:
> Copy the schema from your source keyspace to your new target keyspace,
> nodetool snapshot on your source keys
Thanks Alex. So How do I copy SSTables from 1.0 to 2.0? (Same SSTableLoader
or any other approach?)
Also since I've multi-node cluster - I'll have to do this on every single
node - is there any tool or better way to execute this just from a single
node?
*Thanks & Regards,*
*Ankit Gad
consuming, also being a multi-node cluster (6+6 in each DC) - it wouldn't
be very feasible to do this manually on all the nodes for multiple tables
part of that keyspace. Was wondering if we have any other creative way to
suffice this requirement.
Appreciate your time on this.
*Thanks & Regards,*
*A
14 matches
Mail list logo
