Hi All,
First, let me apologize for the long message. Repair service is driving me
insane. :)
We are running Cassandra version *2.1.11.908* in 3 data centers. While
running nodetool repair we are receiving the following error:
[2015-11-20 00:25:24,803] Repair session
2ed2f930-8f1d-11e5-a498-4
If the fields are null, COPY TO should just be generating "{field1: null,
field2: null}".
Would you mind opening a ticket here with steps to reproduce:
https://issues.apache.org/jira/browse/CASSANDRA
On Thu, Nov 19, 2015 at 1:05 AM, Vova Shelgunov wrote:
> Hi all,
>
> I have a trouble with copy
unsubscribe.
> On Nov 19, 2015, at 3:58 PM, Antoine Bonavita wrote:
>
> Sebastian,
>
> I took into account your suggestion and set max_sstable_age_days to 1.
>
> I left the TTL at 432000 and the gc_grace_seconds at 172800. So, I expect
> SSTable older than 7 days to get deleted. Am I right ?
Sebastian,
I took into account your suggestion and set max_sstable_age_days to 1.
I left the TTL at 432000 and the gc_grace_seconds at 172800. So, I
expect SSTable older than 7 days to get deleted. Am I right ?
I did not change dclocal_read_repair_chance because I have only one DC
at this po
On Thu, Nov 19, 2015 at 1:13 AM, Enrico Sola
wrote:
> Hi, I'm new to Cassandra and I've recently upgraded to 3.0.0 on Ubuntu
> Linux 14.04 LTS, through apt-get upgrade not manual installation, after the
> update all was fine so I could access to my keyspaces using cqlsh but I
> can't access to Ca
unsubscribe
CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution of any kind is strictly
prohibited. If you
Chandra,
I feel that you are trying to implement time series data pattern using
secondary index and one column per row. I think a much better solution would be
to partition data based on some logical row key ..if thats not availabke it may
be hour/day + a bucket id (too prevent hot spots).. Yo
Hello,
We would like to migrate one keyspace from a 6-node cluster to a 3-node one.
Since an individual node does not contain all data, this means that we
should run the sstableloader 6 times, one for each node of our cluster.
To be precise, do "nodetool flush " then run sstableloader -d <3
targ
Have you read the DataStax documentation?
http://docs.datastax.com/en/cassandra/2.0/cassandra/operations/ops_snapshot_restore_new_cluster.html
From: Romain Hardouin [mailto:romainh...@yahoo.fr]
Sent: Wednesday, November 18, 2015 3:59 PM
To: user@cassandra.apache.org
Subject: Re: Strategy tools fo
Hi Chandra,
I will comment on some points. Someone else can take remaining ones:
1. Secondary Index are only useful when data returned by the index query is in
hundreds. Fetching large data using secondary index would be very slow.
Secondary indexes dont scale well.
2.token query should be
As far as I know, docs is quite inconsistent on the matter.
Based on some research here and on IRC, recent versions of Cassandra do no
require anything specific when migrating to incremental repairs but the the
-inc switch even on LCS.
Any confirmation on the matter is more than welcome.
Regards,
11 matches
Mail list logo