Re: Cassandra Data migration from 2.2.3 to 3.7

[Jeff Jirsa]

Roughly that approach should work, modulo copying data in/out to the right
paths, and making sure you dont overwrite any sstables with the same name.

(You dont need to refresh after the upgradesstables unless you've got 2 3.7
clusters, and you may need to refresh before the upgradesstables if the 3.7
cluster in step 3 is already running)


On Tue, Aug 1, 2017 at 3:44 PM, Harika Vangapelli -T (hvangape - AKRAYA INC
at Cisco)  wrote:

> Jeff, I tried the below steps for just 3 rows of data, It looks to be
> working. But Confirm me this is right approach.
>
> 1.   Taking snapshot (using nodetool snapshot) in the existing
> cluster (2.2 cluster)
>
> 2.   Bring the snapshot to new cluster and copy in keyspce/table
> (2.2->3.7)
>
> 3.   Nodetool upgrade sstbales on new cluster (3.7)
>
> 4.   Use noedtool refresh --   (3.7)
>
> Does this approach work?
>
>
>
> [image:
> http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png]
>
>
>
> *Harika Vangapelli*
>
> Engineer - IT
>
> hvang...@cisco.com
>
> Tel:
>
> *Cisco Systems, Inc.*
>
>
>
>
> United States
> cisco.com
>
>
>
> [image: http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
>  for
> Company Registration Information.
>
>
>
> *From:* Jeff Jirsa [mailto:jji...@gmail.com]
> *Sent:* Tuesday, August 1, 2017 3:36 PM
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra Data migration from 2.2.3 to 3.7
>
>
>
> You can't stream across versions, so you either need to use the native
> protocol (do writes with the normal INSERT operations) or you have to get
> to the right sstable version
>
>
>
> That means one of the three of these:
>
>
>
> - export to CSV (copy to/copy from, or Brian Hess' Cassandra-loader on
> github)
>
> - export to CSV and use CQLSSTableWriter to generate sstables you can bulk
> load
>
> - create a minimal cluster, load the sstables in, and run upgradesstables
> to rev the version and then stop that cluster and stream them into the new
> cluster
>
>
>
> --
>
> Jeff Jirsa
>
>
>
>
> On Aug 1, 2017, at 3:30 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at
> Cisco)  wrote:
>
> Jeff, Thanks for initial pointer. I want to add some more information to
> it.
>
>
>
> This is to migrate from one cluster (2.2 version) to 3.7 . The client who
> is in 2.2 cluster they don’t need down time.
>
>
>
> So How the data is migrated to new cluster without down time with
> different versions?
>
>
>
> Thanks,
>
> Harika
>
>
>
> 
>
>
>
> *Harika Vangapelli*
>
> Engineer - IT
>
> hvang...@cisco.com
>
> Tel:
>
> *Cisco Systems, Inc.*
>
>
>
>
> United States
> cisco.com
>
>
>
> Think before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
>  for
> Company Registration Information.
>
>
>
> *From:* Jeff Jirsa [mailto:jji...@gmail.com ]
> *Sent:* Tuesday, August 1, 2017 2:48 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra Data migration from 2.2.3 to 3.7
>
>
>
> If you upgrade in place:
>
>
>
> Stop each node one at a time
>
> Swap binaries
>
> Start each node
>
> Run upgradesstables when all nodes are bounced
>
>
>
> If you want to take data from 2.2 and put it into a 3.x cluster, you'll
> need to run upgradesstables on it offline somehow (like clone that 2.2
> cluster/schema and run it offline with 3.x upgradesstables), then
> sstableloader it into place
>
>
>
> Note that 3.7 is probably not the version you want - 3.11 is probably much
> more stable and solves some serious bugs (or 3.0.14 if you don't need
> features from 3.7 ). The one exception to this would be if you're using a
> 3.7 lts branch (like instaclustr had at one point - and may still have).
>
>
>
>
> --
>
> Jeff Jirsa
>
>
>
>
> On Aug 1, 2017, at 2:24 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at
> Cisco)  wrote:
>
> Please help me understand data migration path from 2.2.3 to 3.7.
>
>
>
> 1.   Tried to take snapshot and load the snapshot using
> sstableloader; but it is throwing Streaming Exception.
>
> Please advise.
>
>
>
> Thanks,
>
> Harika
>
>
>
>

Re: Cassandra Data migration from 2.2.3 to 3.7

[Jon Haddad]

Just curious, why go to 3.7?  3.11 has hundreds of bug fixes that 3.7 doesn’t 
and will continue to receive fixes.

