No. We do not use update.
All inserts are idempotent and there is no read-before-write query.
On the corrupted data row, we have verified that the data only written once.
Thanks for your answer!
From: Laing, Michael [mailto:michael.la...@nytimes.com]
Sent: mercredi 25 novembre 2015 15:39
To:
Hi,
Congratulations! I hope the certification brings good things for you.
Regards, Ariel
On Sun, Nov 22, 2015, at 01:00 PM, Prem Yadav wrote:
> Just letting the community know that I just passed the Cassandra
> architect certification with flying colors :). Have to say I learnt a
> lot from
Be sire to include your actual insert statement. Also, what consistency
level was used for the insert (all, quorum, local quorum, one, or...)?
-- Jack Krupansky
On Wed, Nov 25, 2015 at 11:43 AM, Ngoc Minh VO
wrote:
> No. We do not use update.
>
> All inserts are
Sebastian (and others, help is always appreciated),
After 24h OK, read latencies started to degrade (up to 20ms) and I had
to ramp down volumes again.
The degradation is clearly linked to the number read IOPs which went up
to 1.65k/s after 24h.
If anybody can give me hints on what I should
Hello Sergey,
Currently Cassandra listens in one interface (the listen_address), so you
can only use multiple interfaces if your NAT configuration can route from
your public IP address to your private interface, as typically happens on
EC2 and other clouds. We're currently working to support
Hello,
We faced with the issue that Cassandra 3.0 does not work when we tried
to set up private and public networks usage.
The following doc was used:
http://docs.datastax.com/en/cassandra/3.0/cassandra/configuration/configMultiNetworks.html
First node (172.20.30.91) settings
- seeds:
Hello,
Today we tried to setup DataStaxOpsCenter-5.2.2.2015102711-linux-x64 to
work with Cassandra 3.0.
OpsCenter logs have the following:
2015-11-26 02:17:39+0300 [] INFO: Starting factory
0x2521b00>
2015-11-26 02:17:40+0300 [] INFO: Stopping factory
0x2521b00>
2015-11-26 02:17:40+0300 []
Hi Sergey,
There were some changes of the system schema tables in the released version
of Cassandra 3.0 that are preventing tools like OpsCenter and DevCenter to
connect. We are working on releasing updated versions that are fully
compatible with C 3.0.
thanks for your understanding,
On Wed,
Congrats Prem !!!
Me too planning to take up the certificate.
Please, Provide tips?
regards
Neha
On Wed, Nov 25, 2015 at 10:36 PM, Ariel Weisberg wrote:
> Hi,
>
> Congratulations! I hope the certification brings good things for you.
>
> Regards,
> Ariel
>
>
> On Sun, Nov 22,
Community growth starts by talking with those interested in your
project. ApacheCon North America is coming, are you?
We are delighted to announce that the Call For Presentations (CFP) is
now open for ApacheCon North America. You can submit your proposed
sessions at
There was several bugs in the past related to list in CQL.
Indeed the timestamp used for list columns are computed server side using a
special algorithm. I wonder if in case of read-repair or/and
hinted-handoff, would the original timestamp (the timestamp generated by
the coordinator at the first
Our insert/select queries use CL = QUORUM.
We don’t use BatchStatement to import data but executeAsync(Statement) with a
fixed-size queue.
Regards,
From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
Sent: mercredi 25 novembre 2015 18:09
To: user@cassandra.apache.org
Subject: Re: list data
Hello all,
We encounter an issue on our Production environment that cannot be reproduced
on Test environment: list (T = double or text) value is randomly
"multiplied" by 2 (i.e. value sent to C*= [a, b, c], value stored in C* = [a,
b, c, a, b, c]).
I know that it sounds weird but we just want
Hi all,
Does compaction throughput impact write performance ?
Increasing the value of compaction_throughput_mb_per_sec can improve the insert
data ? If yes, is it possible to explain to me the concept ?
Thanks.
Compaction is done to improve the reads. The compaction process is very CPU
intensive and it can make writes perform slow. Writes are also CPU-bound.
On Wed, Nov 25, 2015 at 11:12 AM, wrote:
> Hi all,
>
>
>
> Does compaction throughput impact write performance ?
>
>
>
Yes to an extent if you have descent machines and but not making use of its
resources. By default the compaction throughput is 16 MB/s which does
performs compaction very slower and runs for hours together which will lag
the compaction and makes more number of pending compaction jobs. You can
My previous answer (sstableloader) allows you moving from larger to smaller
cluster
Sent from Yahoo Mail on Android
On Tue, Nov 24, 2015 at 11:30, Anishek Agarwal wrote:
Peer,
that talks about having a similar sized cluster, I was wondering if there is a
way for
Is the data corrupted exactly the same way on all three nodes and in both
data centers, or just on one or two nodes or in only one data center?
Are both columns doubled in the same row, or only one of them in a
particular row?
Does sound like a bug though, worthy of a Jira ticket.
-- Jack
You don't have any syntax in your application anywhere such as:
UPDATE data SET field5 = field5 + [ 1,2,3 ] WHERE field1=...;
Just a quick idempotency check :)
On Wed, Nov 25, 2015 at 9:16 AM, Jack Krupansky
wrote:
> Is the data corrupted exactly the same way on all
Hello,
The data are corrupted on all the 6 replicas (3 per datacenter). I used
consistency level ONE and queried on all node -> same result.
In our use-case, only 1 of the 4 data columns (field4, 5, 6, 7) contains the
data, the 3 others contain NULL.
We are trying to create a small dataset
20 matches
Mail list logo