How to interpret some GC logs

2015-06-01 Thread Michał Łowicki
Hi, Normally I get logs like: 2015-06-01T09:19:50.610+: 4736.314: [GC 6505591K->4895804K(8178944K), 0.0494560 secs] which is fine and understandable but occasionalIy I see something like: 2015-06-01T09:19:50.661+: 4736.365: [GC 4901600K(8178944K), 0.0049600 secs] How to interpret it? D

AW: check active queries on cluster

2015-06-01 Thread Sebastian Martinka
You could enable DEBUG logging for org.apache.cassandra.transport.Message and TRACE logging for org.apache.cassandra.cql3.QueryProcessor in the log4j-server.properties file: log4j.logger.org.apache.cassandra.transport.Message=DEBUG log4j.logger.org.apache.cassandra.cql3.QueryProcessor=TRACE Aft

Re: How to interpret some GC logs

2015-06-01 Thread Jason Wee
can you tell what jvm is that? jason On Mon, Jun 1, 2015 at 5:46 PM, Michał Łowicki wrote: > Hi, > > Normally I get logs like: > > 2015-06-01T09:19:50.610+: 4736.314: [GC 6505591K->4895804K(8178944K), > 0.0494560 secs] > > which is fine and understandable but occasionalIy I see something li

Re: Minor Compactions Not Triggered

2015-06-01 Thread Robert Coli
On Sun, May 31, 2015 at 11:37 AM, Anuj Wadehra wrote: > 2. We thought that CQL compaction subproperty of *tombstone_threshold* > will help us after major compactions. This property will ensure that even > if we have one huge sstable, once tombstone threshold of 20% has reached, > sstables will be

Re: check active queries on cluster

2015-06-01 Thread Ben Bromhead
A warning on enabling debug and trace logging on the write path. You will be writing information about every query to disk. If you have any significant volume of requests going through the nodes things will get slow pretty quickly. At least with C* < 2.1 and using the default logging config. On 1

RE: Spark SQL JDBC Server + DSE

2015-06-01 Thread Mohammed Guller
Brian, We haven't open sourced the REST server, but not opposed to doing it. Just need to carve out some time to clean up the code and carve it out from all the other stuff that we do in that REST server. Will try to do it in the next few weeks. If you need it sooner, let me know. I did consi

Re: Minor Compactions Not Triggered

2015-06-01 Thread Anuj Wadehra
Thanks Robert !!! As per the algorithm shared in the CASSANDRA 6654, I understand that tombstone_threshold property only comes into picture if you have expirying columns and it wont have any effect if you have manually deleted rows in cf. Is my understanding correct? According to you What wo

ERROR Compaction Interrupted

2015-06-01 Thread Aiman Parvaiz
Hi everyone, I am running C* 2.0.9 without vnodes and RF=2. Recently while repairing, rebalancing the cluster I encountered one instance of this(just one on one node): ERROR CompactionExecutor: 55472 CassandraDaemon.uncaughtException - Exception in thread

Re: Spark SQL JDBC Server + DSE

2015-06-01 Thread Sebastian Estevez
Have you looked at job server? https://github.com/spark-jobserver/spark-jobserver https://www.youtube.com/watch?v=8k9ToZ4m6os http://planetcassandra.org/blog/post/fast-spark-queries-on-in-memory-datasets/ All the best, [image: datastax_logo.png] Sebastián Estévez So

Regarding JIRA

2015-06-01 Thread Kiran mk
Hi , I am using Apache Cassandra Community Edition for my learning and practicing, can I raise the doubts,issues and clarifications using JIRA ticket against Cassandra. Will there be any charges for that. As I know we can create free JIRA account, Can anyone suggest me on this. -- Best Regard

Re: Regarding JIRA

2015-06-01 Thread Daniel Compton
Hi Kiran There's no charges for raising issues in the Apache Cassandra JIRA or emailing the list. However as I'm sure you're aware, members of this list and on JIRA are mostly volunteers, so there's also no guarantee of support or response time. -- Daniel. On Tue, Jun 2, 2015 at 7:32 AM Kiran mk

Re: Regarding JIRA

2015-06-01 Thread Russell Bradberry
Also, feel free to use any of the many other resources available. The Documentation Planet Cassandra Stack Overflow #cassandra on irc.freenode.net From: Daniel Compton Reply-To: Date: Monday, June 1, 2015 at 3:37 PM To: Subject: Re: Regarding JIRA Hi Kiran There's no charges for raisin

Re: Regarding JIRA