> On Aug 1, 2017, at 3:44 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco)  wrote:
> 
> Jeff, I tried the below steps for just 3 rows of data, It looks to be 
> working. But Confirm me this is right approach.
> 1.   Taking snapshot (using nodetool snapshot) in the existing cluster 
> (2.2 cluster)
> 2.   Bring the snapshot to new cluster and copy in keyspce/table 
> (2.2->3.7)
> 3.   Nodetool upgrade sstbales on new cluster (3.7)
> 4.   Use noedtool refresh --   (3.7)
> Does this approach work?
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com 
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com  
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended recipient. Any review, use, distribution or disclosure by 
> others is strictly prohibited. If you are not the intended recipient (or 
> authorized to receive for the recipient), please contact the sender by reply 
> email and delete all copies of this message.
> Please click here 
>  for 
> Company Registration Information.
>  
> From: Jeff Jirsa [mailto:jji...@gmail.com] 
> Sent: Tuesday, August 1, 2017 3:36 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
>  
> You can't stream across versions, so you either need to use the native 
> protocol (do writes with the normal INSERT operations) or you have to get to 
> the right sstable version
>  
> That means one of the three of these: 
>  
> - export to CSV (copy to/copy from, or Brian Hess' Cassandra-loader on github)
> - export to CSV and use CQLSSTableWriter to generate sstables you can bulk 
> load
> - create a minimal cluster, load the sstables in, and run upgradesstables to 
> rev the version and then stop that cluster and stream them into the new 
> cluster
> 
> 
> -- 
> Jeff Jirsa
>  
> 
> On Aug 1, 2017, at 3:30 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco) > wrote:
> 
> Jeff, Thanks for initial pointer. I want to add some more information to it.
>  
> This is to migrate from one cluster (2.2 version) to 3.7 . The client who is 
> in 2.2 cluster they don’t need down time.
>  
> So How the data is migrated to new cluster without down time with different 
> versions?
>  
> Thanks,
> Harika
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com 
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com  
>  
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended recipient. Any review, use, distribution or disclosure by 
> others is strictly prohibited. If you are not the intended recipient (or 
> authorized to receive for the recipient), please contact the sender by reply 
> email and delete all copies of this message.
> Please click here 
>  for 
> Company Registration Information.
>  
> From: Jeff Jirsa [mailto:jji...@gmail.com ] 
> Sent: Tuesday, August 1, 2017 2:48 PM
> To: user@cassandra.apache.org 
> Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
>  
> If you upgrade in place:
>  
> Stop each node one at a time
> Swap binaries
> Start each node
> Run upgradesstables when all nodes are bounced
>  
> If you want to take data from 2.2 and put it into a 3.x cluster, you'll need 
> to run upgradesstables on it offline somehow (like clone that 2.2 
> cluster/schema and run it offline with 3.x upgradesstables), then 
> sstableloader it into place
>  
> Note that 3.7 is probably not the version you want - 3.11 is probably much 
> more stable and solves some serious bugs (or 3.0.14 if you don't need 
> features from 3.7 ). The one exception to this would be if you're using a 3.7 
> lts branch (like instaclustr had at one point - and may still have). 
>  
> 
> -- 
> Jeff Jirsa
>  
> 
> On Aug 1, 2017, at 2:24 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco) > wrote:
> 
> Please help me understand data migration path from 2.2.3 to 3.7.
>  
> 1.   Tried to take snapshot and load the snapshot using sstableloader; 
> but it is throwing Streaming Exception.
> Please advise.
>  
> Thanks,
> Harika
>  
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com 
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com  
>  
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended 

Re: Cassandra failed to start when trying to move to multi-node

[Lucas Alvarez]

Hi Guys,

Sincerely I can't believe the poor log description cassandra has. I'm
really annoyed of it.  I'll be very grateful if someone can tell me what
I'm doing wrong.These are the system.log

