Re: upgrade 2.1 to 3.0

2018-08-21 Thread kooljava2
We found the solution for our High read volume bytes with help of DSE, we made following change $ lvchange -r 16 Following parameter in cassandra.yaml:- disk_access_mode: mmap_index_only Thank you. On Monday, 13 August 2018, 10:39:28 GMT-7, kooljava2 wrote: We did run "nodetool

Re: upgrade 2.1 to 3.0

2018-08-13 Thread kooljava2
We did run "nodetool upgradesstables" on all nodes. The C* version is 3.0.15 Thank you. On Saturday, 11 August 2018, 21:47:52 GMT-7, Elliott Sims wrote: Might be a silly question, but did you run "nodetool upgradesstables" and convert to the 3.0 format?  Also, which 3.0?  Newest, or a

Re: upgrade 2.1 to 3.0

2018-08-11 Thread Elliott Sims
Might be a silly question, but did you run "nodetool upgradesstables" and convert to the 3.0 format? Also, which 3.0? Newest, or an earlier 3.0.x? On Fri, Aug 10, 2018 at 3:05 PM, kooljava2 wrote: > Hello, > > We recently upgrade C* from 2.1 to 3.0. After the upgrade we are seeing > increase i

upgrade 2.1 to 3.0

2018-08-10 Thread kooljava2
Hello, We recently upgrade C* from 2.1 to 3.0. After the upgrade we are seeing increase in the  total read bytes and read ops on the EBS volumes. It almost doubled on all the nodes.  The number of writes are same. Thank you.