[jira] [Created] (CASSANDRA-15330) When repair fails during validation or sync, local metadata does not get freed

David Capwell created CASSANDRA-15330: - Summary: When repair fails during validation or sync, local metadata does not get freed Key: CASSANDRA-15330 URL: https://issues.apache.org/jira/browse/CASSANDRA-15330

[jira] [Commented] (CASSANDRA-15330) When repair fails during validation or sync, local metadata does not get freed

[ https://issues.apache.org/jira/browse/CASSANDRA-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934864#comment-16934864 ] David Capwell commented on CASSANDRA-15330: --- Found using in-JVM dtest; test can be found

[jira] [Updated] (CASSANDRA-15330) When repair fails during validation or sync, local metadata does not get freed

[ https://issues.apache.org/jira/browse/CASSANDRA-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15330: -- Description: If repair fails during validation or sync phase, the local (per

[jira] [Commented] (CASSANDRA-15331) When streaming tries to open a file and gets a exception it re-throws as a normal runtime exception

[ https://issues.apache.org/jira/browse/CASSANDRA-15331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934871#comment-16934871 ] David Capwell commented on CASSANDRA-15331: --- Found with the following in-JVM dtest: 

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934870#comment-16934870 ] David Capwell commented on CASSANDRA-15332: --- Found with the following in-JVM dtest: 

[jira] [Updated] (CASSANDRA-15330) When repair fails during validation or sync, local metadata does not get freed

[ https://issues.apache.org/jira/browse/CASSANDRA-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15330: -- Component/s: (was: Consistency/Coordination)

[jira] [Created] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

David Capwell created CASSANDRA-15332: - Summary: When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied Key: CASSANDRA-15332 URL:

[jira] [Created] (CASSANDRA-15331) When streaming tries to open a file and gets a exception it re-throws as a normal runtime exception

David Capwell created CASSANDRA-15331: - Summary: When streaming tries to open a file and gets a exception it re-throws as a normal runtime exception Key: CASSANDRA-15331 URL:

[jira] [Commented] (CASSANDRA-15330) When repair fails during validation or sync, local metadata does not get freed

[ https://issues.apache.org/jira/browse/CASSANDRA-15330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16934862#comment-16934862 ] David Capwell commented on CASSANDRA-15330: --- If RepairParallelism.PARALLEL is used, then

[jira] [Updated] (CASSANDRA-15329) in-JVM dtest fails on java 11 since system ClassLoader is not a URLClassLoader

[ https://issues.apache.org/jira/browse/CASSANDRA-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15329: -- Attachment: CASSANDRA-15329.patch > in-JVM dtest fails on java 11 since system

[jira] [Created] (CASSANDRA-15329) in-JVM dtest fails on java 11 since system ClassLoader is not a URLClassLoader

David Capwell created CASSANDRA-15329: - Summary: in-JVM dtest fails on java 11 since system ClassLoader is not a URLClassLoader Key: CASSANDRA-15329 URL: https://issues.apache.org/jira/browse/CASSANDRA-15329

[jira] [Commented] (CASSANDRA-15329) in-JVM dtest fails on java 11 since system ClassLoader is not a URLClassLoader

[ https://issues.apache.org/jira/browse/CASSANDRA-15329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938812#comment-16938812 ] David Capwell commented on CASSANDRA-15329: --- Moved patch to GitHub, can be found

[jira] [Created] (CASSANDRA-15338) Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest

David Capwell created CASSANDRA-15338: - Summary: Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest Key: CASSANDRA-15338 URL: https://issues.apache.org/jira/browse/CASSANDRA-15338

[jira] [Updated] (CASSANDRA-15338) Fix flakey testMessagePurging - org.apache.cassandra.net.ConnectionTest

[ https://issues.apache.org/jira/browse/CASSANDRA-15338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15338: -- Description: Example failure: 

[jira] [Updated] (CASSANDRA-15399) Add ability to track state in repair

[ https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15399: -- Change Category: Operability Complexity: Normal Status: Open

[jira] [Created] (CASSANDRA-15399) Add ability to track state in repair

David Capwell created CASSANDRA-15399: - Summary: Add ability to track state in repair Key: CASSANDRA-15399 URL: https://issues.apache.org/jira/browse/CASSANDRA-15399 Project: Cassandra

[jira] [Commented] (CASSANDRA-15406) Add command to show the progress of data streaming and index build

[ https://issues.apache.org/jira/browse/CASSANDRA-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16971805#comment-16971805 ] David Capwell commented on CASSANDRA-15406: --- Linked with CASSANDRA-15399 since repair

[jira] [Commented] (CASSANDRA-15399) Add ability to track state in repair

[ https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969477#comment-16969477 ] David Capwell commented on CASSANDRA-15399: --- I created a PR to get early feedback, but the

[jira] [Commented] (CASSANDRA-15332) When repair is running with tracing, if a CorruptSSTableException is thrown while building Merkle Trees the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963240#comment-16963240 ] David Capwell commented on CASSANDRA-15332: --- [~marcuse] I pushed all changes based off

[jira] [Commented] (CASSANDRA-15332) When repair is running with tracing, if a CorruptSSTableException is thrown while building Merkle Trees the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973766#comment-16973766 ] David Capwell commented on CASSANDRA-15332: --- thanks! [~marcuse] everything good then?

[jira] [Updated] (CASSANDRA-15399) Add ability to track state in repair

[ https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15399: -- Description: To enhance the visibility in repair, we should expose internal state

[jira] [Created] (CASSANDRA-15431) add table options required_ttl and max_ttl

David Capwell created CASSANDRA-15431: - Summary: add table options required_ttl and max_ttl Key: CASSANDRA-15431 URL: https://issues.apache.org/jira/browse/CASSANDRA-15431 Project: Cassandra

[jira] [Commented] (CASSANDRA-15160) Add flag to ignore unreplicated keyspaces during repair

[ https://issues.apache.org/jira/browse/CASSANDRA-15160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16988362#comment-16988362 ] David Capwell commented on CASSANDRA-15160: --- Interesting that the test was success and

[jira] [Commented] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990226#comment-16990226 ] David Capwell commented on CASSANDRA-15444: --- I have to delete all {code}bti{code} files

[jira] [Commented] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990231#comment-16990231 ] David Capwell commented on CASSANDRA-15444: --- There are a few other codepaths I found which

[jira] [Commented] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990261#comment-16990261 ] David Capwell commented on CASSANDRA-15444: --- I have this working, but its getting ugly.

[jira] [Commented] (CASSANDRA-15429) Support NodeTool for in-jvm dtest

[ https://issues.apache.org/jira/browse/CASSANDRA-15429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993122#comment-16993122 ] David Capwell commented on CASSANDRA-15429: --- LGTM +1 > Support NodeTool for in-jvm dtest

[jira] [Commented] (CASSANDRA-15429) Support NodeTool for in-jvm dtest

[ https://issues.apache.org/jira/browse/CASSANDRA-15429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993049#comment-16993049 ] David Capwell commented on CASSANDRA-15429: --- Did another pass. Mostly LGTM; left a few

[jira] [Commented] (CASSANDRA-15446) Per-thread stack size is too small on aarch64 CentOS

[ https://issues.apache.org/jira/browse/CASSANDRA-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16993673#comment-16993673 ] David Capwell commented on CASSANDRA-15446: --- Thanks for the extra details! > Per-thread

[jira] [Commented] (CASSANDRA-15447) in-jvm dtest support for subnets doesn't change seed provider subnet

[ https://issues.apache.org/jira/browse/CASSANDRA-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994933#comment-16994933 ] David Capwell commented on CASSANDRA-15447: --- I modified

[jira] [Commented] (CASSANDRA-15448) Throttle the speed of merkletree row hash

[ https://issues.apache.org/jira/browse/CASSANDRA-15448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994898#comment-16994898 ] David Capwell commented on CASSANDRA-15448: --- Do you have any profiles/gc logs to show

[jira] [Updated] (CASSANDRA-15446) Per-thread stack size is too small on aarch64 CentOS

[ https://issues.apache.org/jira/browse/CASSANDRA-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15446: -- Platform: Java8,Java11,OpenJDK,Linux,ARM (was: Java8,Java11,OpenJDK,Linux) >

[jira] [Updated] (CASSANDRA-15446) Per-thread stack size is too small on aarch64 CentOS

[ https://issues.apache.org/jira/browse/CASSANDRA-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15446: -- Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear

[jira] [Updated] (CASSANDRA-15447) in-jvm dtest support for subnets doesn't change seed provider subnet

[ https://issues.apache.org/jira/browse/CASSANDRA-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15447: -- Reviewers: David Capwell, Yifan Cai (was: Yifan Cai) > in-jvm dtest support for

[jira] [Created] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

David Capwell created CASSANDRA-15450: - Summary: in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id Key:

[jira] [Updated] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15450: -- Bug Category: Parent values: Code(13163)Level 1 values: Bug - Unclear

[jira] [Updated] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15450: -- Test and Documentation Plan: Patch located here:

[jira] [Updated] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15450: -- Description: In \{code}AbstractCluster.uncaughtExceptions\{code}, we attempt to

[jira] [Updated] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15450: -- Description: In AbstractCluster.uncaughtExceptions, we attempt to get the

[jira] [Commented] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995117#comment-16995117 ] David Capwell commented on CASSANDRA-15450: --- [~drohrer] could you review as you were the

[jira] [Commented] (CASSANDRA-15399) Add ability to track state in repair

[ https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16989145#comment-16989145 ] David Capwell commented on CASSANDRA-15399: --- I put this on hold for now; I will come back

[jira] [Created] (CASSANDRA-15444) On start while loading SSTables into memory, if a unsupported version is found, should fail to start

David Capwell created CASSANDRA-15444: - Summary: On start while loading SSTables into memory, if a unsupported version is found, should fail to start Key: CASSANDRA-15444 URL:

[jira] [Updated] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15444: -- Summary: When using StandaloneUpgrader, loading SSTables into memory should fail

[jira] [Commented] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990182#comment-16990182 ] David Capwell commented on CASSANDRA-15444: --- Reworded to reflect the issue is local to

[jira] [Updated] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15444: -- Description: When using the StandaloneUpgrader, if unsupported SSTables are

[jira] [Updated] (CASSANDRA-15444) When using StandaloneUpgrader, loading SSTables into memory should fail if unsupported version is found

[ https://issues.apache.org/jira/browse/CASSANDRA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15444: -- Change Category: Operability Complexity: Low Hanging Fruit

[jira] [Comment Edited] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance i

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997508#comment-16997508 ] David Capwell edited comment on CASSANDRA-15450 at 12/16/19 6:10 PM:

[jira] [Updated] (CASSANDRA-15452) investigate using POSIX_FADV_WILLNEED on compaction

[ https://issues.apache.org/jira/browse/CASSANDRA-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15452: -- Change Category: Performance Complexity: Normal Component/s:

[jira] [Commented] (CASSANDRA-15451) INFO [CompactionExecutor:8] 2019-12-13 17:49:53,408 NoSpamLogger.java:91 - Maximum memory usage reached (4294967296), cannot allocate chunk of 1048576

[ https://issues.apache.org/jira/browse/CASSANDRA-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997497#comment-16997497 ] David Capwell commented on CASSANDRA-15451: --- The warning is coming from 

[jira] [Commented] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997508#comment-16997508 ] David Capwell commented on CASSANDRA-15450: --- {quote} should we add a test?\{quote}   The

[jira] [Commented] (CASSANDRA-15449) Credentials out of sync after replacing the nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997629#comment-16997629 ] David Capwell commented on CASSANDRA-15449: --- Also, may be good to increase the RF for

[jira] [Commented] (CASSANDRA-15450) in-jvm dtest cluster uncaughtExceptions propagation of exception goes to the wrong instance, it uses cluster generation when it should be using the instance id

[ https://issues.apache.org/jira/browse/CASSANDRA-15450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997633#comment-16997633 ] David Capwell commented on CASSANDRA-15450: --- Will file a Jira to backport > in-jvm dtest

[jira] [Commented] (CASSANDRA-15449) Credentials out of sync after replacing the nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-15449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997560#comment-16997560 ] David Capwell commented on CASSANDRA-15449: --- One thing to call out, it’s a good idea to

[jira] [Updated] (CASSANDRA-15456) Backport CASSANDRA-15332 dtest changes to 3.x

[ https://issues.apache.org/jira/browse/CASSANDRA-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15456: -- Change Category: Quality Assurance Complexity: Low Hanging Fruit

[jira] [Created] (CASSANDRA-15456) Backport CASSANDRA-15332 dtest changes to 3.x

David Capwell created CASSANDRA-15456: - Summary: Backport CASSANDRA-15332 dtest changes to 3.x Key: CASSANDRA-15456 URL: https://issues.apache.org/jira/browse/CASSANDRA-15456 Project: Cassandra

[jira] [Assigned] (CASSANDRA-15456) Backport CASSANDRA-15332 dtest changes to 3.x

[ https://issues.apache.org/jira/browse/CASSANDRA-15456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-15456: - Assignee: David Capwell > Backport CASSANDRA-15332 dtest changes to 3.x >

[jira] [Commented] (CASSANDRA-15446) Per-thread stack size is too small on aarch64 CentOS

[ https://issues.apache.org/jira/browse/CASSANDRA-15446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992744#comment-16992744 ] David Capwell commented on CASSANDRA-15446: --- This looks related to

[jira] [Updated] (CASSANDRA-15429) Support NodeTool for in-jvm dtest

[ https://issues.apache.org/jira/browse/CASSANDRA-15429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15429: -- Reviewers: David Capwell, David Capwell (was: David Capwell) David

[jira] [Commented] (CASSANDRA-15447) in-jvm dtest support for subnets doesn't change seed provider subnet

[ https://issues.apache.org/jira/browse/CASSANDRA-15447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16994126#comment-16994126 ] David Capwell commented on CASSANDRA-15447: --- [~drohrer] can you click “Open” and fill out

[jira] [Commented] (CASSANDRA-15429) Support NodeTool for in-jvm dtest

[ https://issues.apache.org/jira/browse/CASSANDRA-15429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16992882#comment-16992882 ] David Capwell commented on CASSANDRA-15429: --- We should refactor NodeProbe and

[jira] [Commented] (CASSANDRA-15364) Avoid over scanning data directories in LogFile.verify()

[ https://issues.apache.org/jira/browse/CASSANDRA-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16961188#comment-16961188 ] David Capwell commented on CASSANDRA-15364: --- Assert msg looks good to me; loop assumes the

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956123#comment-16956123 ] David Capwell commented on CASSANDRA-15332: --- [~marcuse] I see that for streaming but

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956151#comment-16956151 ] David Capwell commented on CASSANDRA-15332: --- Thanks, I'll try to replicate later. > When

[jira] [Updated] (CASSANDRA-15364) Avoid over scanning data directories in LogFile.verify()

[ https://issues.apache.org/jira/browse/CASSANDRA-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15364: -- Reviewers: David Capwell, David Capwell (was: David Capwell) David

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956480#comment-16956480 ] David Capwell commented on CASSANDRA-15332: --- Synced with [~marcuse] and turns out we are

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956514#comment-16956514 ] David Capwell commented on CASSANDRA-15332: --- [~marcuse] [~jrwest] I pushed a change to my

[jira] [Commented] (CASSANDRA-15332) When repair is running with tracing, if a CorruptSSTableException is thrown while building Merkle Trees the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956517#comment-16956517 ] David Capwell commented on CASSANDRA-15332: --- I updated the Jira title to better reflect

[jira] [Updated] (CASSANDRA-15332) When repair is running with tracing, if a CorruptSSTableException is thrown while building Merkle Trees the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15332: -- Summary: When repair is running with tracing, if a CorruptSSTableException is

[jira] [Updated] (CASSANDRA-15356) CassandraEntireSSTableStreamWriter throws IOException rather than FSError for disk issues so doesn't get handled by disk failing policy

[ https://issues.apache.org/jira/browse/CASSANDRA-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15356: -- Description: Found while testing CASSANDRA-15332 Streaming relies on the

[jira] [Updated] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15332: -- Reviewers: Blake Eggleston, Marcus Eriksson (was: Marcus Eriksson) > When

[jira] [Commented] (CASSANDRA-15356) When streaming throws a FSError the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952172#comment-16952172 ] David Capwell commented on CASSANDRA-15356: --- Changing the description and title. Turns

[jira] [Created] (CASSANDRA-15357) test org.apache.cassandra.config.DatabaseDescriptorRefTest#testDatabaseDescriptorRef constantly failing on trunk

David Capwell created CASSANDRA-15357: - Summary: test org.apache.cassandra.config.DatabaseDescriptorRefTest#testDatabaseDescriptorRef constantly failing on trunk Key: CASSANDRA-15357 URL:

[jira] [Updated] (CASSANDRA-15356) CassandraEntireSSTableStreamWriter throws IOException rather than FSError for disk issues so doesn't get handled by disk failing policy

[ https://issues.apache.org/jira/browse/CASSANDRA-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15356: -- Summary: CassandraEntireSSTableStreamWriter throws IOException rather than

[jira] [Updated] (CASSANDRA-15356) CassandraEntireSSTableStreamWriter throws IOException rather than FSError for disk issues so doesn't get handled by disk failing policy

[ https://issues.apache.org/jira/browse/CASSANDRA-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15356: -- Description: Found while testing CASSANDRA-15332 Streaming relies on the

[jira] [Assigned] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-15332: - Assignee: David Capwell > When building MerkleTrees if a

[jira] [Comment Edited] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951444#comment-16951444 ] David Capwell edited comment on CASSANDRA-15332 at 10/15/19 12:52 AM:

[jira] [Created] (CASSANDRA-15356) When streaming throws a FSError the DiskFailurePolicy does not get applied

David Capwell created CASSANDRA-15356: - Summary: When streaming throws a FSError the DiskFailurePolicy does not get applied Key: CASSANDRA-15356 URL: https://issues.apache.org/jira/browse/CASSANDRA-15356

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951444#comment-16951444 ] David Capwell commented on CASSANDRA-15332: --- Can find my patch here:

[jira] [Commented] (CASSANDRA-15356) When streaming throws a FSError the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951458#comment-16951458 ] David Capwell commented on CASSANDRA-15356: ---

[jira] [Commented] (CASSANDRA-15356) When streaming throws a FSError the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951461#comment-16951461 ] David Capwell commented on CASSANDRA-15356: --- updated tests for 15332 to include streaming

[jira] [Comment Edited] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951444#comment-16951444 ] David Capwell edited comment on CASSANDRA-15332 at 10/15/19 5:29 AM:

[jira] [Comment Edited] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951444#comment-16951444 ] David Capwell edited comment on CASSANDRA-15332 at 10/15/19 5:32 AM:

[jira] [Updated] (CASSANDRA-15332) When repair is running with tracing, if a CorruptSSTableException is thrown while building Merkle Trees the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15332: -- Component/s: Observability/Tracing > When repair is running with tracing, if a

[jira] [Updated] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15332: -- Test and Documentation Plan: ||branch||diff||tests||pr||

[jira] [Updated] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15332: -- Test and Documentation Plan: ||branch||diff||tests||

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953849#comment-16953849 ] David Capwell commented on CASSANDRA-15332: --- {quote} In the uncaught exception handler

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953873#comment-16953873 ] David Capwell commented on CASSANDRA-15332: --- {quote} It would be beneficial for tests to

[jira] [Updated] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15332: -- Test and Documentation Plan: ||branch||diff||tests||

[jira] [Commented] (CASSANDRA-15332) When building MerkleTrees if a CorruptSSTableException is thrown the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953874#comment-16953874 ] David Capwell commented on CASSANDRA-15332: --- [~jrwest] > When building MerkleTrees if a

[jira] [Commented] (CASSANDRA-15332) When repair is running with tracing, if a CorruptSSTableException is thrown while building Merkle Trees the DiskFailurePolicy does not get applied

[ https://issues.apache.org/jira/browse/CASSANDRA-15332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16959982#comment-16959982 ] David Capwell commented on CASSANDRA-15332: --- Found out that my change only got execute to

[jira] [Updated] (CASSANDRA-15295) Running into deadlock when do CommitLog initialization

[ https://issues.apache.org/jira/browse/CASSANDRA-15295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15295: -- Attachment: image.png > Running into deadlock when do CommitLog initialization >

[jira] [Commented] (CASSANDRA-15364) Avoid over scanning data directories in LogFile.verify()

[ https://issues.apache.org/jira/browse/CASSANDRA-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956580#comment-16956580 ] David Capwell commented on CASSANDRA-15364: --- FYI I created a quick JMH to show the

[jira] [Comment Edited] (CASSANDRA-15364) Avoid over scanning data directories in LogFile.verify()

[ https://issues.apache.org/jira/browse/CASSANDRA-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956431#comment-16956431 ] David Capwell edited comment on CASSANDRA-15364 at 10/22/19 1:30 AM:

[jira] [Commented] (CASSANDRA-15364) Avoid over scanning data directories in LogFile.verify()

[ https://issues.apache.org/jira/browse/CASSANDRA-15364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16956588#comment-16956588 ] David Capwell commented on CASSANDRA-15364: --- Ran locally and ran with a debugger to

[jira] [Commented] (CASSANDRA-15399) Add ability to track state in repair

[ https://issues.apache.org/jira/browse/CASSANDRA-15399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16980877#comment-16980877 ] David Capwell commented on CASSANDRA-15399: --- I like the idea of resending, I'll take that

[jira] [Assigned] (CASSANDRA-15357) test org.apache.cassandra.config.DatabaseDescriptorRefTest#testDatabaseDescriptorRef constantly failing on trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-15357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-15357: - Assignee: (was: David Capwell) > test >

[jira] [Assigned] (CASSANDRA-15357) test org.apache.cassandra.config.DatabaseDescriptorRefTest#testDatabaseDescriptorRef constantly failing on trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-15357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-15357: - Assignee: David Capwell > test >

[jira] [Updated] (CASSANDRA-15357) test org.apache.cassandra.config.DatabaseDescriptorRefTest#testDatabaseDescriptorRef constantly failing on trunk

[ https://issues.apache.org/jira/browse/CASSANDRA-15357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15357: -- Bug Category: Parent values: Code(13163) Complexity: Low Hanging Fruit

[jira] [Created] (CASSANDRA-15396) RAR does not override skip or skipBytes so will do a lot of disk io when n is large

David Capwell created CASSANDRA-15396: - Summary: RAR does not override skip or skipBytes so will do a lot of disk io when n is large Key: CASSANDRA-15396 URL:

[jira] [Updated] (CASSANDRA-15396) RAR does not override skip or skipBytes so will do a lot of disk io when n is large

[ https://issues.apache.org/jira/browse/CASSANDRA-15396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-15396: -- Change Category: Performance Complexity: Low Hanging Fruit

  1   2   3   4   5   6   7   8   9   10   >