DEBUG [MigrationStage:1] 2017-08-01 19:05:32,316 MigrationManager.java:559
- Gossiping my schema version 86afa796-d883-3932-aa73-6b017cef0d19
INFO  [main] 2017-08-01 19:05:32,321 CassandraDaemon.java:689 - Waiting for
gossip to settle before accepting client requests...
INFO  [StorageServiceShutdownHook] 2017-08-01 19:05:37,139
Gossiper.java:1500 - Announcing shutdown
DEBUG [StorageServiceShutdownHook] 2017-08-01 19:05:37,145
StorageService.java:2084 - Node /10.29.32.141 state shutdown, token
[-1123972637282389021, -1128298667864406016, -1171617287587824921,
-1215843289747623916, -1237937532710359480, -1345880644695771882,
-1349885349161311671, -1362145484087002762, -1440959214603770852,
-1512070380045849364, -15562558941953290, -1591004378839652311,
-1694940268226046775, -1864518086513990320, -1896042425201339911,
-1994292418109908520, -2003588030553215254, -2043188303385004470,
-2055903703812384971, -2109331550938473986, -2122939046043806143,
-2143152627026803975, -2185565512541871884, -2415386864109182287,
-2430846502581329454, -2470138951219298346, -2492107031933585878,
-2587773444277550225, -2637579687313334505, -2735172492291292485,
-2827584735019087585, -290431611581338475, -3071603742423637708,
-3095470153210902324, -3131544462929190835, -3135674413617886725,
-3150440806943715941, -3178396675409442894, -318497997504024006,
-3201019541810055282, -3258165039073354815, -3261780972325383197,
-3278940591444654530, -3345266284193299339, -3422326361881279245,
-3487586668918769359, -3718794461538622174, -3801631139742567423,
-3843670578950890216, -3898829803832756540, -3935407498402044613,
-4251851692152635043, -4415945217017668767, -4452225071746131035,
-453312989101992613, -4839451892769253701, -4973005214058730250,
-5053121942845257846, -5125285697334830036, -5221264363601323946,
-5262268255024886151, -5308112226622381003, -5340754668904733684,
-5355765644228414304, -5459951554417868743, -5469791190167080668,
-5527706442799493981, -559480126390194624, -5689197963457359544,
-5710004903145545370, -5710062375033871504, -58307316983765202,
-5855281765529735420, -5919381082238614185, -5942611986193812207,
-5967329331479625927, -6043267858375974505, -6087175412435843974,
-6094541573537230749, -6246887755069175918, -6280211006509663763,
-6315076974978783216, -6496176019797645480, -6647004211063512670,
-6880104183008897702, -6945857193189828758, -6999768735261214984,
-7158840023093635895, -7269185753501792655, -7323201607900629439,
-744809024780577313, -7649650761736084417, -7666412950471098887,
-7750430497460298689, -7756210366708927339, -7772309298440548768,
-7794625355497929618, -7814051108149202384, -7945368179631418161,
-7975820666185853623, -8121484732018222381, -815626395204134758,
-8188734319418852782, -8203139661838238638, -834506117667975763,
-8362422499286771777, -8426979645752596060, -8451255929616297204,
-8470204464683881322, -8478587847171371050, -8547549412865634230,
-8548035921147149972, -855526750771608018, -8688793174634127296,
-890032833656406846, -893190419569470168, -9051215292531123931,
-962827266461007569, -992770120048953975, 1157249903676150022,
1216324593091504942, 1312337923119780731, 1349448566688352375,
1369333885339882116, 1422138074730275595, 1444912153175734656,
1618884083254618295, 1650714171726687105, 1766820778600528592,
1827094503419133606, 1844353071833421671, 1846691290460555677,
1871123789771135573, 2001059651014325643, 205551488443047106,
2225900781613463715, 2235953372648717266, 224705851767608836,
22797385381515442, 2307318513561489489, 2515829181112560290,
2553364043852683755, 2651896619582180223, 2661175220973492595,
2708080120032361248, 2727648522528026014, 2731295026313523765,
2775444638430797813, 2838818340986386519, 2877910534714789924,
2924407888116243723, 3020357673071192148, 3097435134130345321,
3147758686908008129, 3243420657610994074, 3250920343344209253,
3277866773734103071, 3360948993344871080, 33715193809407712,
3399299329564806585, 3401626455895202317, 3502398306068447099,
3767304883331801067, 3774426950675899295, 3808180916121124450,
3808458941356873995, 3826803268498853584, 3864485432255730689,
3868616704793677452, 4112215614749137106, 4114694661896302657,
4186640741391099326, 4258288096841274725, 4261221646546445003,
426415935612277396, 4300203411069681689, 4465225791823721468,
4466468504386485494, 4506167237972845399, 4575257705631561911,
4700766086930901605, 4701868928277061736, 4794410065338314971,
4830352262513059936, 4941595487977074494, 4978148461725532210,
4988027989860100317, 4992483162624735456, 500527084630227,
5043195386233719595, 5070811491271577796, 5142888664069214922,
5262763252301787651, 5303355533952014988, 5357724928405091434,
5475138402136431120, 554552177710648199, 5676029841178228460,
5736545750793928834, 5740683747595890694, 

Re: Cassandra failed to start when trying to move to multi-node

[Nitan Kainth]

try with bootstrap true in that case. Start the seed node first. I think it
should work.

On Tue, Aug 1, 2017 at 4:54 PM, Lucas Alvarez  wrote:

> I'm sorry the ip address of this node in the configuration was
> 10.29.32.141.
> num_tokens is set to 256
> initial_token is commented.
>
> The server has been just installed.
> Thanks for your help
>
> 2017-08-01 17:01 GMT-03:00 Nitan Kainth :
>
>> If it is blank, you can use bootstrap: true.
>>
>> What is num_tokens and initial token values?
>>
>> On Aug 1, 2017, at 2:42 PM, Lucas Alvarez  wrote:
>>
>> Hi, I'm trying to configure Cassandra as a cluster with two nodes. When
>> trying to simple start the first node just changing this parameters:
>>
>> listen_address: 10.29.30.2
>> seed_provider: 10.29.30.2
>> rpc_address: 10.29.30.2
>> auto_bootstrap: false
>>
>> I'm getting this message and then cassandra stop loading:
>>
>> INFO  [main] 2017-08-01 15:10:13,474 StorageService.java:2087 - Node /
>> 10.29.32.141 state jump to NORMAL
>> DEBUG [main] 2017-08-01 15:10:13,479 StorageService.java:1336 - NORMAL
>> INFO  [main] 2017-08-01 15:10:13,486 CassandraDaemon.java:689 - Waiting
>> for gossip to settle before accepting client requests...
>> DEBUG [PendingRangeCalculator:1] 2017-08-01 15:10:13,491
>> PendingRangeCalculatorService.java:66 - finished calculation for 3
>> keyspaces in 8ms
>> INFO  [StorageServiceShutdownHook] 2017-08-01 15:10:17,848
>> Gossiper.java:1500 - Announcing shutdown
>>
>> I have googled to death and I'm not able to find any solution nor
>> explanation.
>> Any help will be appreciated.
>>
>> Thanks in advance.
>>
>> Lucas
>>
>>
>>
>

RE: Cassandra Data migration from 2.2.3 to 3.7

[Harika Vangapelli -T (hvangape - AKRAYA INC at Cisco)]

Jeff, I tried the below steps for just 3 rows of data, It looks to be working. 
But Confirm me this is right approach.

1.   Taking snapshot (using nodetool snapshot) in the existing cluster (2.2 
cluster)

2.   Bring the snapshot to new cluster and copy in keyspce/table (2.2->3.7)

3.   Nodetool upgrade sstbales on new cluster (3.7)

4.   Use noedtool refresh --   (3.7)
Does this approach work?

[http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png]



Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.


From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, August 1, 2017 3:36 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Data migration from 2.2.3 to 3.7

You can't stream across versions, so you either need to use the native protocol 
(do writes with the normal INSERT operations) or you have to get to the right 
sstable version

That means one of the three of these:

- export to CSV (copy to/copy from, or Brian Hess' Cassandra-loader on github)
- export to CSV and use CQLSSTableWriter to generate sstables you can bulk load
- create a minimal cluster, load the sstables in, and run upgradesstables to 
rev the version and then stop that cluster and stream them into the new cluster


--
Jeff Jirsa


On Aug 1, 2017, at 3:30 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
Cisco) > wrote:
Jeff, Thanks for initial pointer. I want to add some more information to it.

This is to migrate from one cluster (2.2 version) to 3.7 . The client who is in 
2.2 cluster they don’t need down time.

So How the data is migrated to new cluster without down time with different 
versions?

Thanks,
Harika





Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.


From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, August 1, 2017 2:48 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Data migration from 2.2.3 to 3.7

If you upgrade in place:

Stop each node one at a time
Swap binaries
Start each node
Run upgradesstables when all nodes are bounced

If you want to take data from 2.2 and put it into a 3.x cluster, you'll need to 
run upgradesstables on it offline somehow (like clone that 2.2 cluster/schema 
and run it offline with 3.x upgradesstables), then sstableloader it into place

Note that 3.7 is probably not the version you want - 3.11 is probably much more 
stable and solves some serious bugs (or 3.0.14 if you don't need features from 
3.7 ). The one exception to this would be if you're using a 3.7 lts branch 
(like instaclustr had at one point - and may still have).


--
Jeff Jirsa


On Aug 1, 2017, at 2:24 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
Cisco) > wrote:
Please help me understand data migration path from 2.2.3 to 3.7.


1.   Tried to take snapshot and load the snapshot using sstableloader; but 
it is throwing Streaming Exception.
Please advise.

Thanks,
Harika






Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.

Re: Cassandra Data migration from 2.2.3 to 3.7

[Jeff Jirsa]

You can't stream across versions, so you either need to use the native protocol 
(do writes with the normal INSERT operations) or you have to get to the right 
sstable version

That means one of the three of these: 

