[jira] [Commented] (CASSANDRA-17116) When zero-copy-streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438467#comment-17438467 ] David Capwell commented on CASSANDRA-17116: --- patch breaks streaming in python dtest; nice!

[jira] [Commented] (CASSANDRA-17116) When zero-copy-streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438345#comment-17438345 ] David Capwell commented on CASSANDRA-17116: --- To show that the test actually detects the

[jira] [Updated] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

[ https://issues.apache.org/jira/browse/CASSANDRA-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17118: -- Fix Version/s: (was: 4.x) NA Since

[jira] [Updated] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

[ https://issues.apache.org/jira/browse/CASSANDRA-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17118: -- Status: Ready to Commit (was: Review In Progress) > coordinator_large_read

[jira] [Updated] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

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

[cassandra] branch trunk updated: coordinator_read_size had wrong name in cassandra.yaml

This is an automated email from the ASF dual-hosted git repository. dcapwell pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 5b4d369 coordinator_read_size had wrong

[jira] [Commented] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

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

[jira] [Updated] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

[ https://issues.apache.org/jira/browse/CASSANDRA-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17118: Test and Documentation Plan:

[jira] [Commented] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

[ https://issues.apache.org/jira/browse/CASSANDRA-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438319#comment-17438319 ] Ekaterina Dimitrova commented on CASSANDRA-17118: - I think this change requires only

[jira] [Updated] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

[ https://issues.apache.org/jira/browse/CASSANDRA-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17118: Fix Version/s: 4.x > coordinator_large_read should be actually

[jira] [Created] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

Ekaterina Dimitrova created CASSANDRA-17118: --- Summary: coordinator_large_read should be actually coordinator_read_size in cassandra.yaml Key: CASSANDRA-17118 URL:

[jira] [Updated] (CASSANDRA-17118) coordinator_large_read should be actually coordinator_read_size in cassandra.yaml

[ https://issues.apache.org/jira/browse/CASSANDRA-17118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17118: Bug Category: Parent values: Correctness(12982) Complexity:

[jira] [Updated] (CASSANDRA-16957) Actively update auth caches in the background

[ https://issues.apache.org/jira/browse/CASSANDRA-16957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-16957: Reviewers: Caleb Rackliffe Status: Review In Progress (was: Patch

[jira] [Commented] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438311#comment-17438311 ] Doug Rohrer commented on CASSANDRA-17117: - Here are all the workflows in Circle CI - I've

[jira] [Assigned] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer reassigned CASSANDRA-17117: --- Assignee: Sam Tunnicliffe (was: Doug Rohrer) > CQLSSTableWriter backwards

[jira] [Commented] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438305#comment-17438305 ] Brandon Williams commented on CASSANDRA-17117: -- bq. It looks like your 4.0 branch just

[jira] [Commented] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438303#comment-17438303 ] Doug Rohrer commented on CASSANDRA-17117: - Brandon: Thanks for doing that - I do have some

[jira] [Comment Edited] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438296#comment-17438296 ] Brandon Williams edited comment on CASSANDRA-17117 at 11/3/21, 9:18 PM:

[jira] [Commented] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438296#comment-17438296 ] Brandon Williams commented on CASSANDRA-17117: -- Not sure if you planned to add circle

[jira] [Updated] (CASSANDRASC-32) Sidecar health checks are failing since CassandraAdaptorDelegate is not started

[ https://issues.apache.org/jira/browse/CASSANDRASC-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-32: - Authors: Saranya Krishnakumar Fix Version/s: 1.0 Source Control

[jira] [Commented] (CASSANDRASC-32) Sidecar health checks are failing since CassandraAdaptorDelegate is not started

[ https://issues.apache.org/jira/browse/CASSANDRASC-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438292#comment-17438292 ] ASF subversion and git services commented on CASSANDRASC-32: Commit

[cassandra-sidecar] branch trunk updated (4d88af6 -> 01d8b9c)

This is an automated email from the ASF dual-hosted git repository. ycai pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-sidecar.git. from 4d88af6 Avoid having sidecar's health response code depend on Cassandra's health information add

[jira] [Updated] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-17117: Test and Documentation Plan: Patches for 4.0 and trunk are attached - added an

[jira] [Assigned] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer reassigned CASSANDRA-17117: --- Assignee: Doug Rohrer > CQLSSTableWriter backwards compatibility fix for Date

[jira] [Updated] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-17117: Attachment: CASSANDRA-17117-trunk.patch > CQLSSTableWriter backwards compatibility

[jira] [Updated] (CASSANDRA-17116) When zero-copy-streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-17116: - Reviewers: Dinesh Joshi > When zero-copy-streaming sees a channel close this

[jira] [Updated] (CASSANDRA-17116) When zero-copy-streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17116: -- Summary: When zero-copy-streaming sees a channel close this triggers the disk

[jira] [Updated] (CASSANDRA-17116) When streaming sees a channel close this triggers the disk failure policy

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

[jira] [Updated] (CASSANDRA-17116) When streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17116: -- Summary: When streaming sees a channel close this triggers the disk failure

[jira] [Updated] (CASSANDRA-17085) commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

[ https://issues.apache.org/jira/browse/CASSANDRA-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-17085: -- Fix Version/s: (was: 4.x) 4.1 Since

[cassandra] branch trunk updated: commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

This is an automated email from the ASF dual-hosted git repository. dcapwell pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 111e94a commit log was switched from

[jira] [Commented] (CASSANDRA-17085) commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

[ https://issues.apache.org/jira/browse/CASSANDRA-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438252#comment-17438252 ] David Capwell commented on CASSANDRA-17085: --- Starting commit CI Results (pending):

[jira] [Comment Edited] (CASSANDRA-17031) Add support for PEM based key material for SSL

[ https://issues.apache.org/jira/browse/CASSANDRA-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438249#comment-17438249 ] Stefan Miklosovic edited comment on CASSANDRA-17031 at 11/3/21, 6:57 PM:

[jira] [Commented] (CASSANDRA-17031) Add support for PEM based key material for SSL

[ https://issues.apache.org/jira/browse/CASSANDRA-17031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438249#comment-17438249 ] Stefan Miklosovic commented on CASSANDRA-17031: --- I will do it on this Friday. > Add

[jira] [Comment Edited] (CASSANDRA-16349) SSTableLoader reports error when SSTable(s) do not have data for some nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438234#comment-17438234 ] Ekaterina Dimitrova edited comment on CASSANDRA-16349 at 11/3/21, 6:23 PM:

[jira] [Commented] (CASSANDRA-16349) SSTableLoader reports error when SSTable(s) do not have data for some nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438234#comment-17438234 ] Ekaterina Dimitrova commented on CASSANDRA-16349: - [~Ge] I already rebased and

[jira] [Commented] (CASSANDRA-16349) SSTableLoader reports error when SSTable(s) do not have data for some nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438226#comment-17438226 ] Aleksandr Sorokoumov commented on CASSANDRA-16349: -- Thank you for the review and

[jira] [Updated] (CASSANDRA-17085) commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

[ https://issues.apache.org/jira/browse/CASSANDRA-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-17085: -- Attachment: (was: 4.0_iwork_p97.html) > commit log was switched from

[jira] [Updated] (CASSANDRA-17085) commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

[ https://issues.apache.org/jira/browse/CASSANDRA-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie updated CASSANDRA-17085: -- Attachment: 4.0_iwork_p97.html > commit log was switched from non-daemon to

[jira] [Updated] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-17117: Attachment: CASSANDRA-17117-4.0.patch > CQLSSTableWriter backwards compatibility fix

[jira] [Commented] (CASSANDRA-17116) When zero-copy-streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438213#comment-17438213 ] David Capwell commented on CASSANDRA-17116: --- have a patch which replicates the problem and

[jira] [Assigned] (CASSANDRA-17116) When zero-copy-streaming sees a channel close this triggers the disk failure policy

[ https://issues.apache.org/jira/browse/CASSANDRA-17116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell reassigned CASSANDRA-17116: - Assignee: David Capwell > When zero-copy-streaming sees a channel close

[jira] [Commented] (CASSANDRA-17070) ViewComplexTest hardening

[ https://issues.apache.org/jira/browse/CASSANDRA-17070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438204#comment-17438204 ] Andres de la Peña commented on CASSANDRA-17070: --- The PR for trunk looks good to me.

[jira] [Updated] (CASSANDRA-17085) commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

[ https://issues.apache.org/jira/browse/CASSANDRA-17085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-17085: Status: Ready to Commit (was: Review In Progress) +1 LGTM > commit log was

[jira] [Updated] (CASSANDRA-17085) commit log was switched from non-daemon to daemon threads, which causes the JVM to exit in some case as no non-daemon threads are active

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

[jira] [Commented] (CASSANDRA-16349) SSTableLoader reports error when SSTable(s) do not have data for some nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438188#comment-17438188 ] Ekaterina Dimitrova commented on CASSANDRA-16349: -

[jira] [Assigned] (CASSANDRA-14466) Enable Direct I/O

[ https://issues.apache.org/jira/browse/CASSANDRA-14466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mulugeta Mammo reassigned CASSANDRA-14466: -- Assignee: (was: Mulugeta Mammo) > Enable Direct I/O >

[jira] [Comment Edited] (CASSANDRA-16349) SSTableLoader reports error when SSTable(s) do not have data for some nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437675#comment-17437675 ] Ekaterina Dimitrova edited comment on CASSANDRA-16349 at 11/3/21, 3:47 PM:

[jira] [Updated] (CASSANDRA-16349) SSTableLoader reports error when SSTable(s) do not have data for some nodes

[ https://issues.apache.org/jira/browse/CASSANDRA-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-16349: Fix Version/s: 4.x > SSTableLoader reports error when SSTable(s) do

[jira] [Updated] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

[ https://issues.apache.org/jira/browse/CASSANDRA-17117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-17117: - Bug Category: Parent values: Code(13163) Complexity: Normal

[jira] [Created] (CASSANDRA-17117) CQLSSTableWriter backwards compatibility fix for Date fields

Doug Rohrer created CASSANDRA-17117: --- Summary: CQLSSTableWriter backwards compatibility fix for Date fields Key: CASSANDRA-17117 URL: https://issues.apache.org/jira/browse/CASSANDRA-17117 Project:

[jira] [Updated] (CASSANDRA-16801) PasswordObfuscator should not assume PASSWORD is the last item in the WITH clause

[ https://issues.apache.org/jira/browse/CASSANDRA-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-16801: --- Status: Review In Progress (was: Needs Committer) > PasswordObfuscator should

[jira] [Commented] (CASSANDRA-17073) The initial endpoint state is not propagated to all registered listeners in Gossiper

[ https://issues.apache.org/jira/browse/CASSANDRA-17073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17438048#comment-17438048 ] Jacek Lewandowski commented on CASSANDRA-17073: --- I've implemented a failing test here

[jira] [Commented] (CASSANDRA-17070) ViewComplexTest hardening

[ https://issues.apache.org/jira/browse/CASSANDRA-17070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437991#comment-17437991 ] Berenguer Blasi commented on CASSANDRA-17070: - I added the trunk PR with CI. There's no

[jira] [Updated] (CASSANDRA-16801) PasswordObfuscator should not assume PASSWORD is the last item in the WITH clause

[ https://issues.apache.org/jira/browse/CASSANDRA-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Lerer updated CASSANDRA-16801: --- Reviewers: Benjamin Lerer, Ekaterina Dimitrova > PasswordObfuscator should not

[jira] [Updated] (CASSANDRA-17074) Remove custom Duration object and refactor its usages to use Duration from Java

[ https://issues.apache.org/jira/browse/CASSANDRA-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-17074: -- Fix Version/s: (was: 4.1) > Remove custom Duration object and

[jira] [Updated] (CASSANDRA-17074) Remove custom Duration object and refactor its usages to use Duration from Java

[ https://issues.apache.org/jira/browse/CASSANDRA-17074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-17074: -- Resolution: Duplicate Status: Resolved (was: Open) > Remove

[jira] [Commented] (CASSANDRA-16801) PasswordObfuscator should not assume PASSWORD is the last item in the WITH clause

[ https://issues.apache.org/jira/browse/CASSANDRA-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437749#comment-17437749 ] Berenguer Blasi commented on CASSANDRA-16801: - bq. Seems to me you actually fall back to