[
https://issues.apache.org/jira/browse/HBASE-29179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-29179.
----------------------------------
Release Note: The client will now by default use the value of
hbase.rpc.rows.size.threshold.reject when
hbase.client.write.buffer.maxmutations is unset.
Resolution: Fixed
Committed to branch-2+. Thanks for the addendum [~charlesconnell]!
> Fall back to hbase.rpc.rows.warning.threshold if
> hbase.client.write.buffer.maxmutations is not set
> --------------------------------------------------------------------------------------------------
>
> Key: HBASE-29179
> URL: https://issues.apache.org/jira/browse/HBASE-29179
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Nick Dimiduk
> Assignee: Charles Connell
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2
>
>
> HBASE-29148 introduced a nice client-side configuration for allowing the
> BufferedMutator to play nicer in the face of
> {{hbase.rpc.rows.size.threshold.reject}}. It's up to the operator to
> configure the setting themselves. Let's add some smarter default logic that
> will automatically configure the client according to the server's setting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