- export to CSV (copy to/copy from, or Brian Hess' Cassandra-loader on github)
- export to CSV and use CQLSSTableWriter to generate sstables you can bulk load
- create a minimal cluster, load the sstables in, and run upgradesstables to 
rev the version and then stop that cluster and stream them into the new cluster


-- 
Jeff Jirsa


> On Aug 1, 2017, at 3:30 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco)  wrote:
> 
> Jeff, Thanks for initial pointer. I want to add some more information to it.
>  
> This is to migrate from one cluster (2.2 version) to 3.7 . The client who is 
> in 2.2 cluster they don’t need down time.
>  
> So How the data is migrated to new cluster without down time with different 
> versions?
>  
> Thanks,
> Harika
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended recipient. Any review, use, distribution or disclosure by 
> others is strictly prohibited. If you are not the intended recipient (or 
> authorized to receive for the recipient), please contact the sender by reply 
> email and delete all copies of this message.
> Please click here for Company Registration Information.
>  
> From: Jeff Jirsa [mailto:jji...@gmail.com] 
> Sent: Tuesday, August 1, 2017 2:48 PM
> To: user@cassandra.apache.org
> Subject: Re: Cassandra Data migration from 2.2.3 to 3.7
>  
> If you upgrade in place:
>  
> Stop each node one at a time
> Swap binaries
> Start each node
> Run upgradesstables when all nodes are bounced
>  
> If you want to take data from 2.2 and put it into a 3.x cluster, you'll need 
> to run upgradesstables on it offline somehow (like clone that 2.2 
> cluster/schema and run it offline with 3.x upgradesstables), then 
> sstableloader it into place
>  
> Note that 3.7 is probably not the version you want - 3.11 is probably much 
> more stable and solves some serious bugs (or 3.0.14 if you don't need 
> features from 3.7 ). The one exception to this would be if you're using a 3.7 
> lts branch (like instaclustr had at one point - and may still have). 
>  
> 
> -- 
> Jeff Jirsa
>  
> 
> On Aug 1, 2017, at 2:24 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco)  wrote:
> 
> Please help me understand data migration path from 2.2.3 to 3.7.
>  
> 1.   Tried to take snapshot and load the snapshot using sstableloader; 
> but it is throwing Streaming Exception.
> Please advise.
>  
> Thanks,
> Harika
>  
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com
>  
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended recipient. Any review, use, distribution or disclosure by 
> others is strictly prohibited. If you are not the intended recipient (or 
> authorized to receive for the recipient), please contact the sender by reply 
> email and delete all copies of this message.
> Please click here for Company Registration Information.
>  

RE: Cassandra Data migration from 2.2.3 to 3.7

[Harika Vangapelli -T (hvangape - AKRAYA INC at Cisco)]

Jeff, Thanks for initial pointer. I want to add some more information to it.

This is to migrate from one cluster (2.2 version) to 3.7 . The client who is in 
2.2 cluster they don’t need down time.

So How the data is migrated to new cluster without down time with different 
versions?

Thanks,
Harika

[http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png]



Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.


From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Tuesday, August 1, 2017 2:48 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Data migration from 2.2.3 to 3.7

If you upgrade in place:

Stop each node one at a time
Swap binaries
Start each node
Run upgradesstables when all nodes are bounced

If you want to take data from 2.2 and put it into a 3.x cluster, you'll need to 
run upgradesstables on it offline somehow (like clone that 2.2 cluster/schema 
and run it offline with 3.x upgradesstables), then sstableloader it into place

Note that 3.7 is probably not the version you want - 3.11 is probably much more 
stable and solves some serious bugs (or 3.0.14 if you don't need features from 
3.7 ). The one exception to this would be if you're using a 3.7 lts branch 
(like instaclustr had at one point - and may still have).


--
Jeff Jirsa


On Aug 1, 2017, at 2:24 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
Cisco) > wrote:
Please help me understand data migration path from 2.2.3 to 3.7.


1.   Tried to take snapshot and load the snapshot using sstableloader; but 
it is throwing Streaming Exception.
Please advise.

Thanks,
Harika






Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


Think before you print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.

Re: Cassandra isn't compacting old files

[Sotirios Delimanolis]

There aren't any ERROR logs for failure to load these files and they do get 
compacted away. I'll try to plug some DEBUG logs in a custom Cassandra 
version.On Tuesday, August 1, 2017, 12:13:09 PM PDT, Jeff Jirsa 
 wrote:

I don't have time to dive deep into the code of your version, but it may be ( 
https://issues.apache.org/jira/browse/CASSANDRA-13620 ) , or it may be 
something else.
I wouldn't expect compaction to touch them if they're invalid. The handle may 
be a leftover from trying to load them. 


On Tue, Aug 1, 2017 at 10:01 AM, Sotirios Delimanolis 
 wrote:

@Jeff, why does compaction clear them and why does Cassandra keep a handle to 
them? Shouldn't they be ignored entirely? Is there an error log I can enable to 
detect them?
@kurt, there are no such logs for any of these tables. We have a custom log in 
our build of Cassandra that does shows that compactions are happening for that 
table but only ever include the files from July.
On Tuesday, August 1, 2017, 12:55:53 AM PDT, kurt greaves 
 wrote:

Seeing as there aren't even 100 SSTables in L2, LCS should be gradually trying 
to compact L3 with L2. You could search the logs for "Adding high-level (L3)" 
to check if this is happening. ​

Re: Is it possible to delete system_auth keyspace.

[kurt greaves]

You should be able to create it yourself prior to enabling auth without
issues. alternatively you could just add an extra node with auth on, or
switch one node to have auth on then change th RF.

Re: Cassandra failed to start when trying to move to multi-node

[Lucas Alvarez]

I'm sorry the ip address of this node in the configuration was 10.29.32.141
.
num_tokens is set to 256
initial_token is commented.

The server has been just installed.
Thanks for your help

2017-08-01 17:01 GMT-03:00 Nitan Kainth :

