Hi Guys,
I installed a 3 node Cassandra cluster on AWS and my replication factor is
3. I am trying to insert some data into a table. I set the consistency
level of QUORUM at a Cassandra Session level. It only inserts into one node
and unable to talk to other nodes because it is trying to contact
x.com
> > Sent: February 7, 2017 7:43 AM
> > To: dev@cassandra.apache.org
> > Reply-to: dev@cassandra.apache.org
> > Subject: Re: Why does CockroachDB github website say Cassandra has no
> > Availability on datacenter failure?
> >
> >
> > Do not
Why does CockroachDB github website say Cassandra has no Availability on
datacenter failure?
https://github.com/cockroachdb/cockroach
On Tue, Feb 7, 2017 at 3:52 AM, Kant Kodali <k...@peernova.com> wrote:
>
>
> This is the picture taken from https://github.com/cockroachdb/cockroach
>
> On Tue, Feb 7, 2017 at 3:01 AM, Benjamin Lerer <
> benjamin.le...@datastax.com> wrote:
>
>> ... and by
lol. But seriously are they even allowed to say something that is not true
about another product ?
On Tue, Feb 7, 2017 at 4:05 AM, kurt greaves wrote:
> Marketing never lies. Ever
>
d write a blog post showing Cassandra survive a failure and we can
> link to it from the Cassandra site.
>
> Now, this doesn't apply to trademarks, as the PMC is responsible for
> "defending" its marks.
>
>
>
> On Tue, Feb 7, 2017 at 7:59 AM Kant Kodali <k...@pe
; *Cc:* u...@cassandra.apache.org
> *Betreff:* Re: Why does CockroachDB github website say Cassandra has
> noAvailability on datacenter failure?
>
>
>
> The link you posted doesn't say anything about Cassandra
>
> Le 7 févr. 2017 11:41, "Kant Kodali" <k...@peernova.com> a écrit :
>
> Why does CockroachDB github website say Cassandra has no Availability on
> datacenter failure?
>
> https://github.com/cockroachdb/cockroach
>
>
>
>
https://github.com/cockroachdb/cockroach/commit/f46a547827d3439b57baa5c3a11f8f9ad2d8b153
On Tue, Feb 7, 2017 at 3:20 PM, Kant Kodali <k...@peernova.com> wrote:
> LOL They took down that image finally!! But I would still keep an eye on
> what kind of fake benchmarks they m
Adding dev only for this thread.
On Wed, Feb 1, 2017 at 4:39 AM, Kant Kodali <k...@peernova.com> wrote:
> What is the difference between accepting a value and committing a value?
>
>
>
> On Wed, Feb 1, 2017 at 4:25 AM, Kant Kodali <k...@peernova.com> wrote:
>
>&g
synchronous, you'll have a large penalty for latency.
>
> On Mon, Feb 20, 2017 at 10:11 PM, Kant Kodali <k...@peernova.com> wrote:
>
>> Thanks again for the response! if they mean it between client and server
>> I am not sure why they would use the word "replication
Hi,
1. Are Cassandra Triggers Thread Safe? what happens if two writes invoke
the trigger where the trigger is trying to modify same row in a partition?
2. Had anyone used it successfully on production? If so, any issues? (I am
using the latest version of C* 3.10)
3. I have partitions that are
Hi,
when C* coordinator writes to replicas does it write it in same order or
different order? other words, Does the replication happen synchronously or
asynchrnoulsy ? Also does this depend sync or async client? What happens in
the case of concurrent writes to a coordinator ?
Thanks,
kant
If reading from materialized view with a consistency level of quorum am I
guaranteed to have the most recent view? other words is w + r > n contract
maintained for MV's as well for both reads and writes?
Thanks!
PRIMARY KEY ((b), a)
>
>
> 2017-02-10 19:46 GMT+01:00 Kant Kodali <k...@peernova.com>:
>
> > Okies now I understand what you mean by "same" partition key. I think
> you
> > are saying
> >
> > PRIMARY KEY(col1, col2, col3) == PRIMARY KEY(col2, c
e append only cases (or more
> general cases that don't require a read before write on update) you are
> maybe better off with batched denormalized atomics writes.
>
> The main benefit of MVs is if you need denormalization to sort or filter by
> a non-primary key field.
>
> 2017
PRIMARY KEY ((a), b, c) and
> > > PRIMARY KEY ((a), c, b)
> > >
> > > Different partition key:
> > >
> > > PRIMARY KEY ((a, b), c, d) and
> > > PRIMARY KEY ((a), b, d, c)
> > >
> > > PRIMARY KEY ((a), b) and
> > > P
update may always "arrive
> late". I guess it has been implemented like this to not block in case of
> remote request to prefer the cluster sanity over consistency.
>
> Is it now 100% clear?
>
> 2017-02-10 19:17 GMT+01:00 Kant Kodali <k...@peernova.com>:
>
> > So R+
Am 10.02.2017 09:17 schrieb "Kant Kodali" <k...@peernova.com>:
>
> thanks!
>
> On Thu, Feb 9, 2017 at 8:51 PM, Benjamin Roth <benjamin.r...@jaumo.com>
> wrote:
>
> > Yes it is
> >
> > Am 10.02.2017 00:46 schrieb "Kant Kodali" <k
thanks!
On Thu, Feb 9, 2017 at 8:51 PM, Benjamin Roth <benjamin.r...@jaumo.com>
wrote:
> Yes it is
>
> Am 10.02.2017 00:46 schrieb "Kant Kodali" <k...@peernova.com>:
>
> > If reading from materialized view with a consistency level of quorum am I
> >
Hi all,
How to write a trigger in Cassandra to detect updates? My requirement is that I
want a trigger to alert me only when there is an update to an existing row and
looks like given the way INSERT and Update works this might be hard to do
because INSERT will just overwrite if there is an
I have a requirement where I need to know last value that is written
successfully so I could read that value and do some computation and include
it in the subsequent write. For now we are doing read before write which
significantly degrades the performance. Light weight transactions are more
of a
e that is written
> successfully so I could read that value and do some computation and include
> it in the subsequent write"
>
> Maybe keeping the last written value in a distributed cache is cheaper
> than doing a read before write in Cassandra ?
>
> On Sat, Nov 5, 2016 at 11:2
I understand Secondary Indexes in general are inefficient on high
cardinality columns but since SASI is built from scratch I wonder if the
same argument applies there? If not, Why? Because I believe primary keys in
Cassandra are indeed indexed and since Primary key is supposed to be the
column
Do you mean:
>
> 1) a single indexed value is present in a lot of rows
> 2) a single indexed value has only a few (if not just one) matching row
>
>
> On Sat, Oct 15, 2016 at 8:37 AM, Kant Kodali <k...@peernova.com> wrote:
>
>> I understand Secondary Indexes in ge
ialized views guarantee that for each search indexed value, you only
> hit a single node (or N replicas depending on the used consistency level)
>
> However, materialized views have their own drawbacks (weeker consistency
> guarantee) and you can't use range queries (<, >, ≤,
Hi All,
I understand Cassandra can have a maximum of 2B rows per partition but in
practice some people seem to suggest the magic number is 100K. why not
create another partition/rowkey automatically (whenever we reach a safe
limit that we consider would be efficient) with auto increment bigint
to be careful though (just like with random
> partition)
>
> Can you tell what rowkey1, page1, col(x) actually are ? Maybe there is a
> way.
> The most "recent", means there's a timestamp in there ?
>
> On Wed, Oct 12, 2016 at 9:58 AM, Kant Kodali <k...@peernov
+1
On Thu, Mar 2, 2017 at 11:04 AM, S G wrote:
> Hi,
>
> I am not able to find any documentation on the current state of triggers
> being production ready.
>
> The post at
> http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-
> 0-prototype-triggers-support
>
Doan <doanduy...@gmail.com> wrote:
> Yes the recommendation still applies
>
> Wide partitions have huge impact on repair (over streaming), compaction
> and bootstrap
>
> Le 10 mai 2017 23:54, "Kant Kodali" <k...@peernova.com> a écrit :
>
> H
oh this looks like one I am looking for
https://issues.apache.org/jira/browse/CASSANDRA-9754. Is this in Cassandra
3.10 or merged somewhere?
On Thu, May 11, 2017 at 1:13 AM, Kant Kodali <k...@peernova.com> wrote:
> Hi DuyHai,
>
> I am trying to see what are the possible things w
Hi All,
Cassandra community had always been recommending 100MB per partition as a
sweet spot however does this limitation still exist given there is a B-tree
implementation to identify rows inside a partition?
I had to do brew upgrade jemalloc to fix this issue.
On Mon, Sep 11, 2017 at 4:25 AM, Kant Kodali <k...@peernova.com> wrote:
> Hi All,
>
> I am trying to start cassandra 3.11 on Mac OS Sierra 10.12.6. when invoke
> cassandra binary I get the following error
>
> java(298
Hi All,
I am trying to start cassandra 3.11 on Mac OS Sierra 10.12.6. when invoke
cassandra binary I get the following error
java(2981,0x7fffedb763c0) malloc: *** malloc_zone_unregister() failed for
0x7fffedb6c000
I have xcode version 8.3.3 installed (latest). Any clue ?
Thanks!
Java 10 is releasing today!
On Tue, Mar 20, 2018 at 9:07 AM, Ariel Weisberg wrote:
> Hi,
>
> +1 to what Jordan is saying.
>
> It seems like if we are cutting a release off of trunk we want to make
> sure we get N years of supported JDK out of it. For a single LTS release N
>
34 matches
Mail list logo