It will create more overhead on your cluster. Consider using something like
reaper to manage.
> On 21 Apr 2017, at 00:57, eugene miretsky wrote:
>
> In Cassandra 3.0 the default nodetool repair behaviour is incremental and
> parallel.
> Is there a downside to triggering repair from multiple
In Cassandra 3.0 the default nodetool repair behaviour is incremental and
parallel.
Is there a downside to triggering repair from multiple nodes at the same
time?
Basically, instead of scheduling a cron job on one node to run repair, I
want to schedule the job on every node (this way, I don't have
Thanks Jayesh,
Watched all of those.
Still not sure I fully get the theory behind it
Aside from the 2 failure cases I mentioned earlier, the only other way
data can become inconsistent is error when replicating the data in the
background. Does Cassandra have a retry policy for internal replica
Hi Amit,
The size recommendations are based on balancing CPU and the amount of data
stored on a node. LCS requires less disk space but generally requires much
more CPU to keep up with compaction for the same amount of data, which is
why the size recommendation is smaller. There is nothing wrong wi
>There's a system property (actually 2)Which ones?
On Wednesday, April 19, 2017 9:17 AM, Jeff Jirsa wrote:
On 2017-04-12 11:30 (-0700), Vlad wrote:
> Interesting, there is no such explicit warning for v.3
> https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddNodeT
Thanks Carlos,
In each keyspace we also have 11 MVs.
It is impossible to reduce number of tables now. Long GC Pauses take about
one minute. But why it takes so much time and how that can be fixed?
Each node in cluster has 128GB RAM, so resources are not constrained now
Thanks
2017-04-20 13:18
no, in-memory is only available in DataStax Enterprise 4.0+
-- Jacob Shadix
On Thu, Apr 20, 2017 at 3:00 AM, Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in> wrote:
> Hi All,
>
>
>
> As Datastax Cassandra version provide a in memory table. Can we achieve
> same thing in apache C
You have 4800 Tables in total? That is a lot of tables, plus MVs? or MVs
are already considered in the 60*80 account?
I would recommend to reduce the table number. Other thing is that you need
to check your log file for GC Pauses, and how long those pauses take.
You also might need to increase th
Hi,
We are using cassandra 3.10 in a 10 nodes cluster with replication = 3.
MAX_HEAP_SIZE=64GB on all nodes, G1 GC is used. We have about 60 keyspaces
with about 80 tables in each keyspace. We had to delete three tables and
two materialized views from each keyspace. It began to take more and more
Did this error persist? What was the expected outcome? Did you drop this CF
and now expect it to no longer exist?
On 12 April 2017 at 01:26, Jai Bheemsen Rao Dhanwada
wrote:
> Hello,
>
> I am seeing streaming errors while adding new nodes(in the same DC) to the
> cluster.
>
> ERROR [STREAM-IN-/x
Hi Jon,
Thanks for your guidance.
In above mentioned table i can have different scale depending on Report.
One report may have 1 rows.
Second report may have half million rows.
Third report may have 1 million rows.
Fourth report may have 10 million rows.
As this is timeseries data that was
Hi All,
As Datastax Cassandra version provide a in memory table. Can we achieve same
thing in apache Cassandra?
http://docs.datastax.com/en/archived/datastax_enterprise/4.6/datastax_enterprise/inMemory.html
Thanks & Regards,
Abhishek Kumar Maheshwari
+91- 805591 (Mobile)
Times Internet L
12 matches
Mail list logo