> If it is blank, you can use bootstrap: true.
>
> What is num_tokens and initial token values?
>
> On Aug 1, 2017, at 2:42 PM, Lucas Alvarez  wrote:
>
> Hi, I'm trying to configure Cassandra as a cluster with two nodes. When
> trying to simple start the first node just changing this parameters:
>
> listen_address: 10.29.30.2
> seed_provider: 10.29.30.2
> rpc_address: 10.29.30.2
> auto_bootstrap: false
>
> I'm getting this message and then cassandra stop loading:
>
> INFO  [main] 2017-08-01 15:10:13,474 StorageService.java:2087 - Node /
> 10.29.32.141 state jump to NORMAL
> DEBUG [main] 2017-08-01 15:10:13,479 StorageService.java:1336 - NORMAL
> INFO  [main] 2017-08-01 15:10:13,486 CassandraDaemon.java:689 - Waiting
> for gossip to settle before accepting client requests...
> DEBUG [PendingRangeCalculator:1] 2017-08-01 15:10:13,491
> PendingRangeCalculatorService.java:66 - finished calculation for 3
> keyspaces in 8ms
> INFO  [StorageServiceShutdownHook] 2017-08-01 15:10:17,848
> Gossiper.java:1500 - Announcing shutdown
>
> I have googled to death and I'm not able to find any solution nor
> explanation.
> Any help will be appreciated.
>
> Thanks in advance.
>
> Lucas
>
>
>

Re: Cassandra Data migration from 2.2.3 to 3.7

[Jeff Jirsa]

If you upgrade in place:

Stop each node one at a time
Swap binaries
Start each node
Run upgradesstables when all nodes are bounced

If you want to take data from 2.2 and put it into a 3.x cluster, you'll need to 
run upgradesstables on it offline somehow (like clone that 2.2 cluster/schema 
and run it offline with 3.x upgradesstables), then sstableloader it into place

Note that 3.7 is probably not the version you want - 3.11 is probably much more 
stable and solves some serious bugs (or 3.0.14 if you don't need features from 
3.7 ). The one exception to this would be if you're using a 3.7 lts branch 
(like instaclustr had at one point - and may still have). 


-- 
Jeff Jirsa


> On Aug 1, 2017, at 2:24 PM, Harika Vangapelli -T (hvangape - AKRAYA INC at 
> Cisco)  wrote:
> 
> Please help me understand data migration path from 2.2.3 to 3.7.
>  
> 1.   Tried to take snapshot and load the snapshot using sstableloader; 
> but it is throwing Streaming Exception.
> Please advise.
>  
> Thanks,
> Harika
>  
>  
> 
>  
> Harika Vangapelli
> Engineer - IT
> hvang...@cisco.com
> Tel:
> Cisco Systems, Inc.
> 
> 
> 
> United States
> cisco.com
> Think before you print.
> This email may contain confidential and privileged material for the sole use 
> of the intended recipient. Any review, use, distribution or disclosure by 
> others is strictly prohibited. If you are not the intended recipient (or 
> authorized to receive for the recipient), please contact the sender by reply 
> email and delete all copies of this message.
> Please click here for Company Registration Information.
>  

Cassandra Data migration from 2.2.3 to 3.7

[Harika Vangapelli -T (hvangape - AKRAYA INC at Cisco)]

Please help me understand data migration path from 2.2.3 to 3.7.


1.   Tried to take snapshot and load the snapshot using sstableloader; but 
it is throwing Streaming Exception.
Please advise.

Thanks,
Harika


[http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_gradient.png]



Harika Vangapelli
Engineer - IT
hvang...@cisco.com
Tel:

Cisco Systems, Inc.



United States
cisco.com


