[jira] [Commented] (CASSANDRA-6404) Tools emit ERRORs and WARNINGs about missing javaagent

2014-02-11 Thread Daniel Smedegaard Buus (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13897798#comment-13897798
 ] 

Daniel Smedegaard Buus commented on CASSANDRA-6404:
---

Righty-O, thanks :)

 Tools emit ERRORs and WARNINGs about missing javaagent 
 ---

 Key: CASSANDRA-6404
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6404
 Project: Cassandra
  Issue Type: Improvement
  Components: Tools
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Priority: Minor
 Fix For: 1.2.14, 2.0.4

 Attachments: 0001-Set-javaagent-when-running-tools-in-bin.patch


 The combination of CASSANDRA-6107  CASSANDRA-6293 has lead to a number of 
 the tools shipped in bin/ to display the following warnings when run:
 {code}
 ERROR 15:21:47,337 Unable to initialize MemoryMeter (jamm not specified as 
 javaagent).  This means Cassandra will be unable to measure object sizes 
 accurately and may consequently OOM.
  WARN 15:21:47,506 MemoryMeter uninitialized (jamm not specified as java 
 agent); KeyCache size in JVM Heap will not be calculated accurately. Usually 
 this means cassandra-env.sh disabled jamm because you are u
 {code}
 Although harmless, these are a bit disconcerting. The simplest fix seems to 
 be to set the javaagent switch as we do for the main C* launch.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CASSANDRA-6404) Tools emit ERRORs and WARNINGs about missing javaagent

2014-02-09 Thread Daniel Smedegaard Buus (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895900#comment-13895900
 ] 

Daniel Smedegaard Buus commented on CASSANDRA-6404:
---

I know this reads, Fixed, but I'm using 2.0.4 on Ubuntu 14.04, and I see this 
when running nodetool ring.

Should I be concerned about that, or?

Thanks :)

 Tools emit ERRORs and WARNINGs about missing javaagent 
 ---

 Key: CASSANDRA-6404
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6404
 Project: Cassandra
  Issue Type: Improvement
  Components: Tools
Reporter: Sam Tunnicliffe
Assignee: Sam Tunnicliffe
Priority: Minor
 Fix For: 1.2.14, 2.0.4

 Attachments: 0001-Set-javaagent-when-running-tools-in-bin.patch


 The combination of CASSANDRA-6107  CASSANDRA-6293 has lead to a number of 
 the tools shipped in bin/ to display the following warnings when run:
 {code}
 ERROR 15:21:47,337 Unable to initialize MemoryMeter (jamm not specified as 
 javaagent).  This means Cassandra will be unable to measure object sizes 
 accurately and may consequently OOM.
  WARN 15:21:47,506 MemoryMeter uninitialized (jamm not specified as java 
 agent); KeyCache size in JVM Heap will not be calculated accurately. Usually 
 this means cassandra-env.sh disabled jamm because you are u
 {code}
 Although harmless, these are a bit disconcerting. The simplest fix seems to 
 be to set the javaagent switch as we do for the main C* launch.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CASSANDRA-6276) CQL: Map can not be created with the same name as a previously dropped list

2014-01-23 Thread Daniel Smedegaard Buus (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13879828#comment-13879828
 ] 

Daniel Smedegaard Buus commented on CASSANDRA-6276:
---

This is quite frustrating when developing and debugging with large portions of 
data that need to be re-inserted every time you have a schema change because 
you have to drop an entire CF to make minor schema changes like this...

Is there a workaround one could use until this is resolved?

Thanks :)

 CQL: Map can not be created with the same name as a previously dropped list
 ---

 Key: CASSANDRA-6276
 URL: https://issues.apache.org/jira/browse/CASSANDRA-6276
 Project: Cassandra
  Issue Type: Bug
 Environment:  Cassandra 2.0.2 | CQL spec 3.1.0
 centos 64 bit
 Java(TM) SE Runtime Environment (build 1.7.0-b147)
Reporter: Oli Schacher
Priority: Minor

 If create a list, drop it and create a map with the same name, i get Bad 
 Request: comparators do not match or are not compatible.
 {quote}
 cqlsh:os_test1 create table thetable(id timeuuid primary key, somevalue 
 text);
 cqlsh:os_test1 alter table thetable add mycollection listtext;  
 cqlsh:os_test1 alter table thetable drop mycollection;
 cqlsh:os_test1 alter table thetable add mycollection maptext,text;  
 Bad Request: comparators do not match or are not compatible.
 {quote}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)