Performance penalty of multiple UPDATEs of non-pk columns

I've seen some discussions about the topic on the list recently, but I would like to get more clear answers. Given the table: CREATE TABLE t1 ( f1 text, f2 text, f3 text, PRIMARY KEY(f1, f2) ); and assuming I will execute UPDATE of f3 multiple times (say, 1000)

Clarification of property: storage_port

I have questions regarding function and limitations of configurability of the property storage_port. Function: What protocols and functions is storage_port used for? Am I right to believe that it is used for Gossip? And more importantly: It seems to me that storage_port MUST be configured to be

Java Client Driver for Cassandra 2.0.14

Apart from datastax java client driver, does Apache Cassandra provide its own java client driver? Or should be using the datastax one? If yes, then could anyone give me the link? DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persis

Re: Java Client Driver for Cassandra 2.0.14

I started using the datastax driver (coming from astynax driver) recently. It is awesome! Use it :D https://github.com/datastax/java-driver Cheers, artur On 15/05/15 10:32, Rohit Naik wrote: DISCLAIMER == This e-mail may contain privileged an

ODBC connector, UDTs and Tableau

Hello,I'm playing with DataStax's ODBC connector for Cassandra and have noticed something...well...broken. If I have a keyspace with tables that don't have a UDT column (even though the UDT is created), things work fine. However, the moment I add a table that has a UDT column, nothing works. I'm

Re: Clarification of property: storage_port

On Fri, May 15, 2015 at 4:17 AM, Magnus Vojbacke < magnus.vojba...@digitalroute.com> wrote: > > Function: What protocols and functions is storage_port used for? Am I > right to believe that it is used for Gossip? > It's used for all internode communication (gossip, requests, etc). > > And more

Re: Clarification of property: storage_port

On Fri, May 15, 2015 at 4:17 AM, Magnus Vojbacke < magnus.vojba...@digitalroute.com> wrote: > > Why would I want to configure different storage_ports? Function test > environment with multiple nodes on the same hostname. > > You can still do this via multiple loopback addresses. If you have access

Re: Caching the PreparedStatement (Java driver)

Hi Joseph, Java driver currently caches the prepared statements but using a weak reference i.e the cache will hold it as long the client code uses it. So in turn means that we need to cache the same. But I am also not sure of what happens when a cached prepared statement is executed after cassand

After running nodetool clean up, the used disk space was increased

Hello guys, I have a cassandra cluster = 2.1.0-2 comprised of 3 nodes. I successfully added the third node last week. After that, I ran nodetool cleanup on one of the other two nodes, and it finished well but it increased the used disk space. Before running the clean up the node was 197 GB of us

C*1.2 on JVM 1.7

Has anybody run DSE 3.2.6(C*1.2.16) on JRE 1.7. I know its recommended that we have to get to JVM version 7 to get to C*2.0 and higher. We are experiencing latency issues during rolling upgrade from 1.2 to 2.0. Hence cannot get o C*1.2, but plan to just upgrade JRE from 1.6 to 1.7. I wanted to kno

Leap sec

Just curious to know on how you are preparing Prod C* clusters for leap sec. What are the workaorund other than upgrading kernel to 3.4+? Are you upgrading clusters to Java 7 or higher on client and C* servers?

Re: After running nodetool clean up, the used disk space was increased

Did you try running nodetool cleanup on all the nodes ? On May 15, 2015 10:47 PM, "Analia Lorenzatto" wrote: > Hello guys, > > I have a cassandra cluster = 2.1.0-2 comprised of 3 nodes. I successfully > added the third node last week. After that, I ran nodetool cleanup on one > of the other two

RE: C*1.2 on JVM 1.7

I have run plenty of 1.2.x Cassandra versions on the Oracle JVM 1.7. I have used both 1.7.0_40 and 1.7.0_72 with no issues. Also have 3.2.7 DSE running on 1.7.0_72 in PR with no issues. Sean Durity – Cassandra Admin, Big Data Team To engage the team, create a request

Re: After running nodetool clean up, the used disk space was increased

Thanks Kiran for answering! I already ran cleanup on just one node. At this moment, I am running on the second one, but it did not finish there. On Fri, May 15, 2015 at 3:37 PM, Kiran mk wrote: > Did you try running nodetool cleanup on all the nodes ? > On May 15, 2015 10:47 PM, "Analia Loren

Re: After running nodetool clean up, the used disk space was increased