[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think before you 
print.

This email may contain confidential and privileged material for the sole use of 
the intended recipient. Any review, use, distribution or disclosure by others 
is strictly prohibited. If you are not the intended recipient (or authorized to 
receive for the recipient), please contact the sender by reply email and delete 
all copies of this message.
Please click 
here for 
Company Registration Information.

Re: Cassandra failed to start when trying to move to multi-node

[Nitan Kainth]

If it is blank, you can use bootstrap: true.

What is num_tokens and initial token values?

> On Aug 1, 2017, at 2:42 PM, Lucas Alvarez  wrote:
> 
> Hi, I'm trying to configure Cassandra as a cluster with two nodes. When 
> trying to simple start the first node just changing this parameters:
> 
> listen_address: 10.29.30.2
> seed_provider: 10.29.30.2
> rpc_address: 10.29.30.2
> auto_bootstrap: false
> 
> I'm getting this message and then cassandra stop loading:
> 
> INFO  [main] 2017-08-01 15:10:13,474 StorageService.java:2087 - Node 
> /10.29.32.141  state jump to NORMAL
> DEBUG [main] 2017-08-01 15:10:13,479 StorageService.java:1336 - NORMAL
> INFO  [main] 2017-08-01 15:10:13,486 CassandraDaemon.java:689 - Waiting for 
> gossip to settle before accepting client requests...
> DEBUG [PendingRangeCalculator:1] 2017-08-01 15:10:13,491 
> PendingRangeCalculatorService.java:66 - finished calculation for 3 keyspaces 
> in 8ms
> INFO  [StorageServiceShutdownHook] 2017-08-01 15:10:17,848 Gossiper.java:1500 
> - Announcing shutdown
> 
> I have googled to death and I'm not able to find any solution nor explanation.
> Any help will be appreciated.
> 
> Thanks in advance.
> 
> Lucas

Re: Cassandra failed to start when trying to move to multi-node

[Michael Shuler]

10.29.30.2 does not appear to be the IP of the node, if you got "Node
/10.29.32.141 state jump to NORMAL" as the first logged state change
from StorageService. Usually this first entry is the node's local IP
address. Later in the log, you'll see OutboundTcpConnection handshakes
and state change from the other nodes, once they start gossiping.

-- 
Michael

On 08/01/2017 02:42 PM, Lucas Alvarez wrote:
> Hi, I'm trying to configure Cassandra as a cluster with two nodes. When
> trying to simple start the first node just changing this parameters:
> 
> listen_address: 10.29.30.2
> seed_provider: 10.29.30.2
> rpc_address: 10.29.30.2
> auto_bootstrap: false
> 
> I'm getting this message and then cassandra stop loading:
> 
> INFO  [main] 2017-08-01 15:10:13,474 StorageService.java:2087 - Node
> /10.29.32.141  state jump to NORMAL
> DEBUG [main] 2017-08-01 15:10:13,479 StorageService.java:1336 - NORMAL
> INFO  [main] 2017-08-01 15:10:13,486 CassandraDaemon.java:689 - Waiting
> for gossip to settle before accepting client requests...
> DEBUG [PendingRangeCalculator:1] 2017-08-01 15:10:13,491
> PendingRangeCalculatorService.java:66 - finished calculation for 3
> keyspaces in 8ms
> INFO  [StorageServiceShutdownHook] 2017-08-01 15:10:17,848
> Gossiper.java:1500 - Announcing shutdown
> 
> I have googled to death and I'm not able to find any solution nor
> explanation.
> Any help will be appreciated.
> 
> Thanks in advance.
> 
> Lucas


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Cassandra failed to start when trying to move to multi-node

[Lucas Alvarez]

Hi, I'm trying to configure Cassandra as a cluster with two nodes. When
trying to simple start the first node just changing this parameters:

listen_address: 10.29.30.2
seed_provider: 10.29.30.2
rpc_address: 10.29.30.2
auto_bootstrap: false

I'm getting this message and then cassandra stop loading:

INFO  [main] 2017-08-01 15:10:13,474 StorageService.java:2087 - Node /
10.29.32.141 state jump to NORMAL
DEBUG [main] 2017-08-01 15:10:13,479 StorageService.java:1336 - NORMAL
INFO  [main] 2017-08-01 15:10:13,486 CassandraDaemon.java:689 - Waiting for
gossip to settle before accepting client requests...
DEBUG [PendingRangeCalculator:1] 2017-08-01 15:10:13,491
PendingRangeCalculatorService.java:66 - finished calculation for 3
keyspaces in 8ms
INFO  [StorageServiceShutdownHook] 2017-08-01 15:10:17,848
Gossiper.java:1500 - Announcing shutdown

I have googled to death and I'm not able to find any solution nor
explanation.
Any help will be appreciated.

Thanks in advance.

Lucas

Re: cfs and cfs_archive

[Jeff Jirsa]

On 2017-08-01 07:49 (-0700), Greg Lloyd  wrote: 
> We have a cluster that we are moving to two entire new datacenters to
> change the node sizes and move off our current nodes. There is the cfs and
> cfs_archive keyspaces which are of replication factor 1 in our us-east-1
> datacenter only.
> 
> I didn't see any mention in any docs when adding our other datacenters
> about increasing the rf for these keyspaces.
> 
> Is it safe to replicate this to the all the new datacenters? Should this
> exist in only one datacenter? We are not using the cassandra filesystem for
> anything currently.
> 

Was this a DSE cluster, or was it previously using cassandra filesystem? The 
guidance is probably best coming from Datastax, as it's not an open source 
feature.



-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: NGCC 2017 Announcment

[Jeff Jirsa]

Thanks Instaclustr!


On Tue, Aug 1, 2017 at 11:16 AM, Gary Dusbabek  wrote:

> We are pleased to announce the 2017 Next Generation Cassandra Conference
> (NGCC) that will be held on Tuesday September 26th at the Geekdom Event
> Center in San Antonio, Texas. This one day conference is targed toward
> Apache Cassandra developers and large-scale cluster operators, but is
> opened to anyone interested in the Cassandra community.
>
> Presentation topics will cover the current state of project development as
> well as future development. The organizers have alotted a number of opened
> slots for presentations. So, if you would like to participate by giving a
> presentation, please complete this questionnaire [1]. Presentations will be
> selected by a committee formed from the Apache Cassandra PMC.
>
> For more information, or to register, please go to our Eventbrite page[2],
> where you can find a schedule of events as well as accomodation information.
>
> If you have any questions, please reach out to myself or Eric Evans (
> john.eric.ev...@gmail.com).
>
> A special thanks to Instaclustr, who are sponsoring this event.
>
> Thanks,
>
> Gary.
>
> Please Note: Apache Cassandra is a trademark of the Apache Software
> Organization, which has neither endorsed or organized this event.
>
> https://docs.google.com/forms/d/e/1FAIpQLSf2spZG_
> 5gf68Jf4m70SoZGNj2meEpUGUY9Ac08lGstE3N7VQ/viewform?usp=sf_link
> https://www.eventbrite.com/e/next-generation-cassandra-
> conference-ngcc-tickets-36160855091
>

Re: Cassandra isn't compacting old files

[Jeff Jirsa]

I don't have time to dive deep into the code of your version, but it may be
( https://issues.apache.org/jira/browse/CASSANDRA-13620 ) , or it may be
something else.

I wouldn't expect compaction to touch them if they're invalid. The handle
may be a leftover from trying to load them.



On Tue, Aug 1, 2017 at 10:01 AM, Sotirios Delimanolis <
sotodel...@yahoo.com.invalid> wrote:

> @Jeff, why does compaction clear them and why does Cassandra keep a handle
> to them? Shouldn't they be ignored entirely? Is there an error log I can
> enable to detect them?
>
> @kurt, there are no such logs for any of these tables. We have a custom
> log in our build of Cassandra that does shows that compactions are
> happening for that table but only ever include the files from July.
>
> On Tuesday, August 1, 2017, 12:55:53 AM PDT, kurt greaves <
> k...@instaclustr.com> wrote:
>
>
> Seeing as there aren't even 100 SSTables in L2, LCS should be gradually
> trying to compact L3 with L2. You could search the logs for "Adding
> high-level (L3)" to check if this is happening. ​
>

NGCC 2017 Announcment

[Gary Dusbabek]

We are pleased to announce the 2017 Next Generation Cassandra Conference
(NGCC) that will be held on Tuesday September 26th at the Geekdom Event
Center in San Antonio, Texas. This one day conference is targed toward
Apache Cassandra developers and large-scale cluster operators, but is
opened to anyone interested in the Cassandra community.

Presentation topics will cover the current state of project development as
well as future development. The organizers have alotted a number of opened
slots for presentations. So, if you would like to participate by giving a
presentation, please complete this questionnaire [1]. Presentations will be
selected by a committee formed from the Apache Cassandra PMC.

For more information, or to register, please go to our Eventbrite page[2],
where you can find a schedule of events as well as accomodation information.

If you have any questions, please reach out to myself or Eric Evans (
john.eric.ev...@gmail.com).

A special thanks to Instaclustr, who are sponsoring this event.

Thanks,

Gary.

Please Note: Apache Cassandra is a trademark of the Apache Software
Organization, which has neither endorsed or organized this event.

https://docs.google.com/forms/d/e/1FAIpQLSf2spZG_5gf68Jf4m70SoZGNj2meEpUGUY9Ac08lGstE3N7VQ/viewform?usp=sf_link
https://www.eventbrite.com/e/next-generation-cassandra-conference-ngcc-tickets-36160855091

Trouble restoring with sstableloader

[Jim Miller]

Hi all,

I've been running into the following issue while trying to restore a C*
database via sstableloader:

Could not retrieve endpoint ranges:
org.apache.thrift.transport.TTransportException: Frame size (352518912)
larger than max length (15728640)!
java.lang.RuntimeException: Could not retrieve endpoint ranges:
at
org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:283)
at
org.apache.cassandra.io.sstable.SSTableLoader.stream(SSTableLoader.java:144)
at org.apache.cassandra.tools.BulkLoader.main(BulkLoader.java:95)
Caused by: org.apache.thrift.transport.TTransportException: Frame size
(352518912) larger than max length (15728640)!
at
org.apache.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:137)
at
org.apache.thrift.transport.TFramedTransport.read(TFramedTransport.java:101)
at
org.apache.thrift.transport.TTransport.readAll(TTransport.java:84)
at
org.apache.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:362)
at
org.apache.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:284)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:191)
at
org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:69)
at
org.apache.cassandra.thrift.Cassandra$Client.recv_describe_partitioner(Cassandra.java:1327)
at
org.apache.cassandra.thrift.Cassandra$Client.describe_partitioner(Cassandra.java:1315)
at
org.apache.cassandra.tools.BulkLoader$ExternalClient.init(BulkLoader.java:256)
... 2 more

