[jira] [Resolved] (CASSANDRA-7377) Should be an option to fail startup if corrupt SSTable found

[ https://issues.apache.org/jira/browse/CASSANDRA-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low resolved CASSANDRA-7377. Resolution: Duplicate > Should be an option to fail startup if corrupt SSTable found >

[jira] [Commented] (CASSANDRA-7377) Should be an option to fail startup if corrupt SSTable found

[ https://issues.apache.org/jira/browse/CASSANDRA-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287100#comment-16287100 ] Richard Low commented on CASSANDRA-7377: SGTM > Should be an option to fail startup if

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219759#comment-16219759 ] Richard Low commented on CASSANDRA-10726: - Background read repair is quite different. This

[jira] [Commented] (CASSANDRA-8502) Static columns returning null for pages after first

[ https://issues.apache.org/jira/browse/CASSANDRA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645878#comment-15645878 ] Richard Low commented on CASSANDRA-8502: Doesn't Dave's patch change behaviour though? We

[jira] [Commented] (CASSANDRA-8502) Static columns returning null for pages after first

[ https://issues.apache.org/jira/browse/CASSANDRA-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15645846#comment-15645846 ] Richard Low commented on CASSANDRA-8502: Can someone remove 2.0.16 from the fix versions,

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427335#comment-15427335 ] Richard Low commented on CASSANDRA-8523: Are you waiting for me to review the dtest PR? >

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416328#comment-15416328 ] Richard Low commented on CASSANDRA-8523: +1 on the 3.9 version too. > Writes should be sent

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15399949#comment-15399949 ] Richard Low commented on CASSANDRA-8523: I'll review the 3.9 version. I'm very much in favour

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398667#comment-15398667 ] Richard Low commented on CASSANDRA-8523: +1 patch looks good. Really like the dtests. >

[jira] [Commented] (CASSANDRA-9641) Occasional timeouts with blockFor=all for LOCAL_QUORUM query

[ https://issues.apache.org/jira/browse/CASSANDRA-9641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15392096#comment-15392096 ] Richard Low commented on CASSANDRA-9641: I couldn't find the root cause. I'll look to see if

[jira] [Commented] (CASSANDRA-12043) Syncing most recent commit in CAS across replicas can cause all CAS queries in the CQL partition to fail

[ https://issues.apache.org/jira/browse/CASSANDRA-12043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15358348#comment-15358348 ] Richard Low commented on CASSANDRA-12043: - Nice detective work [~kohlisankalp] > Syncing

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337328#comment-15337328 ] Richard Low commented on CASSANDRA-8523: It's not those writes that matter - the replacement

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337290#comment-15337290 ] Richard Low commented on CASSANDRA-8523: Thanks! I'm happy to review. > Writes should be sent

[jira] [Commented] (CASSANDRA-8523) Writes should be sent to a replacement node while it is streaming in data

[ https://issues.apache.org/jira/browse/CASSANDRA-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311526#comment-15311526 ] Richard Low commented on CASSANDRA-8523: Without understanding the FD details, this sounds

[jira] [Commented] (CASSANDRA-11903) Serial reads should not include pending endpoints

[ https://issues.apache.org/jira/browse/CASSANDRA-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304341#comment-15304341 ] Richard Low commented on CASSANDRA-11903: - The write CL is increased by 1 for a pending

[jira] [Created] (CASSANDRA-11903) Serial reads should not include pending endpoints

Richard Low created CASSANDRA-11903: --- Summary: Serial reads should not include pending endpoints Key: CASSANDRA-11903 URL: https://issues.apache.org/jira/browse/CASSANDRA-11903 Project: Cassandra

[jira] [Commented] (CASSANDRA-11746) Add per partition rate limiting

[ https://issues.apache.org/jira/browse/CASSANDRA-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284899#comment-15284899 ] Richard Low commented on CASSANDRA-11746: - I think per table via DDL or backed by a system

[jira] [Created] (CASSANDRA-11746) Add per partition rate limiting

Richard Low created CASSANDRA-11746: --- Summary: Add per partition rate limiting Key: CASSANDRA-11746 URL: https://issues.apache.org/jira/browse/CASSANDRA-11746 Project: Cassandra Issue

[jira] [Created] (CASSANDRA-11745) Add bytes limit to queries and paging

Richard Low created CASSANDRA-11745: --- Summary: Add bytes limit to queries and paging Key: CASSANDRA-11745 URL: https://issues.apache.org/jira/browse/CASSANDRA-11745 Project: Cassandra

[jira] [Commented] (CASSANDRA-11547) Add background thread to check for clock drift

[ https://issues.apache.org/jira/browse/CASSANDRA-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15253057#comment-15253057 ] Richard Low commented on CASSANDRA-11547: - Given how critical clocks are to Cassandra I think

[jira] [Commented] (CASSANDRA-11349) MerkleTree mismatch when multiple range tombstones exists for the same partition and interval

[ https://issues.apache.org/jira/browse/CASSANDRA-11349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15222330#comment-15222330 ] Richard Low commented on CASSANDRA-11349: - I'm also not sure how this is meant to fix it.

[jira] [Updated] (CASSANDRA-10643) Implement compaction for a specific token range

[ https://issues.apache.org/jira/browse/CASSANDRA-10643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-10643: Reviewer: Jason Brown Status: Patch Available (was: Open) > Implement

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15181335#comment-15181335 ] Richard Low commented on CASSANDRA-10726: - What do you think [~jbellis] [~slebresne]? > Read

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15122431#comment-15122431 ] Richard Low commented on CASSANDRA-10726: - Actually, isn't the real problem here that

[jira] [Created] (CASSANDRA-11091) Insufficient disk space in memtable flush should trigger disk fail policy

Richard Low created CASSANDRA-11091: --- Summary: Insufficient disk space in memtable flush should trigger disk fail policy Key: CASSANDRA-11091 URL: https://issues.apache.org/jira/browse/CASSANDRA-11091

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092150#comment-15092150 ] Richard Low commented on CASSANDRA-10726: - It would lose a guarantee (which admittedly I

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081929#comment-15081929 ] Richard Low commented on CASSANDRA-10726: - +1 on the option to disable. > Read repair

[jira] [Commented] (CASSANDRA-10887) Pending range calculator gives wrong pending ranges for moves

[ https://issues.apache.org/jira/browse/CASSANDRA-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15064904#comment-15064904 ] Richard Low commented on CASSANDRA-10887: - Is your key 'jdoe' stored on node1? > Pending

[jira] [Created] (CASSANDRA-10887) Pending range calculator gives wrong pending ranges for moves

Richard Low created CASSANDRA-10887: --- Summary: Pending range calculator gives wrong pending ranges for moves Key: CASSANDRA-10887 URL: https://issues.apache.org/jira/browse/CASSANDRA-10887 Project:

[jira] [Commented] (CASSANDRA-10726) Read repair inserts should not be blocking

[ https://issues.apache.org/jira/browse/CASSANDRA-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058576#comment-15058576 ] Richard Low commented on CASSANDRA-10726: - How does it violate consistency? The replica was

[jira] [Created] (CASSANDRA-10726) Read repair inserts should not be blocking

Richard Low created CASSANDRA-10726: --- Summary: Read repair inserts should not be blocking Key: CASSANDRA-10726 URL: https://issues.apache.org/jira/browse/CASSANDRA-10726 Project: Cassandra

[jira] [Commented] (CASSANDRA-10366) Added gossip states can shadow older unseen states

[ https://issues.apache.org/jira/browse/CASSANDRA-10366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804315#comment-14804315 ] Richard Low commented on CASSANDRA-10366: - +1 > Added gossip states can shadow older unseen

[jira] [Updated] (CASSANDRA-9434) If a node loses schema_columns SSTables it could delete all secondary indexes from the schema

[ https://issues.apache.org/jira/browse/CASSANDRA-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-9434: --- Fix Version/s: (was: 2.0.x) 2.2.x 2.1.x If a

[jira] [Commented] (CASSANDRA-9434) If a node loses schema_columns SSTables it could delete all secondary indexes from the schema

[ https://issues.apache.org/jira/browse/CASSANDRA-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702418#comment-14702418 ] Richard Low commented on CASSANDRA-9434: Thanks for the explanation! With 2.0

[jira] [Commented] (CASSANDRA-9434) If a node loses schema_columns SSTables it could delete all secondary indexes from the schema

[ https://issues.apache.org/jira/browse/CASSANDRA-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700697#comment-14700697 ] Richard Low commented on CASSANDRA-9434: Thanks Aleksey. So it sounds like we

[jira] [Commented] (CASSANDRA-9753) LOCAL_QUORUM reads can block cross-DC if there is a digest mismatch

[ https://issues.apache.org/jira/browse/CASSANDRA-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642825#comment-14642825 ] Richard Low commented on CASSANDRA-9753: I agree with Sankalp. This is with

[jira] [Commented] (CASSANDRA-9753) LOCAL_QUORUM reads can block cross-DC if there is a digest mismatch

[ https://issues.apache.org/jira/browse/CASSANDRA-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642881#comment-14642881 ] Richard Low commented on CASSANDRA-9753: Using a remote replica for an eager

[jira] [Commented] (CASSANDRA-9753) LOCAL_QUORUM reads can block cross-DC if there is a digest mismatch

[ https://issues.apache.org/jira/browse/CASSANDRA-9753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14642883#comment-14642883 ] Richard Low commented on CASSANDRA-9753: Actually I take that back. It's not

[jira] [Commented] (CASSANDRA-9827) Add consistency level to tracing ouput

[ https://issues.apache.org/jira/browse/CASSANDRA-9827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14643012#comment-14643012 ] Richard Low commented on CASSANDRA-9827: +1 Can someone commit? Add

[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14625756#comment-14625756 ] Richard Low commented on CASSANDRA-5901: It would be much better to not have

[jira] [Commented] (CASSANDRA-9765) checkForEndpointCollision fails for legitimate collisions

[ https://issues.apache.org/jira/browse/CASSANDRA-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622507#comment-14622507 ] Richard Low commented on CASSANDRA-9765: Yes I can.

[jira] [Created] (CASSANDRA-9765) checkForEndpointCollision fails for legitimate collisions

Richard Low created CASSANDRA-9765: -- Summary: checkForEndpointCollision fails for legitimate collisions Key: CASSANDRA-9765 URL: https://issues.apache.org/jira/browse/CASSANDRA-9765 Project:

[jira] [Created] (CASSANDRA-9753) LOCAL_QUORUM reads can block cross-DC if there is a digest mismatch

Richard Low created CASSANDRA-9753: -- Summary: LOCAL_QUORUM reads can block cross-DC if there is a digest mismatch Key: CASSANDRA-9753 URL: https://issues.apache.org/jira/browse/CASSANDRA-9753

[jira] [Created] (CASSANDRA-9641) Occasional timeouts with blockFor=all for LOCAL_QUORUM query

Richard Low created CASSANDRA-9641: -- Summary: Occasional timeouts with blockFor=all for LOCAL_QUORUM query Key: CASSANDRA-9641 URL: https://issues.apache.org/jira/browse/CASSANDRA-9641 Project:

[jira] [Created] (CASSANDRA-9596) Tombstone timestamps aren't used to skip SSTables while they are still in the memtable

Richard Low created CASSANDRA-9596: -- Summary: Tombstone timestamps aren't used to skip SSTables while they are still in the memtable Key: CASSANDRA-9596 URL: https://issues.apache.org/jira/browse/CASSANDRA-9596

[jira] [Created] (CASSANDRA-9434) If a node loses schema_columns SSTables it could delete all secondary indexes from the schema

Richard Low created CASSANDRA-9434: -- Summary: If a node loses schema_columns SSTables it could delete all secondary indexes from the schema Key: CASSANDRA-9434 URL:

[jira] [Commented] (CASSANDRA-9434) If a node loses schema_columns SSTables it could delete all secondary indexes from the schema

[ https://issues.apache.org/jira/browse/CASSANDRA-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551601#comment-14551601 ] Richard Low commented on CASSANDRA-9434: cc [~iamaleksey] If a node loses

[jira] [Updated] (CASSANDRA-9434) If a node loses schema_columns SSTables it could delete all secondary indexes from the schema

[ https://issues.apache.org/jira/browse/CASSANDRA-9434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-9434: --- Description: It is possible that a single bad node can delete all secondary indexes if it

[jira] [Commented] (CASSANDRA-9183) Failure detector should detect and ignore local pauses

[ https://issues.apache.org/jira/browse/CASSANDRA-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14541008#comment-14541008 ] Richard Low commented on CASSANDRA-9183: Is it possible to get this in 2.1

[jira] [Commented] (CASSANDRA-8336) Add shutdown gossip state to prevent timeouts during rolling restarts

[ https://issues.apache.org/jira/browse/CASSANDRA-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14538198#comment-14538198 ] Richard Low commented on CASSANDRA-8336: How big is your largest QA cluster? I

[jira] [Commented] (CASSANDRA-9183) Failure detector should detect and ignore local pauses

[ https://issues.apache.org/jira/browse/CASSANDRA-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14533030#comment-14533030 ] Richard Low commented on CASSANDRA-9183: +1. Very minor comment: it would be

[jira] [Updated] (CASSANDRA-9280) Streaming connections should bind to the broadcast_address of the node

[ https://issues.apache.org/jira/browse/CASSANDRA-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-9280: --- Since Version: 1.2.0 Streaming connections should bind to the broadcast_address of the

[jira] [Created] (CASSANDRA-9280) Streaming connections should bind to the broadcast_address of the node

Richard Low created CASSANDRA-9280: -- Summary: Streaming connections should bind to the broadcast_address of the node Key: CASSANDRA-9280 URL: https://issues.apache.org/jira/browse/CASSANDRA-9280

[jira] [Commented] (CASSANDRA-8336) Quarantine nodes after receiving the gossip shutdown message

[ https://issues.apache.org/jira/browse/CASSANDRA-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493345#comment-14493345 ] Richard Low commented on CASSANDRA-8336: +1, thanks Brandon! Quarantine

[jira] [Commented] (CASSANDRA-8336) Quarantine nodes after receiving the gossip shutdown message

[ https://issues.apache.org/jira/browse/CASSANDRA-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14341222#comment-14341222 ] Richard Low commented on CASSANDRA-8336: Here it is: {code} ERROR [main]

[jira] [Created] (CASSANDRA-8829) Add extra checks to catch SSTable ref counting bugs

Richard Low created CASSANDRA-8829: -- Summary: Add extra checks to catch SSTable ref counting bugs Key: CASSANDRA-8829 URL: https://issues.apache.org/jira/browse/CASSANDRA-8829 Project: Cassandra

[jira] [Updated] (CASSANDRA-8829) Add extra checks to catch SSTable ref counting bugs

[ https://issues.apache.org/jira/browse/CASSANDRA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-8829: --- Attachment: 8829-2.0.patch Add extra checks to catch SSTable ref counting bugs

[jira] [Commented] (CASSANDRA-8829) Add extra checks to catch SSTable ref counting bugs

[ https://issues.apache.org/jira/browse/CASSANDRA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326321#comment-14326321 ] Richard Low commented on CASSANDRA-8829: Attached patch for 2.0. Add extra

[jira] [Commented] (CASSANDRA-8829) Add extra checks to catch SSTable ref counting bugs

[ https://issues.apache.org/jira/browse/CASSANDRA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326427#comment-14326427 ] Richard Low commented on CASSANDRA-8829: Agreed that the check in

[jira] [Commented] (CASSANDRA-8829) Add extra checks to catch SSTable ref counting bugs

[ https://issues.apache.org/jira/browse/CASSANDRA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14326749#comment-14326749 ] Richard Low commented on CASSANDRA-8829: Attached v2 patch with

[jira] [Updated] (CASSANDRA-8829) Add extra checks to catch SSTable ref counting bugs

[ https://issues.apache.org/jira/browse/CASSANDRA-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-8829: --- Attachment: 8829-2.0-v2.patch Add extra checks to catch SSTable ref counting bugs

[jira] [Commented] (CASSANDRA-8336) Quarantine nodes after receiving the gossip shutdown message

[ https://issues.apache.org/jira/browse/CASSANDRA-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14325170#comment-14325170 ] Richard Low commented on CASSANDRA-8336: v3 works well and I was able to do a

[jira] [Commented] (CASSANDRA-8815) Race in sstable ref counting during streaming failures

[ https://issues.apache.org/jira/browse/CASSANDRA-8815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14325007#comment-14325007 ] Richard Low commented on CASSANDRA-8815: I think we should add some assertions

[jira] [Commented] (CASSANDRA-7968) permissions_validity_in_ms should be settable via JMX

[ https://issues.apache.org/jira/browse/CASSANDRA-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299269#comment-14299269 ] Richard Low commented on CASSANDRA-7968: How is this meant to work? The MBean

[jira] [Commented] (CASSANDRA-7968) permissions_validity_in_ms should be settable via JMX

[ https://issues.apache.org/jira/browse/CASSANDRA-7968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299285#comment-14299285 ] Richard Low commented on CASSANDRA-7968: As Benedict says, there is at least

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14278204#comment-14278204 ] Richard Low commented on CASSANDRA-8414: I tested this on some real workload

[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 ] Richard Low updated CASSANDRA-8414: --- Fix Version/s: 2.0.12 Avoid loops over array backed iterators that call iter.remove()

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14274593#comment-14274593 ] Richard Low commented on CASSANDRA-8414: Only minor nit is that the BitSet can

[jira] [Commented] (CASSANDRA-5913) Nodes with no gossip STATUS shown as UN by nodetool:status

[ https://issues.apache.org/jira/browse/CASSANDRA-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14273930#comment-14273930 ] Richard Low commented on CASSANDRA-5913: I have seen this on 1.2.19 and 2.0.9.

[jira] [Commented] (CASSANDRA-8515) Hang at startup when no commitlog space

[ https://issues.apache.org/jira/browse/CASSANDRA-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14271668#comment-14271668 ] Richard Low commented on CASSANDRA-8515: I think #5737 was marked as invalid

[jira] [Comment Edited] (CASSANDRA-8515) Hang at startup when no commitlog space

[ https://issues.apache.org/jira/browse/CASSANDRA-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14271668#comment-14271668 ] Richard Low edited comment on CASSANDRA-8515 at 1/9/15 6:38 PM:

[jira] [Updated] (CASSANDRA-8515) Hang at startup when no commitlog space

[ https://issues.apache.org/jira/browse/CASSANDRA-8515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-8515: --- Description: If the commit log directory has no free space, Cassandra hangs on startup.

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14268075#comment-14268075 ] Richard Low commented on CASSANDRA-8414: +1 on 2.0 v5. Do you have a 2.1

[jira] [Created] (CASSANDRA-8515) Hang at startup when no commitlog space

Richard Low created CASSANDRA-8515: -- Summary: Hang at startup when no commitlog space Key: CASSANDRA-8515 URL: https://issues.apache.org/jira/browse/CASSANDRA-8515 Project: Cassandra Issue

[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 ] Richard Low updated CASSANDRA-8414: --- Reviewer: Richard Low Avoid loops over array backed iterators that call iter.remove()

[jira] [Commented] (CASSANDRA-5737) CassandraDaemon - recent unsafe memory access operation in compiled Java code

[ https://issues.apache.org/jira/browse/CASSANDRA-5737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251018#comment-14251018 ] Richard Low commented on CASSANDRA-5737: I get exactly this error when the

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14246961#comment-14246961 ] Richard Low commented on CASSANDRA-8414: Thanks for writing the patch! A few

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14237987#comment-14237987 ] Richard Low commented on CASSANDRA-8414: Yes, I can review this week. Avoid

[jira] [Created] (CASSANDRA-8414) Compaction is O(n^2) when deleting lots of tombstones

Richard Low created CASSANDRA-8414: -- Summary: Compaction is O(n^2) when deleting lots of tombstones Key: CASSANDRA-8414 URL: https://issues.apache.org/jira/browse/CASSANDRA-8414 Project: Cassandra

[jira] [Created] (CASSANDRA-8416) AssertionError 'Incoherent new size -1' during hints compaction

Richard Low created CASSANDRA-8416: -- Summary: AssertionError 'Incoherent new size -1' during hints compaction Key: CASSANDRA-8416 URL: https://issues.apache.org/jira/browse/CASSANDRA-8416 Project:

[jira] [Created] (CASSANDRA-8121) Audit acquire/release SSTable references

Richard Low created CASSANDRA-8121: -- Summary: Audit acquire/release SSTable references Key: CASSANDRA-8121 URL: https://issues.apache.org/jira/browse/CASSANDRA-8121 Project: Cassandra Issue

[jira] [Created] (CASSANDRA-8113) Gossip should ignore generation numbers too far in the future

Richard Low created CASSANDRA-8113: -- Summary: Gossip should ignore generation numbers too far in the future Key: CASSANDRA-8113 URL: https://issues.apache.org/jira/browse/CASSANDRA-8113 Project:

[jira] [Commented] (CASSANDRA-4206) AssertionError: originally calculated column size of 629444349 but now it is 588008950

[ https://issues.apache.org/jira/browse/CASSANDRA-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14107031#comment-14107031 ] Richard Low commented on CASSANDRA-4206: The root cause of this in 1.2 is

[jira] [Created] (CASSANDRA-7808) LazilyCompactedRow incorrectly handles row tombstones

Richard Low created CASSANDRA-7808: -- Summary: LazilyCompactedRow incorrectly handles row tombstones Key: CASSANDRA-7808 URL: https://issues.apache.org/jira/browse/CASSANDRA-7808 Project: Cassandra

[jira] [Updated] (CASSANDRA-7808) LazilyCompactedRow incorrectly handles row tombstones

[ https://issues.apache.org/jira/browse/CASSANDRA-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-7808: --- Attachment: 7808-v1.diff LazilyCompactedRow incorrectly handles row tombstones

[jira] [Commented] (CASSANDRA-7808) LazilyCompactedRow incorrectly handles row tombstones

[ https://issues.apache.org/jira/browse/CASSANDRA-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14104877#comment-14104877 ] Richard Low commented on CASSANDRA-7808: I attached a patch which I think

[jira] [Commented] (CASSANDRA-7808) LazilyCompactedRow incorrectly handles row tombstones

[ https://issues.apache.org/jira/browse/CASSANDRA-7808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14105018#comment-14105018 ] Richard Low commented on CASSANDRA-7808: Sorry, I got my scope wrong. The

[jira] [Commented] (CASSANDRA-7663) Removing a seed causes previously removed seeds to reappear

[ https://issues.apache.org/jira/browse/CASSANDRA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14086574#comment-14086574 ] Richard Low commented on CASSANDRA-7663: +1 on v2, thanks! Removing a seed

[jira] [Commented] (CASSANDRA-7663) Removing a seed causes previously removed seeds to reappear

[ https://issues.apache.org/jira/browse/CASSANDRA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14082613#comment-14082613 ] Richard Low commented on CASSANDRA-7663: Thanks! Removing a seed causes

[jira] [Commented] (CASSANDRA-7663) Removing a seed causes previously removed seeds to reappear

[ https://issues.apache.org/jira/browse/CASSANDRA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14083258#comment-14083258 ] Richard Low commented on CASSANDRA-7663: Actually there's a potential problem

[jira] [Created] (CASSANDRA-7663) Removing a seed causes previously removed seeds to reappear

Richard Low created CASSANDRA-7663: -- Summary: Removing a seed causes previously removed seeds to reappear Key: CASSANDRA-7663 URL: https://issues.apache.org/jira/browse/CASSANDRA-7663 Project:

[jira] [Created] (CASSANDRA-7591) Add read and write metrics for each consistency level

Richard Low created CASSANDRA-7591: -- Summary: Add read and write metrics for each consistency level Key: CASSANDRA-7591 URL: https://issues.apache.org/jira/browse/CASSANDRA-7591 Project: Cassandra

[jira] [Updated] (CASSANDRA-7591) Add per consistency level read and write metrics

[ https://issues.apache.org/jira/browse/CASSANDRA-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low updated CASSANDRA-7591: --- Summary: Add per consistency level read and write metrics (was: Add read and write

[jira] [Resolved] (CASSANDRA-7591) Add per consistency level read and write metrics

[ https://issues.apache.org/jira/browse/CASSANDRA-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Low resolved CASSANDRA-7591. Resolution: Duplicate Dupe of CASSANDRA-7384. Add per consistency level read and

[jira] [Commented] (CASSANDRA-7591) Add per consistency level read and write metrics

[ https://issues.apache.org/jira/browse/CASSANDRA-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070941#comment-14070941 ] Richard Low commented on CASSANDRA-7591: And I've just found CASSANDRA-7384.

[jira] [Commented] (CASSANDRA-7384) Collect metrics on queries by consistency level

[ https://issues.apache.org/jira/browse/CASSANDRA-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070960#comment-14070960 ] Richard Low commented on CASSANDRA-7384: Having relative counts per

[jira] [Commented] (CASSANDRA-5901) Bootstrap should also make the data consistent on the new node

[ https://issues.apache.org/jira/browse/CASSANDRA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070988#comment-14070988 ] Richard Low commented on CASSANDRA-5901: In particular, host replacement can

[jira] [Created] (CASSANDRA-7592) Ownership changes can violate consistency

Richard Low created CASSANDRA-7592: -- Summary: Ownership changes can violate consistency Key: CASSANDRA-7592 URL: https://issues.apache.org/jira/browse/CASSANDRA-7592 Project: Cassandra

[jira] [Commented] (CASSANDRA-6751) Setting -Dcassandra.fd_initial_value_ms Results in NPE

[ https://issues.apache.org/jira/browse/CASSANDRA-6751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068158#comment-14068158 ] Richard Low commented on CASSANDRA-6751: This issue also affects 2.0 branch

[jira] [Commented] (CASSANDRA-7307) New nodes mark dead nodes as up for 10 minutes

[ https://issues.apache.org/jira/browse/CASSANDRA-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14036328#comment-14036328 ] Richard Low commented on CASSANDRA-7307: bq. For bootstrap? Let me be clear,

  1   2   >