[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868329#comment-17868329 ] Dmitry Konstantinov commented on CASSANDRA-19651: - Here they are: *

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868318#comment-17868318 ] Dmitry Konstantinov commented on CASSANDRA-19651: - Hi Ariel, sorry for the delay. I

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867409#comment-17867409 ] Dmitry Konstantinov commented on CASSANDRA-19651: - Yes, I suppose due to randomness

[jira] [Comment Edited] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866456#comment-17866456 ] Dmitry Konstantinov edited comment on CASSANDRA-19651 at 7/16/24 4:03 PM:

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866456#comment-17866456 ] Dmitry Konstantinov commented on CASSANDRA-19651: - Yes, the attached patch was an

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Attachment: (was: 19651-4.1.patch) > idealCLWriteLatency metric

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864967#comment-17864967 ] Dmitry Konstantinov commented on CASSANDRA-19651: - Thank you! > idealCLWriteLatency

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Test and Documentation Plan: an existing unit test is updated and 2

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17861253#comment-17861253 ] Dmitry Konstantinov commented on CASSANDRA-19651: - The fixed version for 4.1 branch:

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860869#comment-17860869 ] Dmitry Konstantinov commented on CASSANDRA-19557: - Created: CASSANDRA-19652 >

[jira] [Comment Edited] (CASSANDRA-19652) ShallowInfoRetriever: cache offsets to void resetting of RandomAccessReader buffer

[ https://issues.apache.org/jira/browse/CASSANDRA-19652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860868#comment-17860868 ] Dmitry Konstantinov edited comment on CASSANDRA-19652 at 6/28/24 5:04 PM:

[jira] [Commented] (CASSANDRA-19652) ShallowInfoRetriever: cache offsets to void resetting of RandomAccessReader buffer

[ https://issues.apache.org/jira/browse/CASSANDRA-19652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860868#comment-17860868 ] Dmitry Konstantinov commented on CASSANDRA-19652: - The initial version of the

[jira] [Comment Edited] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849025#comment-17849025 ] Dmitry Konstantinov edited comment on CASSANDRA-19651 at 5/23/24 4:05 PM:

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17849025#comment-17849025 ] Dmitry Konstantinov commented on CASSANDRA-19651: - I have found one more place in

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Status: In Progress (was: Patch Available) > idealCLWriteLatency

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Test and Documentation Plan: a unit test is updated to cover the

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Since Version: 4.0 (was: 4.1.0) > idealCLWriteLatency metric reports

[jira] [Assigned] (CASSANDRA-19652) ShallowInfoRetriever: cache offsets to void resetting of RandomAccessReader buffer

[ https://issues.apache.org/jira/browse/CASSANDRA-19652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov reassigned CASSANDRA-19652: --- Assignee: Dmitry Konstantinov > ShallowInfoRetriever: cache

[jira] [Updated] (CASSANDRA-19652) ShallowInfoRetriever: cache offsets to void resetting of RandomAccessReader buffer

[ https://issues.apache.org/jira/browse/CASSANDRA-19652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19652: Fix Version/s: 5.x > ShallowInfoRetriever: cache offsets to void

[jira] [Created] (CASSANDRA-19652) ShallowInfoRetriever: cache offsets to void resetting of RandomAccessReader buffer

Dmitry Konstantinov created CASSANDRA-19652: --- Summary: ShallowInfoRetriever: cache offsets to void resetting of RandomAccessReader buffer Key: CASSANDRA-19652 URL:

[jira] [Assigned] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov reassigned CASSANDRA-19651: --- Assignee: Dmitry Konstantinov > idealCLWriteLatency metric

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Description:

[jira] [Comment Edited] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848235#comment-17848235 ] Dmitry Konstantinov edited comment on CASSANDRA-19651 at 5/21/24 2:56 PM:

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Attachment: 19651-4.1.patch > idealCLWriteLatency metric reports the

[jira] [Commented] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848235#comment-17848235 ] Dmitry Konstantinov commented on CASSANDRA-19651: - I am going to attach a patch with

[jira] [Updated] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

[ https://issues.apache.org/jira/browse/CASSANDRA-19651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19651: Discovered By: User Report Since Version: 4.1.0 >

[jira] [Created] (CASSANDRA-19651) idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied

Dmitry Konstantinov created CASSANDRA-19651: --- Summary: idealCLWriteLatency metric reports the worst response time instead of the time when ideal CL is satisfied Key: CASSANDRA-19651 URL:

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846100#comment-17846100 ] Dmitry Konstantinov commented on CASSANDRA-19557: - Agree, the last item may depend

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846086#comment-17846086 ] Dmitry Konstantinov commented on CASSANDRA-19557: - Hi Caleb, yes, I thought about

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844453#comment-17844453 ] Dmitry Konstantinov commented on CASSANDRA-19557: - Thank you for your support! >

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843040#comment-17843040 ] Dmitry Konstantinov commented on CASSANDRA-19557: - [~brandon.williams]  could you

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17840593#comment-17840593 ] Dmitry Konstantinov commented on CASSANDRA-19557: - I have built the current trunk

[jira] [Updated] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19557: Attachment: 19557-5.0.patch > ShallowIndexedEntry scenario: the same

[jira] [Comment Edited] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838765#comment-17838765 ] Dmitry Konstantinov edited comment on CASSANDRA-19557 at 4/18/24 6:29 PM:

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838765#comment-17838765 ] Dmitry Konstantinov commented on CASSANDRA-19557: - I see 3 errors in the test report

[jira] [Commented] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836734#comment-17836734 ] Dmitry Konstantinov commented on CASSANDRA-19557: - Hi Brandon, thank you for the

[jira] [Updated] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19557: Description: When we read rows from a large partition stored in an

[jira] [Updated] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19557: Attachment: 19557-4.1.patch > ShallowIndexedEntry scenario: the same

[jira] [Updated] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

[ https://issues.apache.org/jira/browse/CASSANDRA-19557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-19557: Bug Category: Parent values: Degradation(12984)Level 1 values:

[jira] [Created] (CASSANDRA-19557) ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row

Dmitry Konstantinov created CASSANDRA-19557: --- Summary: ShallowIndexedEntry scenario: the same IndexInfo is read multiple times, per every read row Key: CASSANDRA-19557 URL:

[jira] [Comment Edited] (CASSANDRA-19509) Consider using XOR filters instead of bloom filters

[ https://issues.apache.org/jira/browse/CASSANDRA-19509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832799#comment-17832799 ] Dmitry Konstantinov edited comment on CASSANDRA-19509 at 4/1/24 9:57 AM:

[jira] [Commented] (CASSANDRA-19509) Consider using XOR filters instead of bloom filters

[ https://issues.apache.org/jira/browse/CASSANDRA-19509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832799#comment-17832799 ] Dmitry Konstantinov commented on CASSANDRA-19509: - As I got XOR filters consume more

[jira] [Commented] (CASSANDRA-16531) cqlsh can stuck randomly during a connect-timeout period in Kubernetes

[ https://issues.apache.org/jira/browse/CASSANDRA-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306888#comment-17306888 ] Dmitry Konstantinov commented on CASSANDRA-16531: - Yes, I have created it:

[jira] [Updated] (CASSANDRA-16531) cqlsh can stuck randomly during a connect-timeout period in Kubernetes

[ https://issues.apache.org/jira/browse/CASSANDRA-16531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-16531: Since Version: 3.11.5 > cqlsh can stuck randomly during a

[jira] [Created] (CASSANDRA-16531) cqlsh can stuck randomly during a connect-timeout period in Kubernetes

Dmitry Konstantinov created CASSANDRA-16531: --- Summary: cqlsh can stuck randomly during a connect-timeout period in Kubernetes Key: CASSANDRA-16531 URL:

[jira] [Assigned] (CASSANDRA-9749) CommitLogReplayer continues startup after encountering errors

[ https://issues.apache.org/jira/browse/CASSANDRA-9749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov reassigned CASSANDRA-9749: -- Assignee: Dmitry Konstantinov (was: Branimir Lambov) >

[jira] [Updated] (CASSANDRA-14633) Update trunk's netty to 4.1.28

[ https://issues.apache.org/jira/browse/CASSANDRA-14633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Konstantinov updated CASSANDRA-14633: Summary: Update trunk's netty to 4.1.28 (was: Update trunk's netty to