This seems odd since the frame size thrift is asking for is over 336 MB.

This is happening using Cassandra 2.0.12 | Thrift protocol 19.39.0

Any advice?

Thanks!

--Jim

Re: Cassandra isn't compacting old files

[Sotirios Delimanolis]

@Jeff, why does compaction clear them and why does Cassandra keep a handle to 
them? Shouldn't they be ignored entirely? Is there an error log I can enable to 
detect them?
@kurt, there are no such logs for any of these tables. We have a custom log in 
our build of Cassandra that does shows that compactions are happening for that 
table but only ever include the files from July.
On Tuesday, August 1, 2017, 12:55:53 AM PDT, kurt greaves 
 wrote:

Seeing as there aren't even 100 SSTables in L2, LCS should be gradually trying 
to compact L3 with L2. You could search the logs for "Adding high-level (L3)" 
to check if this is happening. ​

Re: Is it possible to delete system_auth keyspace.

[Pranay akula]

Thanks Jeff for your reply, yes i agree with what you said but the problem
is --- i am trying this in lower environment which had this system_auth
already created so when i alter keyspace to network topology and enabling
authentication its working great and easy  but in prod we don't have
system_auth to alter yet which i am expecting may cause trouble, so to
level the field and start form scratch i am trying to get rid of
system_auth which i couldn't.

I am trying to enable authentication with zero downtime  i am doing it on
apache 2.1

http://cassandra.apache.org/doc/latest/operating/security.html#authentication

Thanks
Pranay.

On Tue, Aug 1, 2017 at 12:50 PM, Jeff Jirsa  wrote:

