Re: Are write-write conflicts possible in Cassandra atomic batches when updating multiple tables?

Hi Mukil. As batches aren't isolated, I think write conflicts are effectively possible unless, somehow, you prevent them with LWT. Carlos Alonso | Software Engineer | @calonso On 17 December 2015 at 00:08, Mukil Kesavan wrote: > Hello,

Re: [Marketing Mail] can't make any permissions change in 2.2.4

On Fri, Dec 18, 2015 at 8:55 AM, Reynald Bourtembourg < reynald.bourtembo...@esrf.fr> wrote: > This does not seem to be explained in the Cassandra 2.2 Upgrading section > of the NEWS.txt file: > > >

Re: [Marketing Mail] Re: [Marketing Mail] can't make any permissions change in 2.2.4

Done: https://issues.apache.org/jira/browse/CASSANDRA-10904 On 18/12/2015 10:51, Sylvain Lebresne wrote: On Fri, Dec 18, 2015 at 8:55 AM, Reynald Bourtembourg > wrote: This does not seem to be explained in the Cassandra

OpsCenter wrong showing nodes ring

Hi, I did start datastax agent on any nodes, and configure* stomp_interface(* /var/lib/datastax-agent/conf/address.yaml*) *on all servers, then restart agent*:* BUT: > nodetool status > Datacenter: Analytics > = > Status=Up/Down > |/ State=Normal/Leaving/Joining/Moving > --

Cassandra 3.1 - Aggregation query failure

I am trying out Aggregations in a single node Cassandra 3.1 installation. The node has 4GB RAM. The table being aggregated on contains ~45 rows. It contains information on US domestic flights for a single month (from

OpsCenter support Cassandra 3.0.x

Hello, Do you know any plan to support Cassandra 3.0.x in OpsCenter by DataStax? Thanks

Re: [Marketing Mail] Re: [Marketing Mail] can't make any permissions change in 2.2.4

On Fri, Dec 18, 2015 at 3:04 PM, Kai Wang wrote: > Reynald, > > Thanks for link. That explains it. > > Sylvain, > > What exactly are the "legacy tables" I am supposed to drop? Before I drop > them, is there any way I can confirm the old schema has been converted to > the new

Re: [Marketing Mail] Re: [Marketing Mail] can't make any permissions change in 2.2.4

Reynald, Thanks for link. That explains it. Sylvain, What exactly are the "legacy tables" I am supposed to drop? Before I drop them, is there any way I can confirm the old schema has been converted to the new one successfully? Thanks. On Fri, Dec 18, 2015 at 5:05 AM, Reynald Bourtembourg <

Re: Cassandra 3.1 - Aggregation query failure

Hello There are 2 details that are important here: 1. The node has only 4Gb of RAM 2. However, the aggregation on all ~45 rows always fails, sometimes immediately, sometimes after 30-60 seconds: The consequence of point 1 is that the JVM Heap size is small: 1Gb The formulae to compute max

Re: [Marketing Mail] Re: [Marketing Mail] can't make any permissions change in 2.2.4

Sylvain, Thank you very much. On Fri, Dec 18, 2015 at 9:20 AM, Sylvain Lebresne wrote: > On Fri, Dec 18, 2015 at 3:04 PM, Kai Wang wrote: > >> Reynald, >> >> Thanks for link. That explains it. >> >> Sylvain, >> >> What exactly are the "legacy tables" I

Re: Cassandra 3.1 - Aggregation query failure

On Fri, Dec 18, 2015 at 9:17 AM, DuyHai Doan wrote: > Cassandra will perform a full table scan and fetch all the data in memory > to apply the aggregate function. Just to clarify for others on the list: when executing aggregation functions, Cassandra *will* use paging

Re: OpsCenter support Cassandra 3.0.x

"*Note: Future versions of OpsCenter will support Cassandra versions 2.2 and 3.0.*" http://docs.datastax.com/en/upgrade/doc/upgrade/opscenter/opscCompatibility.html On Fri, Dec 18, 2015 at 8:16 AM, Cassandramail wrote: > Hello, > > Do you know any plan to support