[jira] [Updated] (CASSANDRA-18026) Operability improvements around internode_max_message_size[_in_bytes] in 4.0+

["Caleb Rackliffe (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-18026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Caleb Rackliffe updated CASSANDRA-18026:
----------------------------------------
    Change Category: Operability
         Complexity: Normal
        Component/s: Documentation/NEWS.txt
                     Local/Config
                     Messaging/Internode
      Fix Version/s: 4.0.x
                     4.1.x
                     4.x
             Status: Open  (was: Triage Needed)

> Operability improvements around internode_max_message_size[_in_bytes] in 4.0+
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18026
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18026
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation/NEWS.txt, Local/Config, Messaging/Internode
>            Reporter: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 4.x
>
>
> There are a few things we could do to make {{internode_max_message_size}} (formerly {{internode_max_message_size_in_bytes}}) a bit more friendly:
> 1.) If a read fails because of an {{OversizedMessageException}}, it would be nice to emit a client warning. Currently the client gets a {{ReadFailureException}}, surfaced as something like this:
> {noformat}
> msg="Cassandra failure during read query at consistency QUORUM (3 responses were required but only 0 replica responded, 2 failed)"
> query="SELECT key, column1, value FROM ks.tbl WHERE key=? AND column1>? AND column1<=? LIMIT 256;"
> stackTrace="com.datastax.driver.core.exceptions.ReadFailureException: Cassandra failure during read query at consistency QUORUM (3 responses were required but only 0 replica responded, 2 failed)
> {noformat}
> 2.) We should add an entry in {{NEWS.txt}} to indicate the possible impact of {{internode_max_message_size_in_bytes}} when upgrading to 4.0+.
> 3.) {{internode_max_message_size_in_bytes}} / {{internode_max_message_size}} should be settable at runtime via JMX/vtable/etc.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org