Hi,
I have a column family with compact storage setting:
CREATE TABLE course_book_catalogue (
key text,
"actVersion" int,
"addonResources" text,
"assessmentOpnrEnabled" boolean,
"attachmentId" text,
version int,
PRIMARY KEY ((key))
) WITH COMPACT STORAGE AND...
I have a need to add
Hi,
I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did not
run 'nodetool upgradesstables' at all. Per my confirmation afterwards,
everything is fine. But according to documentation at
https://support.datastax.com/hc/en-us/articles/208040036-Nodetool-upgradesstables-FAQ.
I need t
;>
> > >> 256 was chosen because the original vnode allocation algorithm was
> > random
> > >> and fewer than 256 could lead to unbalanced nodes
> > >>
> > >> In 3.0 there’s a less naive algorithm to ensure more balanced
> > >> di
ion algorithm was random
> and fewer than 256 could lead to unbalanced nodes
>
> In 3.0 there’s a less naive algorithm to ensure more balanced
> distribution, and there 16 or 32 is probably preferable
>
>
> --
> Jeff Jirsa
>
>
> > On Oct 9, 2017, at 7:38
Hi,
the documentation says that '...The recommended initial value for
num_tokens is 256...' and this is what we did with our cluster which is
running Cassandra Community 2.0.9, has 3 physical nodes with replication
factor 3 for all keyspaces, each with 256 vnodes, each physical node has
about 96 G
thian - Love your data
> >
> > rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
> > *linkedin.com/in/carlosjuzarterolo
> > <http://linkedin.com/in/carlosjuzarterolo>*
> > Mobile: +351 918 918 100
> > www.pythian.com
> >
> > On Thu, Ma
Hi,
due to internal infrastructure changes, we have to replace all nodes with
new nodes. All the existing nodes are running Cassandra Community version
2.0.9. I was thinking may be this is also an opportunity for us to upgrade
to Cassandra Community version 2.1.14. I hope I am not asking a crazy
q