What is the data distribution status across nodes ? What is the RP ? On May 16, 2015 12:30 AM, "Analia Lorenzatto" wrote: > Thanks Kiran for answering! > > I already ran cleanup on just one node. At this moment, I am running on > the second one, but it did not finish there. > > > On Fri, May 15,

Re: After running nodetool clean up, the used disk space was increased

What is the Replication Factor ? What does ring status saying ? On May 16, 2015 12:32 AM, "Kiran mk" wrote: > What is the data distribution status across nodes ? What is the RP ? > On May 16, 2015 12:30 AM, "Analia Lorenzatto" > wrote: > >> Thanks Kiran for answering! >> >> I already ran cleanu

Re: After running nodetool clean up, the used disk space was increased

The cluster is comprised of 3 nodes, with a RP=2: # nodetool status Datacenter: us-east === Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns (effective) Host ID Rack UN 10.x.x.a 420.05 GB 256 66.7% eed9e9f5-f279-4

Re: Caching the PreparedStatement (Java driver)

On Fri, May 15, 2015 at 12:02 PM, Ajay wrote: > > But I am also not sure of what happens when a cached prepared statement is > executed after cassandra nodes restart. Does the server prepared statements > cache is persisted or in memory?. For now, it's just in memory, so they are lost when the

Re: After running nodetool clean up, the used disk space was increased

run cleanup on all the nodes and wait till it completes. On May 15, 2015 10:47 PM, "Analia Lorenzatto" wrote: > Hello guys, > > I have a cassandra cluster = 2.1.0-2 comprised of 3 nodes. I successfully > added the third node last week. After that, I ran nodetool cleanup on one > of the other tw

Re: Leap sec

This post has some good advice for preparing for the leap second: http://www.datastax.com/dev/blog/preparing-for-the-leap-second On Fri, May 15, 2015 at 12:25 PM, cass savy wrote: > Just curious to know on how you are preparing Prod C* clusters for leap > sec. > > What are the workaorund other t

Re: Out of memory on wide row read

I William file a jira for that, thanks On May 12, 2015 10:15 PM, "Jack Krupansky" wrote: > Sounds like it's worth a Jira - Cassandra should protect itself from > innocent mistakes or excessive requests from clients. Maybe there should be > a timeout or result size (bytes in addition to count) lim

Re: Leap sec

> This post has some good advice for preparing for the leap second: > http://www.datastax.com/dev/blog/preparing-for-the-leap-second Post author here. Let me know if you have any questions about it. > What are the workaorund other than upgrading kernel to 3.4+? A couple NTP-based workarounds are

Re: After running nodetool clean up, the used disk space was increased

The Replication Factor = 2. The RP is the default, but not sure how to check it. I am attaching the output of: nodetool ring Thanks a lot! On Fri, May 15, 2015 at 4:17 PM, Kiran mk wrote: > run cleanup on all the nodes and wait till it completes. > On May 15, 2015 10:47 PM, "Analia Lorenzatto"

Re: Leap sec

Are you suggesting the JDK 7 for client/driver and c* side as well. We use Java driver 2.1.4 and plan to goto JDK7u80 on application end. In addition, do I also have to upgrade to Java 7u60+ on C* servers as well. On Fri, May 15, 2015 at 1:06 PM, Jim Witschey wrote: > > This post has some good a

Re: After running nodetool clean up, the used disk space was increased

Have you cleared snapshots? On May 15, 2015, at 2:24 PM, Analia Lorenzatto mailto:analialorenza...@gmail.com>> wrote: The Replication Factor = 2. The RP is the default, but not sure how to check it. I am attaching the output of: nodetool ring Thanks a lot! On Fri, May 15, 2015 at 4:17 PM, Ki

Re: Leap sec

> In addition, do I also have to upgrade to Java 7u60+ on C* servers as well. Yes -- we observed C* nodes locking up when running under older versions of the JDK. Jim Witschey Software Engineer in Test | jim.witsc...@datastax.com

Re: After running nodetool clean up, the used disk space was increased

Yes Robert, I already cleared the snapshots. After that, the used disk space is: 10.x.x.b@$ df -h /mnt/cassandra Filesystem Size Used Avail Use% Mounted on /dev/xvdb1 745G 174G 572G 24% /mnt/cassandra But, the cluster shows me a different thing: $ nodetool status Datacenter: us-ea