RE: [EXTERNAL] Lot of hints piling up

d good too. Issue here is, this causing replication lag across the datacenters. On Mon, Oct 23, 2017 at 10:23 AM, Mohapatra, Kishore mailto:kishore.mohapa...@nuance.com>> wrote: Do you see any error in the cassandra log ? Check compactionstats ? Also check the OS level log messages to se

RE: [EXTERNAL]

consistency of ONE or by bumping up read_repair_chance? We have tried from command line with ONE but that times out. On 2017-10-23 10:18, "Mohapatra, Kishore" wrote: > What is your RF for the keyspace and how many nodes are there in each DC ? > > Did you force a Read Repair

RE: [EXTERNAL] Lot of hints piling up

Do you see any error in the cassandra log ? Check compactionstats ? Also check the OS level log messages to see if you are getting hardware level error messages. Thanks Kishore Mohapatra Principal Operations DBA Seattle, WA Ph : 425-691-6417 (cell) Email : kishore.mohapa...@nuance.com

RE: [EXTERNAL]

What is your RF for the keyspace and how many nodes are there in each DC ? Did you force a Read Repair to see, if you are getting the data or getting an error ? Thanks Kishore Mohapatra Principal Operations DBA Seattle, WA Email : kishore.mohapa...@nuance.com -Original Message- From:

RE: [EXTERNAL] Re: Increasing VNodes

ice is easiest solution without a lot of effort. Repairs are hard. Chris On Wed, Oct 4, 2017 at 11:48 AM, Jeff Jirsa mailto:jji...@gmail.com>> wrote: You don't need to change the number of vnodes, you can manually select CONTAINED token subranges and pass in -st and -et (just try

Increasing VNodes

Hi, We are having a lot of problems in repair process. We use sub range repair. But most of the time, some ranges fails with streaming error or some other kind of error. So wondering if it will help if we increase the no. of VNodes from 256 (default) to 512. But increasing the VNodes wil

RE: [EXTERNAL] Cassandra copy command is giving OverflowError

Try this. COPY keyspace1.table1 TO '/tmp/table1.csv' WITH PAGETIMEOUT=40 AND PAGESIZE=20; Thanks Kishore Mohapatra Principal Operations DBA Seattle, WA Email : kishore.mohapa...@nuance.com From: AI Rumman [mailto:rumman...@gmail.com] Sent: Thursday, Septemb

RE: [EXTERNAL] Re: Cassandra repair process in Low Bandwidth Network

to limit repair so that sessions don't always hit all 3 dcs - for exactly, you could do a repair between DC1 and DC2 using -dc, then do a repair of DC1 and DC3 using -dc - it's a lot more coordination required, but likely helps cut down on the traffic over your VPN link. On

Cassandra repair process in Low Bandwidth Network

Hi, we have a cassandra cluster with 7 nodes each in 3 datacenters. We are using C* 2.1.15.4 version. Network bandwidth between DC1 and DC2 is very good (10Gbit/s) and a dedicated one. However network pipe between DC1 and DC3 and between DC2 and DC3 is very poor and has only 100 MBit/s an