Re: disable reads from node till hints are fully synced

Hi, If you are using datastax java driver, I think this might work. http://docs.datastax.com/en/latest-java-driver-api/com/datastax/driver/core/policies/WhiteListPolicy.html On Sep 11, 2017 2:28 AM, "Jeff Jirsa" wrote: > There's not - you can disable native/binary to make it

Re: Secondary Index

Thanks for the reply vladimir but we can't upgrade c* binary that soon as we have a quick requirement for the use case I said in my first mail. So just wanted to know the difference between the 2 queries I asked in my last mail 1. select * from ks1.cf1 where status=1; 2. select * from ks1.cf1

Re: Disk full during new node bootstrap

Yes .. same number of tokens... 256 On Sat, Feb 4, 2017 at 11:56 AM, Jonathan Haddad wrote: > Are you using the same number of tokens on the new node as the old ones? > > On Fri, Feb 3, 2017 at 8:31 PM techpyaasa . wrote: > >> Hi, >> >> We are using c*

Re: Cannot set TTL in COPY command

You mean to say instead of *COPY keyspace1.columnFamily1 FROM 'dump_data.csv' WITH TTL = '7200';*use *COPY keyspace1.columnFamily1 FROM 'dump_data.csv' WITH DEFAULT_TIME_TO_LIVE = '7200';* I tried this way too, but again exception thrown saying "*Unrecognized COPY FROM options:

Re: Difference in token range count

Hi Eric, Thanks for the reply... RF=3 for all DCs... On Fri, Sep 30, 2016 at 9:57 PM, Eric Stevens wrote: > What is your replication factor in this DC? > > On Fri, Sep 30, 2016 at 8:08 AM techpyaasa . wrote: > >> Hi , >> >> We have c*-2.0.17 with 3

Re: New node block in autobootstrap

palive* and/or network/firewall settings. > > 2016-09-27 15:29 GMT-03:00 laxmikanth sadula <laxmikanth...@gmail.com>: > >> Hi paul, >> >> Thanks for the reply... >> >> I'm getting following streaming exceptions during nodetool rebuild in >> c*-2.0.17 &g

Re: New node block in autobootstrap

> https://docs.datastax.com/en/cassandra/2.0/cassandra/troubleshooting/ > trblshootIdleFirewall.html > > 2016-09-27 14:07 GMT-03:00 laxmikanth sadula <laxmikanth...@gmail.com>: > >> @Paulo Motta >> >> Even we are facing Streaming timeout exceptions

Re: New node block in autobootstrap

@Paulo Motta Even we are facing Streaming timeout exceptions during 'nodetool rebuild' , I set streaming_socket_timeout_in_ms to 8640 (24 hours) as suggested in datastax blog - https://support.datastax.com/hc/en-us/articles/206502913-

Re: How long/how many days 'nodetool gossipinfo' will have decommissioned nodes info

Thank you @Jaoquin and @DuyHai On Mon, Sep 26, 2016 at 10:00 PM, DuyHai Doan wrote: > I've read from some that the gossip info will stay > around for 72h before being removed. > > On Mon, Sep 26, 2016 at 6:19 PM, Joaquin Casares < > joaq...@thelastpickle.com> wrote: > >>

Nodetool rebuild exception on c*-2.0.17

Hi, We have c* 2.0.17 cluster with 2 DCs - DC1, DC2. We tried to add new data center DC3 and ran "nodetool rebuild 'DC1'" and we faced below exception on few nodes after some data got streamed to new nodes in new data center DC3. *Exception in thread "main" java.lang.RuntimeException: Error

Nodetool rebuild exception

Hi, We have c* 2.0.17 cluster with 2 DCs - DC1, DC2. We tried to add new data center DC3 and ran "nodetool rebuild 'DC1'" and we faced below exception on few nodes after some data got streamed to new nodes in new data center DC3. *Exception in thread "main" java.lang.RuntimeException: Error

Re: Throughout of hints delivery

ctivity? > > Matija > > -- > > *Matija Gobec* > *Co-Founder & Senior Consultant* > www.smartcat.io > > > > *Data <https://www.smartcat.io/expertise/> --> Knowledge > <https://www.smartcat.io/blog/> --> Power <https://www.smartcat.io

Throughout of hints delivery

Hi, Is there any way to monitor hints delivery throughout/performance/issue delivering hints? We have 2 DC c* cluster with 2.0.17 with RF=3 setup. Due to inter DC connectivity issues/some other issues hints shoot upto GBs/node. So I would like to monitor hints throughput/pin point the reason

Is to ok restart DECOMMISION

I started decommssioned a node in our cassandra cluster. But its taking too long time (more than 12 hrs) , so I would like to restart(stop/kill the node & restart 'node decommission' again).. Does killing node/stopping decommission and restarting decommission will cause any issues to cluster?

Re: New data center to an existing cassandra cluster

new nodes are building >> So it is always advised to use LOCAL_QUORUM instead of QUORUM and >> LOCAL_ONE instead of ONE >> >> On 27 August 2016 at 09:45, laxmikanth sadula <laxmikanth...@gmail.com> >> wrote: >> >>> Hi, >>> >>>

New data center to an existing cassandra cluster

Hi, I'm going to add a new data center DC3 to an existing cassandra cluster which has already 2 data centers DC1 , DC2. The thing I'm worried of is about tables in one keyspace which has QUORUM reads and NOT LOCAL_QUORUM. So while adding a new data centers with auto_bootstrap:false and 'nodetool