2015-06-01 Thread Dave Brosius
JIra should be left for issues that you have some confidence are bugs in cassandra or items you want as feature requests. For general questions, try the cassandra mailing lists user@cassandra.apache.org to subscribe -> user-subscr...@cassandra.apache.org or use irc #cassandra on freenode O

Re: GC pauses affecting entire cluster.

2015-06-01 Thread graham sanderson
Yes native_objects is the way to go… you can tell if memtables are you problem because you’ll see promotion failures of objects sized 131074 dwords. If your h/w is fast enough make your young gen as big as possible - we can collect 8G in sub second always, and this gives you your best chance of

Rename User

2015-06-01 Thread Petr Malik
Hello. I know that Cassandra does not natively provide functionality for renaming users, just for altering passwords. I implemented it in my application by creating a user with the new name and original password, granting it the privileges of the original user and dropping the original user.

Re: Hbase vs Cassandra

2015-06-01 Thread Otis Gospodnetic
Hi Ajay, You won't be able to get unbiased opinion here easily. You'll need to try and see how each works for your use case. We use HBase for the SPM backend and it has worked well for us - it's stable, handles billions and billions of rows (I lost track of the actual number many moons ago) and

JSON Cassandra 2.2 - insert syntax

2015-06-01 Thread Michel Blase
Hi all, I'm trying to test the new JSON functionalities in C* 2.2. I'm using this example: https://issues.apache.org/jira/browse/CASSANDRA-7970 I believe there is a typo in the CREATE TABLE statement that requires frozen: CREATE TABLE users (id int PRIMARY KEY,name text,addresses map>); but m

Re: JSON Cassandra 2.2 - insert syntax

2015-06-01 Thread Zach Kurey
Looks like you have your use of single vs. double quotes inverted. What you want is: INSERT INTO users JSON '{"id": 123,"name": "jbellis","address": {"home": { "street": "123 Cassandra Dr","city": "Austin","zip_code": 78747,"phones": [ 2101234567]}}}'; HTH On Mon, Jun 1, 2015 at 6:03 PM, Miche

Re: JSON Cassandra 2.2 - insert syntax

2015-06-01 Thread Michel Blase
Thanks Zach, tried that but I get the same error: *SyntaxException: * On Mon, Jun 1, 2015 at 6:12 PM, Zach Kurey wrote: > Looks like you have your use of single vs. double quotes inverted. What > you want is: > > INSERT INTO users JSON '{"id": 123,"name": "jbellis","address": {"home": > {"st

Re: JSON Cassandra 2.2 - insert syntax

2015-06-01 Thread Zach Kurey
Hi Michel, My only other guess is that you actually are running Cassandra 2.1, since thats the exact error I get if I try to execute a JSON statement against a version earlier than 2.2. On Mon, Jun 1, 2015 at 6:13 PM, Michel Blase wrote: > Thanks Zach, > > tried that but I get the same error:

Re: 10000+ CF support from Cassandra

2015-06-01 Thread Arun Chaitanya
Thanks Jon and Jack, > I strongly advise against this approach. Jon, I think so too. But so you actually foresee any problems with this approach? I can think of a few. [I want to evaluate if we can live with this problem] - No more CQL. - No data types, everything needs to be a blob. - L

Re: JSON Cassandra 2.2 - insert syntax

2015-06-01 Thread Michel Blase
Zach, this is embarrassing.you were right, I was running 2.1 shame on me! but now I'm getting the error: *InvalidRequest: code=2200 [Invalid query] message="JSON values map contains unrecognized column: address"* any idea? This is the sequence of commands that I'm running: CREATE KEYSPA

Re: 10000+ CF support from Cassandra

2015-06-01 Thread Jonathan Haddad
> Sorry for this naive question but how important is this tuning? Can this have a huge impact in production? Massive. Here's a graph of when we did some JVM tuning at my previous company: http://33.media.tumblr.com/5d0efca7288dc969c1ac4fc3d36e0151/tumblr_inline_mzvj254quj1rd24f4.png About an or

Re: 10000+ CF support from Cassandra

2015-06-01 Thread graham sanderson
> > I strongly advise against this approach. > Jon, I think so too. But so you actually foresee any problems with this > approach? > I can think of a few. [I want to evaluate if we can live with this problem] Just to be clear, I’m not saying this is a great approach, I AM saying that it may be be

Re: ERROR Compaction Interrupted

2015-06-01 Thread Jason Wee
looks like it is graciously handle in the code, should be okay. if (ci.isStopRequested()) throw new CompactionInterruptedException(ci.getCompactionInfo()); https://github.com/apache/cassandra/blob/cassandra-2.0.9/src/java/org/apache/cassandra/db/compaction/Comp