You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (Jira)" <ji...@apache.org> on 2021/09/08 06:52:00 UTC
[jira] [Comment Edited] (CASSANDRA-16886) Reduce
native_transport_max_frame_size_in_mb
[ https://issues.apache.org/jira/browse/CASSANDRA-16886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411413#comment-17411413 ]
Benjamin Lerer edited comment on CASSANDRA-16886 at 9/8/21, 6:51 AM:
---------------------------------------------------------------------
{quote}I can switch to ByteUnit here if you prefer{quote}
Yes, I would prefer. Thanks :-)
was (Author: blerer):
{quote}I can switch to ByteUnit here if you prefer{quote}
Yes, it would prefer. Thanks :-)
> Reduce native_transport_max_frame_size_in_mb
> --------------------------------------------
>
> Key: CASSANDRA-16886
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16886
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Client
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
>
> There is really no point in having this set to 256MB when the commitlog segment size defaults to 32MB, effectively capping the largest insertable mutation to 16MB.
> The native transport can provide a good first line of defense against large mutations that would otherwise hit the heap if left to be rejected by the commitlog.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org