> It'll be created on startup if it doesn't exist (that doesn't mean it'll
> be used, but it'll be created)
>
> --
> Jeff Jirsa
>
>
> > On Aug 1, 2017, at 9:43 AM, Pranay akula 
> wrote:
> >
> > I am trying to enable authentication in different scenarios, trying to
> delete system_auth keyspace and disabled authentication  removed keyspace
> from data directory and restart the cassandra service.
> >
> > Still when cassandra comes up i am seeing system_auth keyspace created
> again. Is there any way to delete it.
> >
> > I have tried dropping keyspace as well, which it's not allowing me to do.
> >
> >
> >
> >
> >
> >
> > Thanks
> > Pranay.
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

Re: Issue with cassandra 3.1X and Python 2.7.13 in Debian 8.8

[Michael Shuler]

/usr/local/bin/python is your own source install of python. Using the
system python with cqlsh should "just work" on Jessie with `apt-get
install python'

-- 
Michael

On 08/01/2017 01:05 AM, K Natarajan, Karthik (Nokia - IN/Bangalore) wrote:
> Hi,
> When I Install Cassandra 3.11X and Python 2.7.X in Debian 8.8, the Cqlsh
> does not start. I get the following error.
>  
> debian@vm-184:/opt/apache-cassandra-3.10/bin$ ./cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH. You might
> try "pip install cassandra-driver".
> Python: /usr/local/bin/python Module load path:
> ['/opt/apache-cassandra-3.10/bin/../lib/six-1.7.3-py2.py3-none-any.zip',
> '/opt/apache-cassandra-3.10/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/opt/apache-cassandra-3.10/bin/../lib/cassandra-driver-internal-only-3.7.0.post0-2481531.zip/cassandra-driver-3.7.0.post0-2481531',
> '/opt/apache-cassandra-3.10/bin', '/usr/local/lib/python27.zip',
> '/usr/local/lib/python2.7', '/usr/local/lib/python2.7/plat-linux2',
> '/usr/local/lib/python2.7/lib-tk', '/usr/local/lib/python2.7/lib-old',
> '/usr/local/lib/python2.7/lib-dynload',
> '/usr/local/lib/python2.7/site-packages']
> Error: can't decompress data; zlib not available
>  
> Have to do some workaround like this to get it working.
> ./configure --with-zlib --with-ssl
> sudo apt-get install libssl-dev
> sudo apt-get install zlib1g-dev
>  
> I feel there is an issue with default installation of Cassandra
> integration with python.
>  
> Regards
> Karthik
>  
>  
>  


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Is it possible to delete system_auth keyspace.

[Jeff Jirsa]

It'll be created on startup if it doesn't exist (that doesn't mean it'll be 
used, but it'll be created)

-- 
Jeff Jirsa


> On Aug 1, 2017, at 9:43 AM, Pranay akula  wrote:
> 
> I am trying to enable authentication in different scenarios, trying to  
> delete system_auth keyspace and disabled authentication  removed keyspace 
> from data directory and restart the cassandra service.
> 
> Still when cassandra comes up i am seeing system_auth keyspace created again. 
> Is there any way to delete it.
> 
> I have tried dropping keyspace as well, which it's not allowing me to do.
> 
> 
> 
> 
> 
> 
> Thanks
> Pranay.

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Is it possible to delete system_auth keyspace.

[Pranay akula]

I am trying to enable authentication in different scenarios, trying to
 delete system_auth keyspace and disabled authentication  removed keyspace
from data directory and restart the cassandra service.

Still when cassandra comes up i am seeing system_auth keyspace created
again. Is there any way to delete it.

I have tried dropping keyspace as well, which it's not allowing me to do.






Thanks
Pranay.

cfs and cfs_archive

[Greg Lloyd]

We have a cluster that we are moving to two entire new datacenters to
change the node sizes and move off our current nodes. There is the cfs and
cfs_archive keyspaces which are of replication factor 1 in our us-east-1
datacenter only.

I didn't see any mention in any docs when adding our other datacenters
about increasing the rf for these keyspaces.

Is it safe to replicate this to the all the new datacenters? Should this
exist in only one datacenter? We are not using the cassandra filesystem for
anything currently.

Thanks
GReg

Re: How to minimize side effects induced by tombstones when using deletion?

[kurt greaves]

> Also, if we repaired once successfully, will the next repair process take
a more reasonable time?
Depends on if there was a lot of inconsistent data to repair in the first
place. Also full repairs or incremental?

Repairs are complicated and tricky to get working efficiently. If you're
using vnodes you are probably going to have a really hard time.
​
Another avenue is to tune your compaction strategy. The strategies are
generally pretty bad at purging tombstones if you delete old data, so that
should be avoided where possible, however there are some properties you can
tune that might help. See tombstone_compaction_threshold. Note that in 2.1
it's not that effective as it only does singe SSTable compaction.

Re: Cassandra isn't compacting old files

[kurt greaves]

Seeing as there aren't even 100 SSTables in L2, LCS should be gradually
trying to compact L3 with L2. You could search the logs for "Adding
high-level (L3)" to check if this is happening. ​

Re: How to minimize side effects induced by tombstones when using deletion?

[Jing Meng]

Thanks, we'll try delete range of rows as it seems to fit our scenario.
One more question, as you mentioned "repair often" - and we have seen that
several times, the official doc, representations, blogs, etc.

But when we repair a column family sized to terabytes on a cluster with ~30
nodes, it takes almost a week long, and like, always ends with some
unexpected failure.
Are we missing something here, or is it reasonable at this magnitude? Also,
if we repaired once successfully, will the next repair process take a more
reasonable time?




2017-08-01 14:08 GMT+08:00 Jeff Jirsa :

> Delete using as few tombstones as possible (deleting the whole partition
> is better than deleting a row; deleting a range of rows is better than
> deleting many rows in a range).
>
> Repair often and lower gc_grace_seconds so the tombstones can be collected
> more frequently
>
>
> --
> Jeff Jirsa
>
>
> On Jul 31, 2017, at 11:02 PM, Jing Meng  wrote:
>
> Hi there.
>
>
> We have a keyspace containing tons of records, and deletions are used as
> enforced by its business logic.
>
> As the data accumulates, we are suffering from performance penalty due to
> tombstones, still confusing about what could be done to minimize the harm,
> or shall we avoid any deletions and adapt our code?
>
> FYI, if it’s concerned, we are using C* 2.1.18.
>
>
> Thanks for your urgent replying.
>
>
>

Re: How to minimize side effects induced by tombstones when using deletion?

[Jeff Jirsa]

Delete using as few tombstones as possible (deleting the whole partition is 
better than deleting a row; deleting a range of rows is better than deleting 
many rows in a range).

Repair often and lower gc_grace_seconds so the tombstones can be collected more 
frequently


-- 
Jeff Jirsa


> On Jul 31, 2017, at 11:02 PM, Jing Meng  wrote:
> 
> Hi there.
> 
> 
> 
> We have a keyspace containing tons of records, and deletions are used as 
> enforced by its business logic.
> 
> 
> As the data accumulates, we are suffering from performance penalty due to 
> tombstones, still confusing about what could be done to minimize the harm, or 
> shall we avoid any deletions and adapt our code?
> 
> 
> FYI, if it’s concerned, we are using C* 2.1.18.
> 
> 
> 
> Thanks for your urgent replying.
> 
> 
> 

Issue with cassandra 3.1X and Python 2.7.13 in Debian 8.8

[K Natarajan, Karthik (Nokia - IN/Bangalore)]

Hi,
When I Install Cassandra 3.11X and Python 2.7.X in Debian 8.8, the Cqlsh does 
not start. I get the following error.

debian@vm-184:/opt/apache-cassandra-3.10/bin$ ./cqlsh
Python Cassandra driver not installed, or not on PYTHONPATH. You might try "pip 
install cassandra-driver".
Python: /usr/local/bin/python Module load path: 
['/opt/apache-cassandra-3.10/bin/../lib/six-1.7.3-py2.py3-none-any.zip', 
'/opt/apache-cassandra-3.10/bin/../lib/futures-2.1.6-py2.py3-none-any.zip', 
'/opt/apache-cassandra-3.10/bin/../lib/cassandra-driver-internal-only-3.7.0.post0-2481531.zip/cassandra-driver-3.7.0.post0-2481531',
 '/opt/apache-cassandra-3.10/bin', '/usr/local/lib/python27.zip', 
'/usr/local/lib/python2.7', '/usr/local/lib/python2.7/plat-linux2', 
'/usr/local/lib/python2.7/lib-tk', '/usr/local/lib/python2.7/lib-old', 
'/usr/local/lib/python2.7/lib-dynload', 
'/usr/local/lib/python2.7/site-packages']
Error: can't decompress data; zlib not available

Have to do some workaround like this to get it working.

./configure --with-zlib --with-ssl
sudo apt-get install libssl-dev
sudo apt-get install zlib1g-dev

I feel there is an issue with default installation of Cassandra integration 
with python.

Regards
Karthik

How to minimize side effects induced by tombstones when using deletion?

[Jing Meng]

Hi there.


We have a keyspace containing tons of records, and deletions are used as
enforced by its business logic.

As the data accumulates, we are suffering from performance penalty due to
tombstones, still confusing about what could be done to minimize the harm,
or shall we avoid any deletions and adapt our code?

FYI, if it’s concerned, we are using C* 2.1.18.


Thanks for your urgent replying.