Yes, that is what he means. CL is for how many nodes need to respond, not
agree.
On Tue, Jun 23, 2015 at 2:26 PM, arun sirimalla wrote:
> So do you mean with CL set to QUORUM, if data is only on one node, the
> query still succeeds.
>
> On Tue, Jun 23, 2015 at 11:21 AM, Phi
Anuj,
In the first scenario, the data from the single node holding data is
returned. The query will not fail if the consistency level is met, even if
the read was inconsistent.
On Tue, Jun 23, 2015 at 2:16 PM, Anuj Wadehra
wrote:
> Why would it fail and with what Thrift error? What if the data
In a way, yes. A tombstone will only be removed after gc_grace iff the
compaction is sure that it contains all rows which that tombstone might
shadow. When two non-tombstone conflicting rows are compacted, it's always
just LWW.
On Wed, Apr 29, 2015 at 2:42 PM, Eric Stevens wrote:
> But we're tal
Did the original patch make it into upstream? That's unclear. If so, what
was the JIRA #? Have you filed a JIRA for the new problem?
On Mon, Apr 13, 2015 at 12:21 PM, Robert Wille wrote:
> Back in 2.0.4 or 2.0.5 I ran into a problem with delete-only workloads. If
> I did lots of deletes and no u
You are correct. If an overwrite occurs while the original is still in the
memtable, only the newest will be flushed to disk.
On Thu, Feb 5, 2015 at 6:15 PM, Andreas Finke
wrote:
> Hi,
>
> we are currently writing the same column within a row multiple times (up
> to 10 times a second). I am fa
Jan is incorrect. Keyspaces do not have consistency levels set on them.
Consistency Levels are always set by the client. You are almost certainly
running into https://issues.apache.org/jira/browse/CASSANDRA-7947 which is
fixed in 2.1.3 and 2.0.12.
On Fri, Jan 30, 2015 at 8:37 AM, Michał Łowicki w
uming that adding a comment of "+1" or the like
>> is more likely to be *counter*productive.
>>
>> - Ian
>>
>>
>> On Wed, Jan 21, 2015 at 5:02 PM, Philip Thompson <
>> philip.thomp...@datastax.com> wrote:
>>
>>> There is an o
There is an open ticket for this improvement at
https://issues.apache.org/jira/browse/CASSANDRA-8561
On Wed, Jan 21, 2015 at 4:55 PM, Ian Rose wrote:
> When I see a warning like "Read 9 live and 5769 tombstoned cells in ...
> " is there a way for me to see the partition key that this query was
>
I might be misinterpreting you, but it seems you are only using one seed
per node. Is there a specific reason for that? A node can have multiple
seeds in its seed list. It is my understanding that typically, every node
in a cluster has the same seed list.
On Sun, Jan 11, 2015 at 10:03 PM, Tim Dunp
2.0.11 is the current oldstable version, and is probably what you are
looking for.
On Wed, Dec 31, 2014 at 11:38 AM, Ajay wrote:
> Hi All,
>
> For my research and learning I am using Cassandra 2.1.2. But I see couple
> of mail threads going on issues in 2.1.2. So what is the stable or popular
>
I believe the problem here is that the consistency level it is showing you
is not the number of nodes that need to respond, but the enum value that
corresponds to QUORUM internally. If you would like, you can file an
improvement request on the Apache Cassandra Jira.
On Wed, Dec 17, 2014 at 12:47 A
meone else in the user
list can provide, as I have never needed to do that.
On Thu, Dec 11, 2014 at 1:59 PM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:
> Hi Philip,
>
> Yes, I'm using cqlsh. Is there any way I can solve this?
>
> Thank You!
>
> On Fri,
I assume the query you are sending is through cqlsh. You are actually
getting a client-side timeout error, which is unclear in 2.1.2, but I
believe the error message will be more helpful as of 2.1.3.
On Thu, Dec 11, 2014 at 1:52 PM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:
> Hello
racingAwareExecutorService$FutureTask.run(AbstractTracingAwareExecutorService.java:164)
> [apache-cassandra-2.1.2.jar:2.1.2]
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105)
> [apache-cassandra-2.1.2.jar:2.1.2]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_7
;
> On Thu, Dec 11, 2014 at 6:43 PM, Philip Thompson <
> philip.thomp...@datastax.com> wrote:
>
>> There is a definitely a problem here, but without the entire stack trace,
>> it is unclear what exactly may be wrong.
>>
>> On Thu, Dec 11, 2014 at 7:37 AM, Cha
There is a definitely a problem here, but without the entire stack trace,
it is unclear what exactly may be wrong.
On Thu, Dec 11, 2014 at 7:37 AM, Chamila Wijayarathna <
cdwijayarat...@gmail.com> wrote:
> Hello all,
>
> I have a column family with following schema.
>
> CREATE TABLE corpus.trigra
ler is going to add some codes to split unlogged batch and
> make the batch insertion token aware.
>
> it is already done? or else i can do it too.
>
> thanks,
> - Dong
>
> On Dec 5, 2014, at 2:06 PM, Philip Thompson
> wrote:
>
> What progress are you trying to
What progress are you trying to be aware of? All of the features Tyler
discussed are implemented and can be used.
On Fri, Dec 5, 2014 at 2:41 PM, Dong Dai wrote:
>
> On Dec 5, 2014, at 11:23 AM, Tyler Hobbs wrote:
>
>
> On Fri, Dec 5, 2014 at 1:15 AM, Dong Dai wrote:
>
>> Sounds great! By the
With the newest versions of Cassandra, cql is not hanging, but returns the
same Invalid Query Exception you are seeing through hector. I would assume
from the exception that 63072 is in fact that largest TTL you can use.
What are you doing that you need to set a TTL of approximately 30 years?
This question probably belongs in the python driver's mailing list.
However, if your RF is in fact 3, then that failed query is running at
CL.ALL, not CL.QUORUM, which you can see because the required_responses is
3. The consistency: 5 is because consistency levels are an enum class, as
seen here:
lable immediately on PyPI. Future updates will also be
published to PyPI, allowing easy installation via pip.
In a future release of CCM, ownership of the project will be transferred to
DataStax. CCM will remain open source and Apache licensed.
Thank you,
Philip Thompson
Kevin,
Have you looked at the Cassandra integration tests used by the Cassandra
development team: https://github.com/riptano/cassandra-dtest ? They make
use of CCM for integration testing: https://github.com/pcmanus/ccm
Philip Thompson
On Mon, Oct 13, 2014 at 2:50 PM, Kevin Burton wrote
You are running into https://issues.apache.org/jira/browse/CASSANDRA-7967 .
This is fixed in 2.0.11 and 2.1.1, until then I believe you will need to
explicitly grant select permission onto system.schema_triggers to the user
as a workaround.
On Sun, Sep 28, 2014 at 12:53 PM, Jens Rantil wrote:
>
Could you be experiencing
https://issues.apache.org/jira/browse/CASSANDRA-7801 ?
On Wed, Sep 17, 2014 at 2:09 PM, Jonathan Haddad wrote:
> Make sure your clocks are synced. If they aren't, the writetime that
> determines the most recent value will be incorrect.
>
> On Wed, Sep 17, 2014 at 11:58
24 matches
Mail list logo
