[jira] [Commented] (CASSANDRA-8325) Cassandra 2.1.x fails to start on FreeBSD (JVM crash)

[ https://issues.apache.org/jira/browse/CASSANDRA-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265799#comment-14265799 ] graham sanderson commented on CASSANDRA-8325: - Well that is good news I

[jira] [Commented] (CASSANDRA-8528) Add an ExecutionException to the protocol

[ https://issues.apache.org/jira/browse/CASSANDRA-8528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264400#comment-14264400 ] Sylvain Lebresne commented on CASSANDRA-8528: - bq. that extends

[jira] [Commented] (CASSANDRA-8560) Make CassandraException be an unchecked exception

[ https://issues.apache.org/jira/browse/CASSANDRA-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264442#comment-14264442 ] Robert Stupp commented on CASSANDRA-8560: - Making {{CassandraException}}

[jira] [Commented] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264482#comment-14264482 ] Sylvain Lebresne commented on CASSANDRA-8558: - [~philipthompson] Can you

[jira] [Commented] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264494#comment-14264494 ] Benedict commented on CASSANDRA-8546: - Did you accidentally set me as assignee?

[jira] [Commented] (CASSANDRA-8559) OOM caused by large tombstone warning.

[ https://issues.apache.org/jira/browse/CASSANDRA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264497#comment-14264497 ] Benedict commented on CASSANDRA-8559: - This suggests you are _requesting_ some

[jira] [Updated] (CASSANDRA-8552) Large compactions run out of off-heap RAM

[ https://issues.apache.org/jira/browse/CASSANDRA-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-8552: --- Reproduced In: 2.1.2, 2.1.1 (was: 2.1.1, 2.1.2) Assignee: Benedict

[jira] [Commented] (CASSANDRA-8549) Not able to bring cassandra cluster to stable state

[ https://issues.apache.org/jira/browse/CASSANDRA-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264468#comment-14264468 ] Rahul Bhardwaj commented on CASSANDRA-8549: --- thanks alot .. It worked..!!

[jira] [Created] (CASSANDRA-8560) Make CassandraException be an unchecked exception

Sylvain Lebresne created CASSANDRA-8560: --- Summary: Make CassandraException be an unchecked exception Key: CASSANDRA-8560 URL: https://issues.apache.org/jira/browse/CASSANDRA-8560 Project:

[jira] [Commented] (CASSANDRA-7970) JSON support for CQL

[ https://issues.apache.org/jira/browse/CASSANDRA-7970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264342#comment-14264342 ] Sylvain Lebresne commented on CASSANDRA-7970: - bq. are you okay with

[jira] [Commented] (CASSANDRA-8365) CamelCase name is used as index name instead of lowercase

[ https://issues.apache.org/jira/browse/CASSANDRA-8365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264365#comment-14264365 ] Benjamin Lerer commented on CASSANDRA-8365: --- I had a look at the code. In

[jira] [Updated] (CASSANDRA-7016) can't map/reduce over subset of rows with cql

[ https://issues.apache.org/jira/browse/CASSANDRA-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-7016: -- Attachment: CASSANDRA-7016-V5-trunk.txt This patch fixes the problems mentioned by

[jira] [Commented] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264520#comment-14264520 ] Dominic Letz commented on CASSANDRA-8546: - Sorry for the assignment, Tyler

[jira] [Comment Edited] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264520#comment-14264520 ] Dominic Letz edited comment on CASSANDRA-8546 at 1/5/15 12:00 PM:

[jira] [Commented] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264524#comment-14264524 ] zhaoyan commented on CASSANDRA-8558: we used 2.0.8 before it is ok with 2.0.8

[jira] [Commented] (CASSANDRA-8559) OOM caused by large tombstone warning.

[ https://issues.apache.org/jira/browse/CASSANDRA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264532#comment-14264532 ] Sylvain Lebresne commented on CASSANDRA-8559: - I would have suspected that

[jira] [Commented] (CASSANDRA-8559) OOM caused by large tombstone warning.

[ https://issues.apache.org/jira/browse/CASSANDRA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264538#comment-14264538 ] Dominic Letz commented on CASSANDRA-8559: - Both is true, there are huge gaps

[jira] [Commented] (CASSANDRA-8552) Large compactions run out of off-heap RAM

[ https://issues.apache.org/jira/browse/CASSANDRA-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264549#comment-14264549 ] Benedict commented on CASSANDRA-8552: - Well now, this is going to be tricky then,

[jira] [Commented] (CASSANDRA-8554) Node where gossip is disabled still shows as UP on that node; other nodes show it as DN

[ https://issues.apache.org/jira/browse/CASSANDRA-8554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264550#comment-14264550 ] Brandon Williams commented on CASSANDRA-8554: - bq. the drained node will

[jira] [Commented] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264565#comment-14264565 ] Benedict commented on CASSANDRA-8546: - If CASSANDRA-8099 fixes it somehow, that's

[jira] [Commented] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264547#comment-14264547 ] Sylvain Lebresne commented on CASSANDRA-8546: - The reason you get this is

[jira] [Commented] (CASSANDRA-8549) Not able to bring cassandra cluster to stable state

[ https://issues.apache.org/jira/browse/CASSANDRA-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264571#comment-14264571 ] Benedict commented on CASSANDRA-8549: - It's possible you're facing CASSANDRA-8552.

[jira] [Commented] (CASSANDRA-8561) Tombstone log warning does not log partition key

[ https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264580#comment-14264580 ] Jens Rantil commented on CASSANDRA-8561: I updated the gist to also include

[jira] [Created] (CASSANDRA-8561) Tombstone log warning does not log partition key

Jens Rantil created CASSANDRA-8561: -- Summary: Tombstone log warning does not log partition key Key: CASSANDRA-8561 URL: https://issues.apache.org/jira/browse/CASSANDRA-8561 Project: Cassandra

[jira] [Commented] (CASSANDRA-8560) Make CassandraException be an unchecked exception

[ https://issues.apache.org/jira/browse/CASSANDRA-8560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264588#comment-14264588 ] Robert Stupp commented on CASSANDRA-8560: - Note:

[jira] [Updated] (CASSANDRA-7275) Errors in FlushRunnable may leave threads hung

[ https://issues.apache.org/jira/browse/CASSANDRA-7275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7275: Assignee: Pavel Yaskevich (was: Benedict) Errors in FlushRunnable may leave threads hung

[jira] [Updated] (CASSANDRA-8414) Avoid loops over array backed iterators that call iter.remove()

[ https://issues.apache.org/jira/browse/CASSANDRA-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-8414: Issue Type: Improvement (was: Bug) Avoid loops over array backed iterators that call

[jira] [Commented] (CASSANDRA-7275) Errors in FlushRunnable may leave threads hung

[ https://issues.apache.org/jira/browse/CASSANDRA-7275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264623#comment-14264623 ] Benedict commented on CASSANDRA-7275: - Accidentally assigned myself this ticket.

[jira] [Updated] (CASSANDRA-7937) Apply backpressure gently when overloaded with writes

[ https://issues.apache.org/jira/browse/CASSANDRA-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7937: Issue Type: Improvement (was: Bug) Apply backpressure gently when overloaded with writes

[jira] [Resolved] (CASSANDRA-8549) Not able to bring cassandra cluster to stable state

[ https://issues.apache.org/jira/browse/CASSANDRA-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict resolved CASSANDRA-8549. - Resolution: Duplicate Not able to bring cassandra cluster to stable state

[jira] [Created] (CASSANDRA-8562) Fix checking available disk space before compaction starts

Marcus Eriksson created CASSANDRA-8562: -- Summary: Fix checking available disk space before compaction starts Key: CASSANDRA-8562 URL: https://issues.apache.org/jira/browse/CASSANDRA-8562 Project:

[jira] [Resolved] (CASSANDRA-8555) Immediate sequential update of column sometimes not immediately applied (OS X only?)

[ https://issues.apache.org/jira/browse/CASSANDRA-8555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Tolbert resolved CASSANDRA-8555. - Resolution: Not a Problem Reproduced In: 2.1.2, 2.0.11, 1.2.19 (was: 1.2.19,

[jira] [Commented] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264638#comment-14264638 ] Philip Thompson commented on CASSANDRA-8558: I am able to reproduce this

[jira] [Comment Edited] (CASSANDRA-8555) Immediate sequential update of column sometimes not immediately applied (OS X only?)

[ https://issues.apache.org/jira/browse/CASSANDRA-8555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264640#comment-14264640 ] Andy Tolbert edited comment on CASSANDRA-8555 at 1/5/15 2:50 PM:

[jira] [Commented] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264645#comment-14264645 ] Philip Thompson commented on CASSANDRA-8558: [~slebresne], I have pushed

[1/3] cassandra git commit: ninja fix CommitLogAllocator error suppression on shutdown for CASSANDRA-8474

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 aeb7d3f2e - c1374ae42 refs/heads/trunk 1dcf66b09 - ec15878ef ninja fix CommitLogAllocator error suppression on shutdown for CASSANDRA-8474 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[3/3] cassandra git commit: Merge branch 'cassandra-2.1' into trunk

Merge branch 'cassandra-2.1' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/ec15878e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/ec15878e Diff:

[2/3] cassandra git commit: ninja fix CommitLogAllocator error suppression on shutdown for CASSANDRA-8474

ninja fix CommitLogAllocator error suppression on shutdown for CASSANDRA-8474 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/c1374ae4 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/c1374ae4 Diff:

[jira] [Updated] (CASSANDRA-7980) cassandra-stress should support partial clustering column generation

[ https://issues.apache.org/jira/browse/CASSANDRA-7980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-7980: Issue Type: Improvement (was: Bug) cassandra-stress should support partial clustering column

[jira] [Comment Edited] (CASSANDRA-8548) Nodetool Cleanup - IllegalArgumentException

[ https://issues.apache.org/jira/browse/CASSANDRA-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264794#comment-14264794 ] Sebastian Estevez edited comment on CASSANDRA-8548 at 1/5/15 5:28 PM:

[jira] [Commented] (CASSANDRA-8548) Nodetool Cleanup - IllegalArgumentException

[ https://issues.apache.org/jira/browse/CASSANDRA-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264794#comment-14264794 ] Sebastian Estevez commented on CASSANDRA-8548: -- Here's another, almost

[jira] [Created] (CASSANDRA-8563) cqlsh broken for some thrift created tables.

Jeremiah Jordan created CASSANDRA-8563: -- Summary: cqlsh broken for some thrift created tables. Key: CASSANDRA-8563 URL: https://issues.apache.org/jira/browse/CASSANDRA-8563 Project: Cassandra

[jira] [Commented] (CASSANDRA-8535) java.lang.RuntimeException: Failed to rename XXX to YYY

[ https://issues.apache.org/jira/browse/CASSANDRA-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264791#comment-14264791 ] Leonid Shalupov commented on CASSANDRA-8535: This is ticket is about both

[jira] [Comment Edited] (CASSANDRA-8548) Nodetool Cleanup - IllegalArgumentException

[ https://issues.apache.org/jira/browse/CASSANDRA-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264794#comment-14264794 ] Sebastian Estevez edited comment on CASSANDRA-8548 at 1/5/15 5:28 PM:

[jira] [Commented] (CASSANDRA-8544) Cassandra could not start with NPE in ColumnFamilyStore.removeUnfinishedCompactionLeftovers

[ https://issues.apache.org/jira/browse/CASSANDRA-8544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264804#comment-14264804 ] Leonid Shalupov commented on CASSANDRA-8544: I've seen it two times

[jira] [Comment Edited] (CASSANDRA-8535) java.lang.RuntimeException: Failed to rename XXX to YYY

[ https://issues.apache.org/jira/browse/CASSANDRA-8535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264791#comment-14264791 ] Leonid Shalupov edited comment on CASSANDRA-8535 at 1/5/15 5:41 PM:

[jira] [Updated] (CASSANDRA-8399) Reference Counter exception when dropping user type

[ https://issues.apache.org/jira/browse/CASSANDRA-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-8399: Assignee: Joshua McKenzie (was: Benedict) Reference Counter exception when dropping user type

[jira] [Commented] (CASSANDRA-3025) PHP/PDO driver for Cassandra CQL

[ https://issues.apache.org/jira/browse/CASSANDRA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265139#comment-14265139 ] Michael Shuler commented on CASSANDRA-3025: --- This bug shouldn't be reopened.

[jira] [Commented] (CASSANDRA-8399) Reference Counter exception when dropping user type

[ https://issues.apache.org/jira/browse/CASSANDRA-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265268#comment-14265268 ] Benedict commented on CASSANDRA-8399: - OK, after looking at this some more, I have

[jira] [Created] (CASSANDRA-8566) node crash (while auto-compaction?)

Dmitri Dmitrienko created CASSANDRA-8566: Summary: node crash (while auto-compaction?) Key: CASSANDRA-8566 URL: https://issues.apache.org/jira/browse/CASSANDRA-8566 Project: Cassandra

[jira] [Created] (CASSANDRA-8567) Functions like length() and trim() on cqlsh table fields

Rekha Joshi created CASSANDRA-8567: -- Summary: Functions like length() and trim() on cqlsh table fields Key: CASSANDRA-8567 URL: https://issues.apache.org/jira/browse/CASSANDRA-8567 Project: Cassandra

[jira] [Commented] (CASSANDRA-8565) opinion on refactoring ListenableFuture to Java 8 CompletableFuture

[ https://issues.apache.org/jira/browse/CASSANDRA-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265334#comment-14265334 ] Aleksey Yeschenko commented on CASSANDRA-8565: -- We can't do it just yet,

[jira] [Resolved] (CASSANDRA-8565) opinion on refactoring ListenableFuture to Java 8 CompletableFuture

[ https://issues.apache.org/jira/browse/CASSANDRA-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko resolved CASSANDRA-8565. -- Resolution: Later opinion on refactoring ListenableFuture to Java 8

[jira] [Updated] (CASSANDRA-8547) Make RangeTombstone.Tracker.isDeleted() faster

[ https://issues.apache.org/jira/browse/CASSANDRA-8547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Letz updated CASSANDRA-8547: Attachment: Selection_044.png Attaching a screenshot of visualvm showing where a

[jira] [Commented] (CASSANDRA-8552) Large compactions run out of off-heap RAM

[ https://issues.apache.org/jira/browse/CASSANDRA-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265400#comment-14265400 ] Brent Haines commented on CASSANDRA-8552: - We have 4 tables in the keyspace -

[jira] [Commented] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265568#comment-14265568 ] Dominic Letz commented on CASSANDRA-8546: - This makes all sense. From my

[jira] [Updated] (CASSANDRA-8546) RangeTombstoneList becoming bottleneck on tombstone heavy tasks

[ https://issues.apache.org/jira/browse/CASSANDRA-8546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Letz updated CASSANDRA-8546: Attachment: rangetombstonelist_read.png rangetombstonelist_mutation.png

[jira] [Updated] (CASSANDRA-8559) OOM caused by large tombstone warning.

[ https://issues.apache.org/jira/browse/CASSANDRA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominic Letz updated CASSANDRA-8559: Attachment: stacktrace.log Attaching stacktrace of the very crash (Cassandra 2.0.11).

[jira] [Commented] (CASSANDRA-8559) OOM caused by large tombstone warning.

[ https://issues.apache.org/jira/browse/CASSANDRA-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265596#comment-14265596 ] Dominic Letz commented on CASSANDRA-8559: - To qualify that a bit more, you are

[jira] [Commented] (CASSANDRA-6123) Break timestamp ties consistently for a given user requests

[ https://issues.apache.org/jira/browse/CASSANDRA-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264814#comment-14264814 ] Aleksey Yeschenko commented on CASSANDRA-6123: -- No, but CASSANDRA-7801

[jira] [Updated] (CASSANDRA-8545) Simple hints are timing out on replay

[ https://issues.apache.org/jira/browse/CASSANDRA-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-8545: --- Reproduced In: 2.0.11 Simple hints are timing out on replay

[jira] [Commented] (CASSANDRA-8325) Cassandra 2.1.x fails to start on FreeBSD (JVM crash)

[ https://issues.apache.org/jira/browse/CASSANDRA-8325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264819#comment-14264819 ] Leonid Shalupov commented on CASSANDRA-8325: untested_8325.patch works for

[jira] [Commented] (CASSANDRA-8520) Prototype thread per core

[ https://issues.apache.org/jira/browse/CASSANDRA-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264824#comment-14264824 ] Jonathan Ellis commented on CASSANDRA-8520: --- Agreed that this is the correct

[jira] [Resolved] (CASSANDRA-8529) Cassandra suddenly stops responding to clients though process is still running

[ https://issues.apache.org/jira/browse/CASSANDRA-8529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-8529. --- Resolution: Incomplete Reproduced In: (was: 2.1.2) Sounds like your JVM

[jira] [Commented] (CASSANDRA-8531) metric CommitLog.PendingTasks is always growing

[ https://issues.apache.org/jira/browse/CASSANDRA-8531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264830#comment-14264830 ] Jonathan Ellis commented on CASSANDRA-8531: --- Not sure what you're looking

[jira] [Commented] (CASSANDRA-6123) Break timestamp ties consistently for a given user requests

[ https://issues.apache.org/jira/browse/CASSANDRA-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264808#comment-14264808 ] Thanh commented on CASSANDRA-6123: -- To be clear, this jira does _not_ apply to

[jira] [Commented] (CASSANDRA-7705) Safer Resource Management

[ https://issues.apache.org/jira/browse/CASSANDRA-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265038#comment-14265038 ] Benedict commented on CASSANDRA-7705: - Noting: there seems to be agreement on IRC

[jira] [Created] (CASSANDRA-8565) opinion on refactoring ListenableFuture to Java 8 CompletableFuture

Yu Lin created CASSANDRA-8565: - Summary: opinion on refactoring ListenableFuture to Java 8 CompletableFuture Key: CASSANDRA-8565 URL: https://issues.apache.org/jira/browse/CASSANDRA-8565 Project:

[jira] [Commented] (CASSANDRA-8520) Prototype thread per core

[ https://issues.apache.org/jira/browse/CASSANDRA-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264866#comment-14264866 ] Benedict commented on CASSANDRA-8520: - Right. I wanted to highlight this wider

[jira] [Commented] (CASSANDRA-8548) Nodetool Cleanup - IllegalArgumentException

[ https://issues.apache.org/jira/browse/CASSANDRA-8548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264873#comment-14264873 ] Sebastian Estevez commented on CASSANDRA-8548: -- Looks like the second

[jira] [Updated] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-8558: --- Assignee: Benedict deleted row still can be selected out

[jira] [Commented] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264900#comment-14264900 ] Philip Thompson commented on CASSANDRA-8558: I've assigned this to

[jira] [Commented] (CASSANDRA-8558) deleted row still can be selected out

[ https://issues.apache.org/jira/browse/CASSANDRA-8558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264898#comment-14264898 ] Philip Thompson commented on CASSANDRA-8558: {code}

[jira] [Updated] (CASSANDRA-8563) cqlsh broken for some thrift created tables.

[ https://issues.apache.org/jira/browse/CASSANDRA-8563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-8563: --- Labels: cqlsh (was: ) cqlsh broken for some thrift created tables.

[jira] [Updated] (CASSANDRA-8194) Reading from Auth table should not be in the request path

[ https://issues.apache.org/jira/browse/CASSANDRA-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-8194: - Reviewer: Sam Tunnicliffe (was: Aleksey Yeschenko) Reading from Auth table

[jira] [Commented] (CASSANDRA-8194) Reading from Auth table should not be in the request path

[ https://issues.apache.org/jira/browse/CASSANDRA-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264934#comment-14264934 ] Aleksey Yeschenko commented on CASSANDRA-8194: -- [~beobal] can you have a

[jira] [Updated] (CASSANDRA-7666) Range-segmented sstables

[ https://issues.apache.org/jira/browse/CASSANDRA-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-7666: - Fix Version/s: (was: 3.0) 3.1 Range-segmented

[jira] [Created] (CASSANDRA-8564) Harmless exception logged as ERROR

Philip Thompson created CASSANDRA-8564: -- Summary: Harmless exception logged as ERROR Key: CASSANDRA-8564 URL: https://issues.apache.org/jira/browse/CASSANDRA-8564 Project: Cassandra

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264970#comment-14264970 ] Jon Haddad commented on CASSANDRA-8494: --- Is it possible for a node to acquire a

cassandra git commit: Add CONTRIBUTING.md

Repository: cassandra Updated Branches: refs/heads/cassandra-2.0 e550ea602 - a22308294 Add CONTRIBUTING.md See https://github.com/blog/1184-contributing-guidelines Hopefully this will miminise the amount of pull requests we keep getting. Project:

[1/2] cassandra git commit: Add CONTRIBUTING.md

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 c1374ae42 - 1af8ea5ef Add CONTRIBUTING.md See https://github.com/blog/1184-contributing-guidelines Hopefully this will miminise the amount of pull requests we keep getting. Project:

[2/3] cassandra git commit: Merge branch 'cassandra-2.0' into cassandra-2.1

Merge branch 'cassandra-2.0' into cassandra-2.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1af8ea5e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1af8ea5e Diff:

[1/3] cassandra git commit: Add CONTRIBUTING.md

Repository: cassandra Updated Branches: refs/heads/trunk ec15878ef - dc0102a8e Add CONTRIBUTING.md See https://github.com/blog/1184-contributing-guidelines Hopefully this will miminise the amount of pull requests we keep getting. Project:

[2/2] cassandra git commit: Merge branch 'cassandra-2.0' into cassandra-2.1

Merge branch 'cassandra-2.0' into cassandra-2.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/1af8ea5e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/1af8ea5e Diff:

[3/3] cassandra git commit: Merge branch 'cassandra-2.1' into trunk

Merge branch 'cassandra-2.1' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/dc0102a8 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/dc0102a8 Diff:

[jira] [Updated] (CASSANDRA-8562) Fix checking available disk space before compaction starts

[ https://issues.apache.org/jira/browse/CASSANDRA-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-8562: --- Attachment: 0001-Check-for-available-disk-space-before-starting-compa.patch

[jira] [Comment Edited] (CASSANDRA-8562) Fix checking available disk space before compaction starts

[ https://issues.apache.org/jira/browse/CASSANDRA-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264659#comment-14264659 ] Marcus Eriksson edited comment on CASSANDRA-8562 at 1/5/15 3:20 PM:

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264688#comment-14264688 ] Yuki Morishita commented on CASSANDRA-8494: --- In that case, we need to

[jira] [Updated] (CASSANDRA-8561) Tombstone log warning does not log partition key

[ https://issues.apache.org/jira/browse/CASSANDRA-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-8561: --- Fix Version/s: 2.1.3 2.0.12 Tombstone log warning does not

[jira] [Updated] (CASSANDRA-8562) Fix checking available disk space before compaction starts

[ https://issues.apache.org/jira/browse/CASSANDRA-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-8562: --- Attachment: 0001-Check-for-available-disk-space-before-starting-compa.patch Fix

[jira] [Updated] (CASSANDRA-8562) Fix checking available disk space before compaction starts

[ https://issues.apache.org/jira/browse/CASSANDRA-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-8562: --- Attachment: (was:

[jira] [Commented] (CASSANDRA-8490) DISTINCT queries with LIMITs or paging are incorrect when partitions are deleted

[ https://issues.apache.org/jira/browse/CASSANDRA-8490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264665#comment-14264665 ] Sylvain Lebresne commented on CASSANDRA-8490: - It is indeed annoying. bq.

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14264714#comment-14264714 ] T Jake Luciani commented on CASSANDRA-8494: --- I'm not suggesting we change

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265078#comment-14265078 ] T Jake Luciani commented on CASSANDRA-8494: --- bq. Is it possible for a node

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265084#comment-14265084 ] Jon Haddad commented on CASSANDRA-8494: --- {quote} If the node dies nothing bad

[jira] [Updated] (CASSANDRA-8499) Ensure SSTableWriter cleans up properly after failure

[ https://issues.apache.org/jira/browse/CASSANDRA-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-8499: Attachment: 8499-21v2 8499-20v2 Ensure SSTableWriter cleans up properly after

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265087#comment-14265087 ] T Jake Luciani commented on CASSANDRA-8494: --- It could I think. Assuming it

[jira] [Commented] (CASSANDRA-8499) Ensure SSTableWriter cleans up properly after failure

[ https://issues.apache.org/jira/browse/CASSANDRA-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265086#comment-14265086 ] Benedict commented on CASSANDRA-8499: - Good point. I've updated both versions to

[jira] [Commented] (CASSANDRA-3025) PHP/PDO driver for Cassandra CQL

[ https://issues.apache.org/jira/browse/CASSANDRA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265088#comment-14265088 ] Lex Lythius commented on CASSANDRA-3025: Would you mind reopening this bug?

[jira] [Commented] (CASSANDRA-8494) incremental bootstrap

[ https://issues.apache.org/jira/browse/CASSANDRA-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265097#comment-14265097 ] Jon Haddad commented on CASSANDRA-8494: --- {quote} It could I think. Assuming it

  1   2   >