Hi Kant,
I reached out to Datastax with this very question a few months ago, here's the
response I received:
"Great to hear that you enjoyed yourself last year, we surely enjoyed having
you and the other community folks! In regards to the actual summit, we will
not be holding the Cassandra Su
Hi all,
Running Cassandra 3.9 on 5 node cluster (c4.2xlarge machines).
We have loaded quite huge 350M rows table. Also there are some other read
and write operations happening *on other small tables*, but the load is
very little, cpu is normally less than 10%, network traffic from and to
nodes is
Hi Varun,
can you elaborate a bit more? I have seen a schema change being pushed, but
that was just the first restart. After that, everything has been smooth so
far (including several schema changes, all of them verified via "describe").
Thanks!
Stefano
On Sat, May 20, 2017 at 2:10 AM, Varun Gup
It's better wait for 3.0.14
https://issues.apache.org/jira/browse/CASSANDRA/fixforversion/12340362/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
Cheers.
On 05/20/2017 11:31 AM, Stefano Ortolani wrote:
> Hi Varun,
>
> can you elaborate a bit more? I have seen a schem
If you're on AWS you can use Netflix Priam
> On 17 May 2017, at 18:40, Abhishek Gupta wrote:
>
> Hi Zaidi,
>
> We use Chef for the configuration management of our 14 node cluster.
>
> You can have a look at Chef or maybe some other config management tools too
> like Ansible and Puppet.
>
>
Thank you all for your kind advises.
On 20 May 2017 at 18:41, Cogumelos Maravilha
wrote:
> It's better wait for 3.0.14
>
> https://issues.apache.org/jira/browse/CASSANDRA/fixforversion/12340362/?
> selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>
> Cheers.
>
>
> On 05/
One issue that will be encountered with this data model is the unbounded
partition growth. Partition will continue to grow indefinitely over time
and there will be a risk to hit the limit of 2 billions columns per
partition.
Consider a composite partition key.
Thanks,
Gedeon
On Wed, May 17, 201
If the nodetool status shows DN, then you will need to tell the cluster to
remove the memory of that node by running removenode. If that doesn't work,
you may run assassinate - the ultimate command to shutdown the node.
Thanks,
Gedeon
On Tue, May 16, 2017 at 12:01 PM, Mark Furlong
wrote:
> I ha