Hey Jonathan,
Thanks for your reply.
i created schema structure in this manner
CREATE SCHEMA schemaname WITH replication = { 'class' : 'SimpleStrategy',
'replication_factor' : 1 };
and table according to requirement.
I didn't used node structure.
So will it be the reason for performance?
And
Hi all,
I notice that descanter 1.1.1doesn’t support User defined types (as far as I
can see). Is it just a matter of importing a template or will we need to wait
for full 2.1 support in descanter ?
Andy
The University of Dundee is a registered Scottish Charity, No: SC015096
Hi Andrew,
DevCenter has a complete CQL parser inside which helps with the offline
validations and suggestions. So the bad news is that it requires a new
version for every CQL grammar change.
The good news is that this wait is not going to be too long (I cannot talk
yet about a specific release
Hi, All,
I use the following configuration (in yaml file) to enable the client-to-node
encryption:
client_encryption_options:
enabled: true
keystore: path-to-keystore-file
keystore_password: some-password
truststore: path-to-truststore-file
truststore_password: some-password
But
Hi,
You need to install JCE -
http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html
Bulat
On Sep 26, 2014, at 7:58, Lu, Boying boying...@emc.com wrote:
Hi, All,
I use the following configuration (in yaml file) to enable the
client-to-node encryption:
Thanks a lot. I’ll try it.
From: Bulat Shakirzyanov [mailto:mallluh...@gmail.com]
Sent: 2014年9月26日 23:58
To: user@cassandra.apache.org
Subject: Re: How to setup Cassandra client-to-node encryption
Hi,
You need to install JCE -
I’m not sure I understand correctly “for example column.name would be
event_name(temperature)“, what I gather however is that you have multiple
events that may or may not have certain properties, in your example I
believe you mean you want a CF for events with a type event_name that
contains a
I am fairly new to Cassandra. We have a 9 node cluster, 5 in one DC and 4 in
another.
Running a repair on a large column family seems to be moving much slower than I
expect.
Looking at nodetool compaction stats it indicates the Validation phase is
running that the total bytes is 4.5T
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26, 2014 at 9:52 AM, Gene Robichaux
gene.robich...@match.com wrote:
I am fairly new to Cassandra. We have a 9 node cluster, 5 in one DC and 4 in
another.
Running a repair on a
Unfortunately DSE 4.5.0 is still on 2.0.x
-- Brice
On Fri, Sep 26, 2014 at 7:40 PM, Jonathan Haddad j...@jonhaddad.com wrote:
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26, 2014 at 9:52 AM, Gene Robichaux
With a 4.5 TB table and just 4 nodes, repair will likely take forever for
any version.
-Bryan
On Fri, Sep 26, 2014 at 10:40 AM, Jonathan Haddad j...@jonhaddad.com wrote:
Are you using Cassandra 2.0 vnodes? If so, repair takes forever.
This problem is addressed in 2.1.
On Fri, Sep 26,
I am on DSE 4.0.3 which is 2.0.7.
If 4.5.1 is NOT 2.1. I guess an upgrade will not buy me much…..
The bad thing is that table is not our largest….. :(
Gene Robichaux
Manager, Database Operations
Match.com
8300 Douglas Avenue I Suite 800 I Dallas, TX 75225
Phone: 214-576-3273
From: Brice
If you're using DSE you might want to contact Datastax support, rather
than the ML.
On Fri, Sep 26, 2014 at 10:52 AM, Gene Robichaux
gene.robich...@match.com wrote:
I am on DSE 4.0.3 which is 2.0.7.
If 4.5.1 is NOT 2.1. I guess an upgrade will not buy me much…..
The bad thing is that
Using their community edition..no support (yet!) :(
Gene Robichaux
Manager, Database Operations
Match.com
8300 Douglas Avenue I Suite 800 I Dallas, TX 75225
Phone: 214-576-3273
-Original Message-
From: jonathan.had...@gmail.com [mailto:jonathan.had...@gmail.com] On Behalf Of
Well, in that case, you may want to roll your own script for doing
constant repairs of your cluster, and extend your gc grace seconds so
you can repair the whole cluster before the tombstones are cleared.
On Fri, Sep 26, 2014 at 11:15 AM, Gene Robichaux
gene.robich...@match.com wrote:
Using
Hi,
I have run cassandra-stress write and cassandra-stress read on my office
PC and on my home PC.
Office PC : Intel Core i7-4479, 8 virtual core, 16G RAM, 500G SSD Home PC :
Intel Xeon E3-1230V3, 8 virtual core, 8G RAM, 500G SATA disk.
From the cassandra-stress result (please see
I have the requirements to periodically run full tables scans on our data.
It’s mostly for repair tasks or making bulk UPDATEs… but I’d prefer to do
it in Java because I need something mildly trivial.
Pig / hadoop / etc are mildly overkill for this. I don’t want or need a
whole hadoop or HDFS
What SSD was it? There are a lot of variability in terms of SSD
performance.
1. Is it a new vs old SSD? Old SSDs can become slower if they’re really
worn out
2. was the office SSD near capacity holding other data?
3. what models were they?
SSD != SSD… there is a massive amount of
18 matches
Mail list logo
