[jira] [Commented] (CASSANDRA-11738) Re-think the use of Severity in the DynamicEndpointSnitch calculation

[ https://issues.apache.org/jira/browse/CASSANDRA-11738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290389#comment-15290389 ] Jonathan Ellis commented on CASSANDRA-11738: It could, but how would you decide when to

[jira] [Commented] (CASSANDRA-11055) C*2.1 cqlsh DESCRIBE KEYSPACE ( or TABLE ) returns 'NoneType' object has no attribute 'replace'

[ https://issues.apache.org/jira/browse/CASSANDRA-11055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290375#comment-15290375 ] Stefania commented on CASSANDRA-11055: -- Thanks for opening

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290374#comment-15290374 ] stone commented on CASSANDRA-11569: --- see nodeLatency.PNG,I change latency from 90ms to 30ms at

[jira] [Updated] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stone updated CASSANDRA-11569: -- Attachment: nodeLatency.PNG > Track message latency across DCs >

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290370#comment-15290370 ] stone commented on CASSANDRA-11569: --- thx,what I mean is the value of crossNodeLatency is not

[jira] [Commented] (CASSANDRA-11503) Need a tool to detect what percentage of SSTables on a node have been repaired when using incremental repairs.

[ https://issues.apache.org/jira/browse/CASSANDRA-11503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290359#comment-15290359 ] Chris Lohfink commented on CASSANDRA-11503: --- Added it to each table, and a global one. The

[jira] [Updated] (CASSANDRA-11503) Need a tool to detect what percentage of SSTables on a node have been repaired when using incremental repairs.

[ https://issues.apache.org/jira/browse/CASSANDRA-11503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lohfink updated CASSANDRA-11503: -- Attachment: CASSANDRA-11503v2.patch > Need a tool to detect what percentage of

[jira] [Commented] (CASSANDRA-11272) NullPointerException (NPE) during bootstrap startup in StorageService.java

[ https://issues.apache.org/jira/browse/CASSANDRA-11272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290293#comment-15290293 ] Joel Knighton commented on CASSANDRA-11272: --- [~ifesdjeen] - why log e.getCause() instead of

[jira] [Resolved] (CASSANDRA-11557) Download page must not link to snapshots / nightly builds

[ https://issues.apache.org/jira/browse/CASSANDRA-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved CASSANDRA-11557. -- Resolution: Fixed Thought I could move the issue; it appears not > Download page must not link to

[jira] [Reopened] (CASSANDRA-11557) Download page must not link to snapshots / nightly builds

[ https://issues.apache.org/jira/browse/CASSANDRA-11557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened CASSANDRA-11557: -- > Download page must not link to snapshots / nightly builds >

[jira] [Commented] (CASSANDRA-11731) dtest failure in pushed_notifications_test.TestPushedNotifications.move_single_node_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290243#comment-15290243 ] Stefania commented on CASSANDRA-11731: -- I think this line here: {code}

[jira] [Commented] (CASSANDRA-11191) Support more flexible offline access to SSTable

[ https://issues.apache.org/jira/browse/CASSANDRA-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290190#comment-15290190 ] Yuki Morishita commented on CASSANDRA-11191: My initial approach will be to create

[jira] [Comment Edited] (CASSANDRA-11055) C*2.1 cqlsh DESCRIBE KEYSPACE ( or TABLE ) returns 'NoneType' object has no attribute 'replace'

[ https://issues.apache.org/jira/browse/CASSANDRA-11055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290104#comment-15290104 ] Adam Holmberg edited comment on CASSANDRA-11055 at 5/18/16 11:47 PM:

[jira] [Commented] (CASSANDRA-11055) C*2.1 cqlsh DESCRIBE KEYSPACE ( or TABLE ) returns 'NoneType' object has no attribute 'replace'

[ https://issues.apache.org/jira/browse/CASSANDRA-11055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290104#comment-15290104 ] Adam Holmberg commented on CASSANDRA-11055: --- I did miss this. Thanks. bq. Due to the API

[jira] [Updated] (CASSANDRA-9530) SSTable corruption can trigger OOM

[ https://issues.apache.org/jira/browse/CASSANDRA-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-9530: --- Reviewer: Stefania > SSTable corruption can trigger OOM >

[jira] [Updated] (CASSANDRA-11580) remove DatabaseDescriptor dependency from SegmentedFile

[ https://issues.apache.org/jira/browse/CASSANDRA-11580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-11580: Reviewer: Stefania > remove DatabaseDescriptor dependency from SegmentedFile >

[jira] [Updated] (CASSANDRA-11670) Error while waiting on bootstrap to complete. Bootstrap will have to be restarted. Stream failed

[ https://issues.apache.org/jira/browse/CASSANDRA-11670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-11670: Status: Patch Available (was: In Progress) > Error while waiting on bootstrap to

[jira] [Commented] (CASSANDRA-11670) Error while waiting on bootstrap to complete. Bootstrap will have to be restarted. Stream failed

[ https://issues.apache.org/jira/browse/CASSANDRA-11670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15290085#comment-15290085 ] Paulo Motta commented on CASSANDRA-11670: - Attaching initial patch for review. Basic idea is

[jira] [Updated] (CASSANDRA-11842) Unbounded commit log file growth

[ https://issues.apache.org/jira/browse/CASSANDRA-11842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated CASSANDRA-11842: - Description: Today I noticed that 2 nodes in a 54 node cluster have been

[jira] [Created] (CASSANDRA-11842) Unbounded commit log file growth

Andrew Jorgensen created CASSANDRA-11842: Summary: Unbounded commit log file growth Key: CASSANDRA-11842 URL: https://issues.apache.org/jira/browse/CASSANDRA-11842 Project: Cassandra

[jira] [Updated] (CASSANDRA-11842) Unbounded commit log file growth

[ https://issues.apache.org/jira/browse/CASSANDRA-11842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Jorgensen updated CASSANDRA-11842: - Description: Today I noticed that 2 nodes in a 54 node cluster have been

[Cassandra Wiki] Update of "GettingStarted" by TylerHobbs

Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification. The "GettingStarted" page has been changed by TylerHobbs: https://wiki.apache.org/cassandra/GettingStarted?action=diff=107=108 Comment: Specify that Java 8 is required for Cassandra

[jira] [Commented] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289824#comment-15289824 ] Benedict commented on CASSANDRA-9669: - Committed as 2837ec65b91abd78ec1bb37f1d69565b976e42e6 > If

[jira] [Updated] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedict updated CASSANDRA-9669: Resolution: Fixed Reproduced In: 2.1.7, 2.0.16, 1.2.19 (was: 1.2.19, 2.0.16, 2.1.7)

[jira] [Commented] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289810#comment-15289810 ] Chris Lohfink commented on CASSANDRA-11569: --- bq. I will got an error as the crosslatency is

[jira] [Updated] (CASSANDRA-11569) Track message latency across DCs

[ https://issues.apache.org/jira/browse/CASSANDRA-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Lohfink updated CASSANDRA-11569: -- Attachment: CASSANDRA-11569v2.txt > Track message latency across DCs >

[6/8] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.7

Merge branch 'cassandra-3.0' into cassandra-3.7 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/326a263f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/326a263f Diff:

[3/8] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

Merge branch 'cassandra-2.2' into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/958183fa Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/958183fa Diff:

[8/8] cassandra git commit: Merge branch 'cassandra-3.7' into trunk

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

[5/8] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

Merge branch 'cassandra-2.2' into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5a5d0a1e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5a5d0a1e Diff:

[2/8] cassandra git commit: merge from 2.1

merge from 2.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/be653932 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/be653932 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/be653932

[7/8] cassandra git commit: Merge branch 'cassandra-3.0' into cassandra-3.7

Merge branch 'cassandra-3.0' into cassandra-3.7 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/326a263f Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/326a263f Diff:

[4/8] cassandra git commit: Fix deadlock on truncation with secondary index.

Fix deadlock on truncation with secondary index. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2837ec65 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2837ec65 Diff:

[1/8] cassandra git commit: Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834

Repository: cassandra Updated Branches: refs/heads/cassandra-3.7 424b0b9e0 -> 326a263f4 refs/heads/trunk bc7846680 -> beb6464c0 Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834

[6/6] cassandra git commit: Merge branch 'cassandra-3.0' into trunk

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

[3/6] cassandra git commit: Fix deadlock on truncation with secondary index.

Fix deadlock on truncation with secondary index. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2837ec65 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2837ec65 Diff:

[4/6] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

Merge branch 'cassandra-2.2' into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5a5d0a1e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5a5d0a1e Diff:

[2/6] cassandra git commit: Fix deadlock on truncation with secondary index.

Fix deadlock on truncation with secondary index. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/2837ec65 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/2837ec65 Diff:

[1/6] cassandra git commit: Fix deadlock on truncation with secondary index.

Repository: cassandra Updated Branches: refs/heads/cassandra-2.2 be653932d -> 2837ec65b refs/heads/cassandra-3.0 958183fad -> 5a5d0a1eb refs/heads/trunk 5bdf3184b -> bc7846680 Fix deadlock on truncation with secondary index. Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo

[5/6] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

Merge branch 'cassandra-2.2' into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/5a5d0a1e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/5a5d0a1e Diff:

[jira] [Commented] (CASSANDRA-10786) Include hash of result set metadata in prepared statement id

[ https://issues.apache.org/jira/browse/CASSANDRA-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289767#comment-15289767 ] Robert Stupp commented on CASSANDRA-10786: -- A v5 is fine IMO. But I'd suggest to include the

[jira] [Commented] (CASSANDRA-11750) Offline scrub should not abort when it hits corruption

[ https://issues.apache.org/jira/browse/CASSANDRA-11750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289741#comment-15289741 ] Yuki Morishita commented on CASSANDRA-11750: So, to be clear, the issue happens when one

[jira] [Commented] (CASSANDRA-11760) dtest failure in TestCQLNodes3RF3_Upgrade_current_2_2_x_To_next_3_x.more_user_types_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289730#comment-15289730 ] Tyler Hobbs commented on CASSANDRA-11760: - I believe this has the same cause as

[jira] [Resolved] (CASSANDRA-11613) dtest failure in upgrade_tests.cql_tests.TestCQLNodes2RF1_2_2_HEAD_UpTo_Trunk.more_user_types_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs resolved CASSANDRA-11613. - Resolution: Fixed Reproduced In: (was: 3.6) Thanks, committed with the nits

[1/3] cassandra git commit: Freeze UDTs and nested UDTs/collections during schema upgrade

Repository: cassandra Updated Branches: refs/heads/trunk 0f483d8ff -> 5bdf3184b Freeze UDTs and nested UDTs/collections during schema upgrade Patch by Tyler Hobbs; reviewed by Benjamin Lerer for CASSANDRA-11613 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

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

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

[2/3] cassandra git commit: Merge branch 'cassandra-3.6' into cassandra-3.7

Merge branch 'cassandra-3.6' into cassandra-3.7 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/424b0b9e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/424b0b9e Diff:

[1/2] cassandra git commit: Freeze UDTs and nested UDTs/collections during schema upgrade

Repository: cassandra Updated Branches: refs/heads/cassandra-3.7 ad546832f -> 424b0b9e0 Freeze UDTs and nested UDTs/collections during schema upgrade Patch by Tyler Hobbs; reviewed by Benjamin Lerer for CASSANDRA-11613 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[2/2] cassandra git commit: Merge branch 'cassandra-3.6' into cassandra-3.7

Merge branch 'cassandra-3.6' into cassandra-3.7 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/424b0b9e Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/424b0b9e Diff:

cassandra git commit: Freeze UDTs and nested UDTs/collections during schema upgrade

Repository: cassandra Updated Branches: refs/heads/cassandra-3.6 c17cbe187 -> dee84ccc5 Freeze UDTs and nested UDTs/collections during schema upgrade Patch by Tyler Hobbs; reviewed by Benjamin Lerer for CASSANDRA-11613 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Commented] (CASSANDRA-11738) Re-think the use of Severity in the DynamicEndpointSnitch calculation

[ https://issues.apache.org/jira/browse/CASSANDRA-11738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289722#comment-15289722 ] Robert Stupp commented on CASSANDRA-11738: -- Could the sum of all pending+active requests be

[jira] [Commented] (CASSANDRA-11837) dtest failure in topology_test.TestTopology.simple_decommission_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289714#comment-15289714 ] Philip Thompson commented on CASSANDRA-11837: - Testing a fix here:

[jira] [Assigned] (CASSANDRA-11837) dtest failure in topology_test.TestTopology.simple_decommission_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson reassigned CASSANDRA-11837: --- Assignee: Philip Thompson (was: DS Test Eng) > dtest failure in

[jira] [Updated] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-9669: --- Status: Ready to Commit (was: Patch Available) > If sstable flushes complete out

[jira] [Updated] (CASSANDRA-11840) Set a more conservative default to streaming_socket_timeout_in_ms

[ https://issues.apache.org/jira/browse/CASSANDRA-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-11840: Status: Patch Available (was: Open) > Set a more conservative default to

[jira] [Updated] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-9669: --- Reproduced In: 2.1.7, 2.0.16, 1.2.19 (was: 1.2.19, 2.0.16, 2.1.7)

[jira] [Commented] (CASSANDRA-11840) Set a more conservative default to streaming_socket_timeout_in_ms

[ https://issues.apache.org/jira/browse/CASSANDRA-11840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289711#comment-15289711 ] Paulo Motta commented on CASSANDRA-11840: - Attaching patch that sets default

[jira] [Commented] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289709#comment-15289709 ] Benedict commented on CASSANDRA-9669: - Sure; +1 > If sstable flushes complete out of order, on

[jira] [Commented] (CASSANDRA-10786) Include hash of result set metadata in prepared statement id

[ https://issues.apache.org/jira/browse/CASSANDRA-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289708#comment-15289708 ] Tyler Hobbs commented on CASSANDRA-10786: - I agree that it's best to change this behavior as

[jira] [Updated] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-9669: --- Reviewer: (was: Branimir Lambov) > If sstable flushes complete out of order, on

[jira] [Updated] (CASSANDRA-10786) Include hash of result set metadata in prepared statement id

[ https://issues.apache.org/jira/browse/CASSANDRA-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs updated CASSANDRA-10786: Labels: client-impacting protocolv5 (was: client-impacting) > Include hash of result

[jira] [Commented] (CASSANDRA-11731) dtest failure in pushed_notifications_test.TestPushedNotifications.move_single_node_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289703#comment-15289703 ] Philip Thompson commented on CASSANDRA-11731: - [~stefania], you worked on CASSANDRA-8516,

[jira] [Commented] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289699#comment-15289699 ] Joshua McKenzie commented on CASSANDRA-9669: [~benedict]: Care to take review of these

[jira] [Resolved] (CASSANDRA-8343) Secondary index creation causes moves/bootstraps to fail

[ https://issues.apache.org/jira/browse/CASSANDRA-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta resolved CASSANDRA-8343. Resolution: Fixed > Secondary index creation causes moves/bootstraps to fail >

[jira] [Updated] (CASSANDRA-9669) If sstable flushes complete out of order, on restart we can fail to replay necessary commit log records

[ https://issues.apache.org/jira/browse/CASSANDRA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-9669: --- Assignee: Branimir Lambov (was: Benedict) > If sstable flushes complete out of

[jira] [Commented] (CASSANDRA-11483) Enhance sstablemetadata

[ https://issues.apache.org/jira/browse/CASSANDRA-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289694#comment-15289694 ] Jeremiah Jordan commented on CASSANDRA-11483: - +1 for defaulting the colors and unicode

[jira] [Created] (CASSANDRA-11839) Active streams fail with SocketTimeoutException

Paulo Motta created CASSANDRA-11839: --- Summary: Active streams fail with SocketTimeoutException Key: CASSANDRA-11839 URL: https://issues.apache.org/jira/browse/CASSANDRA-11839 Project: Cassandra

[jira] [Commented] (CASSANDRA-10786) Include hash of result set metadata in prepared statement id

[ https://issues.apache.org/jira/browse/CASSANDRA-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289691#comment-15289691 ] Robert Stupp commented on CASSANDRA-10786: -- I'm +1 on this with a new protocol version (or

[jira] [Created] (CASSANDRA-11840) Set a more conservative default to streaming_socket_timeout_in_ms

Paulo Motta created CASSANDRA-11840: --- Summary: Set a more conservative default to streaming_socket_timeout_in_ms Key: CASSANDRA-11840 URL: https://issues.apache.org/jira/browse/CASSANDRA-11840

[jira] [Created] (CASSANDRA-11841) Add keep-alive to stream protocol

Paulo Motta created CASSANDRA-11841: --- Summary: Add keep-alive to stream protocol Key: CASSANDRA-11841 URL: https://issues.apache.org/jira/browse/CASSANDRA-11841 Project: Cassandra Issue

[jira] [Commented] (CASSANDRA-11826) Repairs failing for some of bigger tables

[ https://issues.apache.org/jira/browse/CASSANDRA-11826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289675#comment-15289675 ] Paulo Motta commented on CASSANDRA-11826: - Thanks for the report. Will close this as

[jira] [Commented] (CASSANDRA-8343) Secondary index creation causes moves/bootstraps to fail

[ https://issues.apache.org/jira/browse/CASSANDRA-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289672#comment-15289672 ] Paulo Motta commented on CASSANDRA-8343: Closing as duplicate of more general ticket

[jira] [Resolved] (CASSANDRA-11826) Repairs failing for some of bigger tables

[ https://issues.apache.org/jira/browse/CASSANDRA-11826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta resolved CASSANDRA-11826. - Resolution: Duplicate > Repairs failing for some of bigger tables >

[jira] [Commented] (CASSANDRA-10786) Include hash of result set metadata in prepared statement id

[ https://issues.apache.org/jira/browse/CASSANDRA-10786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289652#comment-15289652 ] Alex Petrov commented on CASSANDRA-10786: - [~adutra] has also proposed to make a toggle

[jira] [Updated] (CASSANDRA-11838) dtest failure in largecolumn_test:TestLargeColumn.cleanup_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-11838: Reproduced In: 3.6 > dtest failure in

[jira] [Updated] (CASSANDRA-11838) dtest failure in largecolumn_test:TestLargeColumn.cleanup_test

[ https://issues.apache.org/jira/browse/CASSANDRA-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Thompson updated CASSANDRA-11838: Labels: dtest (was: ) > dtest failure in

[jira] [Created] (CASSANDRA-11838) dtest failure in largecolumn_test:TestLargeColumn.cleanup_test

Philip Thompson created CASSANDRA-11838: --- Summary: dtest failure in largecolumn_test:TestLargeColumn.cleanup_test Key: CASSANDRA-11838 URL: https://issues.apache.org/jira/browse/CASSANDRA-11838

[jira] [Created] (CASSANDRA-11837) dtest failure in topology_test.TestTopology.simple_decommission_test

Philip Thompson created CASSANDRA-11837: --- Summary: dtest failure in topology_test.TestTopology.simple_decommission_test Key: CASSANDRA-11837 URL: https://issues.apache.org/jira/browse/CASSANDRA-11837

[jira] [Commented] (CASSANDRA-11686) dtest failure in replication_test.SnitchConfigurationUpdateTest.test_rf_expand_gossiping_property_file_snitch_multi_dc

[ https://issues.apache.org/jira/browse/CASSANDRA-11686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289436#comment-15289436 ] Philip Thompson commented on CASSANDRA-11686: - Looking at the logs for this failure of

[jira] [Created] (CASSANDRA-11836) dtest failure in repair_tests.repair_test.TestRepair.thread_count_repair_test

Philip Thompson created CASSANDRA-11836: --- Summary: dtest failure in repair_tests.repair_test.TestRepair.thread_count_repair_test Key: CASSANDRA-11836 URL:

[jira] [Created] (CASSANDRA-11835) dtest failure in replace_address_test.TestReplaceAddress.replace_with_reset_resume_state_test

Philip Thompson created CASSANDRA-11835: --- Summary: dtest failure in replace_address_test.TestReplaceAddress.replace_with_reset_resume_state_test Key: CASSANDRA-11835 URL:

[08/10] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

Merge branch 'cassandra-2.2' into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/958183fa Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/958183fa Diff:

[jira] [Assigned] (CASSANDRA-11831) Ability to disable purgeable tombstone check via startup flag

[ https://issues.apache.org/jira/browse/CASSANDRA-11831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson reassigned CASSANDRA-11831: --- Assignee: Marcus Eriksson > Ability to disable purgeable tombstone

[jira] [Updated] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-11834: --- Resolution: Fixed Fix Version/s: 2.2.7 Status: Resolved (was:

[07/10] cassandra git commit: merge from 2.1

merge from 2.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/be653932 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/be653932 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/be653932

[09/10] cassandra git commit: Merge branch 'cassandra-2.2' into cassandra-3.0

Merge branch 'cassandra-2.2' into cassandra-3.0 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/958183fa Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/958183fa Diff:

[05/10] cassandra git commit: merge from 2.1

merge from 2.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/be653932 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/be653932 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/be653932

[03/10] cassandra git commit: Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834

Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/00f25401 Tree:

[02/10] cassandra git commit: Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834

Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/00f25401 Tree:

[06/10] cassandra git commit: merge from 2.1

merge from 2.1 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/be653932 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/be653932 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/be653932

[04/10] cassandra git commit: Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834

Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/00f25401 Tree:

[01/10] cassandra git commit: Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone patch by jbellis; reviewed by marcuse for CASSANDRA-11834

Repository: cassandra Updated Branches: refs/heads/cassandra-2.1 9359af2ea -> 00f25401c refs/heads/cassandra-2.2 89344f182 -> be653932d refs/heads/cassandra-3.0 f73b48502 -> 958183fad refs/heads/trunk 050516c53 -> 0f483d8ff Don't compute expensive MaxPurgeableTimestamp until we've

[10/10] cassandra git commit: Merge branch 'cassandra-3.0' into trunk

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

[jira] [Updated] (CASSANDRA-11679) Cassandra Driver returns different number of results depending on fetchsize

[ https://issues.apache.org/jira/browse/CASSANDRA-11679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-11679: --- Fix Version/s: (was: 2.1.x) 2.1.15 > Cassandra Driver

[jira] [Updated] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-11834: Reviewer: Marcus Eriksson > Don't compute expensive MaxPurgeableTimestamp

[jira] [Commented] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15289353#comment-15289353 ] Marcus Eriksson commented on CASSANDRA-11834: - +1 > Don't compute expensive

[jira] [Updated] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-11834: --- Assignee: Jonathan Ellis Status: Patch Available (was: Open) > Don't

[jira] [Updated] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-11834: --- Priority: Minor (was: Major) > Don't compute expensive MaxPurgeableTimestamp

[jira] [Updated] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

[ https://issues.apache.org/jira/browse/CASSANDRA-11834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-11834: --- Attachment: 11834.txt Trivial patch attached. > Don't compute expensive

[jira] [Created] (CASSANDRA-11834) Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone

Jonathan Ellis created CASSANDRA-11834: -- Summary: Don't compute expensive MaxPurgeableTimestamp until we've verified there's an expired tombstone Key: CASSANDRA-11834 URL:

  1   2   >