Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Nandakishore Tokala
s have similar token ranges. > > Regard’s > Dhanunjaya Tokala > > On Mon, Sep 9, 2019 at 6:25 PM Nandakishore Tokala < > nandakishore.tok...@gmail.com> wrote: > >> @dhanunjayatok...@gmail.com NO, we did not >> remove those nodes and it is not exactly same missin

Re: After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Nandakishore Tokala
it really 3.1 or 3.11.0 ? > > > On Mon, Sep 9, 2019 at 10:51 AM Nandakishore Tokala < > nandakishore.tok...@gmail.com> wrote: > >> Hi All, >> >> we are running apache Cassandra 3.1.0 on AWS in multi-region nearly >> around 200 nodes. >> after

After restarting Cassandra , some of nodes are missing in nodetool status

2019-09-09 Thread Nandakishore Tokala
Hi All, we are running apache Cassandra 3.1.0 on AWS in multi-region nearly around 200 nodes. after restarting each node I am seeing some of the nodes are missing from the nodetool status (not UN or DN they are completely missing). after couple of restarts, I am seeing them back. Please help me

Re: Node tool status is not showing all the nodes on sum of the nodes in the cluster

2019-08-09 Thread Nandakishore Tokala
( TOKENS: not present ) why we will see this issue Thanks Nanda On Sun, Jul 14, 2019 at 11:59 PM Nandakishore Tokala < nandakishore.tok...@gmail.com> wrote: > HI All > > I am having 2 que's > > first one: > My cluster is a 200 node cluster and we recently joined 4

Node tool status is not showing all the nodes on sum of the nodes in the cluster

2019-07-14 Thread Nandakishore Tokala
HI All I am having 2 que's first one: My cluster is a 200 node cluster and we recently joined 4 Datacenters to existing 48 node cluster. on some of the nodes, Nodetool status is reporting 197, 198 (which varies from 198 to 202), Can anyone faced the same issue? Second one: what represents Token

Re: Cassandra tools are missing

2019-06-24 Thread Nandakishore Tokala
regards, > Michael > > On 6/24/19 10:04 PM, Nandakishore Tokala wrote: > > HI , > > > > we installed cassandra-3.11.0 on centos -7 and i see only below tools, > > sstableloader sstablescrubsstableupgrade sstableutil > > sstableverify > > > > &

Cassandra tools are missing

2019-06-24 Thread Nandakishore Tokala
HI , we installed cassandra-3.11.0 on centos -7 and i see only below tools, sstableloader sstablescrubsstableupgrade sstableutil sstableverify i am missing lot of other tools , Can any one help me to get other tools -- Thanks & Regards, Nanda Kishore

Ideal duration for max_hint_window_in_ms

2019-05-24 Thread Nandakishore Tokala
HI All, what is the impact of increasing the duration of the max_hint_window_in_ms, as we are seeing nodes are going down and some times we are not bringing them up in 3 hour's and during the repair, we are seeing a lot of streaming data, due to the node is down. so we are planning to increase th

Merging two cluster's in to one without any downtime

2019-03-25 Thread Nandakishore Tokala
Please let me know the best practices to combine 2 different cluster's into one without having any downtime. Thanks & Regards, Nanda Kishore

Migrating from DSE5.1.2 to Opensource cassandra

2018-12-04 Thread Nandakishore Tokala
HI All, we are migrating from DSE to open source Cassandra. if anyone has recently migrated, Can you please share their experience, steps you followed and challenges you guys faced. we want to migrate to the same computable version in open source, can you give us version number(even with the mino

Re: Schema version mismatch

2018-06-07 Thread Nandakishore Tokala
hen repeat the process for each remaining node that has the incorrect schema. On Thu, Jun 7, 2018 at 4:54 PM, Nandakishore Tokala < nandakishore.tok...@gmail.com> wrote: > Thanks Justin > > On Thu, Jun 7, 2018 at 4:27 PM, Justin Cameron > wrote: > >> You may run in

Re: Schema version mismatch

2018-06-07 Thread Nandakishore Tokala
king schema changes > in advance. If you need to make dynamic changes then you could check the > version to make sure that the previous change has applied before applying > the next one. > > AFAIK the only way to resolve schema mismatch is a rolling restart > > On Fri,

Schema version mismatch

2018-06-07 Thread Nandakishore Tokala
what is the schema version in Cassandra and for what are all the changes schema version is changed? why do we see schema version mismatch other than upgrades time? Can we solve the schema version mismatch without restart the Cassandra nodes -- Thanks & Regards, Nanda Kishore

Re: Repair fails for unknown reason

2018-01-03 Thread Nandakishore Tokala
hi Hannu, I think some of the repairs are hanging there. please restart all the nodes in the cluster and start the repair Thanks Nanda On Wed, Jan 3, 2018 at 9:35 AM, Hannu Kröger wrote: > Additional notes: > > 1) If I run the repair just on those tables, it works fine > 2) Those tables are