[jira] [Updated] (CASSANDRA-14527) Real time bad query logging framework

[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Summary: Real time bad query logging framework (was: Real time

[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework

[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: Debugging Cassandra performance problems in really

[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework

[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: Debugging Cassandra performance problems in really

[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework

[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: Debugging Cassandra performance problems in really

[jira] [Updated] (CASSANDRA-14527) Real time Bad query logging framework

[ https://issues.apache.org/jira/browse/CASSANDRA-14527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaydeepkumar Chovatia updated CASSANDRA-14527: -- Description: Debugging Cassandra performance problems in really

[jira] [Commented] (CASSANDRA-14056) Many dtests fail with ConfigurationException: offheap_objects are not available in 3.0 when OFFHEAP_MEMTABLES="true"

[ https://issues.apache.org/jira/browse/CASSANDRA-14056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517744#comment-16517744 ] Alex Lourie commented on CASSANDRA-14056: - Hey [~jasobrown] [~mkjellman], could you spare

[jira] [Commented] (CASSANDRA-14054) testRegularColumnTimestampUpdates - org.apache.cassandra.cql3.ViewTest is flaky: expected <2> but got <1>

[ https://issues.apache.org/jira/browse/CASSANDRA-14054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517743#comment-16517743 ] Alex Lourie commented on CASSANDRA-14054: - [~mkjellman] This one is laying around for

[jira] [Commented] (CASSANDRA-7814) enable describe on indices

[ https://issues.apache.org/jira/browse/CASSANDRA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517721#comment-16517721 ] Nate McCall commented on CASSANDRA-7814: [~ptbannister] If you narrowed in on the cause of a

[jira] [Commented] (CASSANDRA-7814) enable describe on indices

[ https://issues.apache.org/jira/browse/CASSANDRA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517653#comment-16517653 ] Patrick Bannister commented on CASSANDRA-7814: -- Is it a requirement that the output of

[jira] [Commented] (CASSANDRA-14515) Short read protection in presence of almost-purgeable range tombstones may cause permanent data loss

[ https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517649#comment-16517649 ] C. Scott Andreas commented on CASSANDRA-14515: -- Thanks for the quick review! [~beobal],

[jira] [Commented] (CASSANDRA-14515) Short read protection in presence of almost-purgeable range tombstones may cause permanent data loss

[ https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517634#comment-16517634 ] Blake Eggleston commented on CASSANDRA-14515: - +1, assuming the tests look good. Also,

[jira] [Created] (CASSANDRA-14531) Only include data owned by the node in totals for repaired, un-repaired and pending repair.

Matt Byrd created CASSANDRA-14531: - Summary: Only include data owned by the node in totals for repaired, un-repaired and pending repair. Key: CASSANDRA-14531 URL:

[jira] [Assigned] (CASSANDRA-14531) Only include data owned by the node in totals for repaired, un-repaired and pending repair.

[ https://issues.apache.org/jira/browse/CASSANDRA-14531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Byrd reassigned CASSANDRA-14531: - Assignee: Matt Byrd > Only include data owned by the node in totals for repaired,

[jira] [Updated] (CASSANDRA-14515) Short read protection in presence of almost-purgeable range tombstones may cause permanent data loss

[ https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-14515: -- Status: Patch Available (was: Open) > Short read protection in presence

[jira] [Commented] (CASSANDRA-14515) Short read protection in presence of almost-purgeable range tombstones may cause permanent data loss

[ https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517629#comment-16517629 ] Aleksey Yeschenko commented on CASSANDRA-14515: --- [3.11

[jira] [Commented] (CASSANDRA-14515) Short read protection in presence of almost-purgeable range tombstones may cause permanent data loss

[ https://issues.apache.org/jira/browse/CASSANDRA-14515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517612#comment-16517612 ] Aleksey Yeschenko commented on CASSANDRA-14515: --- 3.0 branch

[jira] [Commented] (CASSANDRA-14495) Memory Leak /High Memory usage post 3.11.2 upgrade

[ https://issues.apache.org/jira/browse/CASSANDRA-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517453#comment-16517453 ] Chris Lohfink commented on CASSANDRA-14495: --- something like {{fgrep "stopped: [1-9]"

[jira] [Commented] (CASSANDRA-14525) streaming failure during bootstrap makes new node into inconsistent state

[ https://issues.apache.org/jira/browse/CASSANDRA-14525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517407#comment-16517407 ] Jaydeepkumar Chovatia commented on CASSANDRA-14525: --- I agree there are few

[jira] [Updated] (CASSANDRA-12526) For LCS, single SSTable up-level is handled inefficiently

[ https://issues.apache.org/jira/browse/CASSANDRA-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-12526: Resolution: Fixed Status: Resolved (was: Ready to Commit) > For LCS, single

[jira] [Commented] (CASSANDRA-14495) Memory Leak /High Memory usage post 3.11.2 upgrade

[ https://issues.apache.org/jira/browse/CASSANDRA-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517325#comment-16517325 ] Abdul Patel commented on CASSANDRA-14495: - i have gc log , it doesnt  show much of full

[jira] [Commented] (CASSANDRA-14495) Memory Leak /High Memory usage post 3.11.2 upgrade

[ https://issues.apache.org/jira/browse/CASSANDRA-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517313#comment-16517313 ] Abdul Patel commented on CASSANDRA-14495: - We still got 80% and abover memory usage alert

[jira] [Commented] (CASSANDRA-14495) Memory Leak /High Memory usage post 3.11.2 upgrade

[ https://issues.apache.org/jira/browse/CASSANDRA-14495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517317#comment-16517317 ] Chris Lohfink commented on CASSANDRA-14495: --- As mentioned before, 80% memory usage is not

[jira] [Commented] (CASSANDRA-12526) For LCS, single SSTable up-level is handled inefficiently

[ https://issues.apache.org/jira/browse/CASSANDRA-12526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517281#comment-16517281 ] Alex Petrov commented on CASSANDRA-12526: - Committed with

cassandra git commit: Bump SSTable level instead of rewriting SSTable completely during single-sstable compactions

Repository: cassandra Updated Branches: refs/heads/trunk d52bdaefd -> 53c0ef171 Bump SSTable level instead of rewriting SSTable completely during single-sstable compactions Patch by Marcus Eriksson, reviewed by Alex Petrov for CASSANDRA-12526 Project:

[jira] [Updated] (CASSANDRA-14388) Fix setting min/max compaction threshold with LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Petrov updated CASSANDRA-14388: Resolution: Fixed Status: Resolved (was: Patch Available) > Fix setting

[jira] [Comment Edited] (CASSANDRA-14388) Fix setting min/max compaction threshold with LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517264#comment-16517264 ] Alex Petrov edited comment on CASSANDRA-14388 at 6/19/18 4:04 PM: --

[jira] [Commented] (CASSANDRA-14388) Fix setting min/max compaction threshold with LCS

[ https://issues.apache.org/jira/browse/CASSANDRA-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517264#comment-16517264 ] Alex Petrov commented on CASSANDRA-14388: - Committed as

cassandra git commit: Make it possible to set the max/min compaction thresholds

Repository: cassandra Updated Branches: refs/heads/trunk c6570fac1 -> d52bdaefd Make it possible to set the max/min compaction thresholds Patch by Marcus Eriksson, reviewed by Alex Petrov for CASSANDRA-14388 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit:

[jira] [Updated] (CASSANDRA-14530) Unable to start repair process

[ https://issues.apache.org/jira/browse/CASSANDRA-14530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ALEXEY KASHINTSEV updated CASSANDRA-14530: -- Environment: Description: Debian GNU/Linux 8.5 (jessie) Codename: jessie

[jira] [Updated] (CASSANDRA-14530) Unable to start repair process

[ https://issues.apache.org/jira/browse/CASSANDRA-14530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ALEXEY KASHINTSEV updated CASSANDRA-14530: -- Component/s: Repair Core > Unable to start repair

[jira] [Updated] (CASSANDRA-14530) Unable to start repair process

[ https://issues.apache.org/jira/browse/CASSANDRA-14530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ALEXEY KASHINTSEV updated CASSANDRA-14530: -- Priority: Blocker (was: Major) > Unable to start repair process >

[jira] [Created] (CASSANDRA-14530) Unable to start repair process

ALEXEY KASHINTSEV created CASSANDRA-14530: - Summary: Unable to start repair process Key: CASSANDRA-14530 URL: https://issues.apache.org/jira/browse/CASSANDRA-14530 Project: Cassandra

[jira] [Commented] (CASSANDRA-14423) SSTables stop being compacted

[ https://issues.apache.org/jira/browse/CASSANDRA-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517011#comment-16517011 ] Kurt Greaves commented on CASSANDRA-14423: -- OK. I've updated all 3 branches to use

[jira] [Commented] (CASSANDRA-14344) Support filtering using IN restrictions

[ https://issues.apache.org/jira/browse/CASSANDRA-14344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516774#comment-16516774 ] Benjamin Lerer commented on CASSANDRA-14344: {quote}I agree with the comment "approach