diff options
author | Daniele Sciascia <daniele.sciascia@galeracluster.com> | 2016-05-06 16:07:53 +0200 |
---|---|---|
committer | Nirbhay Choubey <nirbhay@mariadb.com> | 2016-07-25 11:44:57 -0400 |
commit | 74f80b349924c7f0c091a0973dea0ec61191c2c9 (patch) | |
tree | c6d0265edd1470a850c70eda77f773ea315ca85b /sql/wsrep_applier.cc | |
parent | 5197fcf6b4611a26b3847d1101f1a4fb6d17570a (diff) | |
download | mariadb-git-74f80b349924c7f0c091a0973dea0ec61191c2c9.tar.gz |
MW-267 Enforce wsrep_max_ws_size limit in wsrep provider
This changes variable wsrep_max_ws_size so that its value
is linked to the value of provider option repl.max_ws_size.
That is, changing the value of variable wsrep_max_ws_size
will change the value of provider option repl.max_ws_size,
and viceversa.
The writeset size limit is always enforced in the provider,
regardless of which option is used.
Diffstat (limited to 'sql/wsrep_applier.cc')
-rw-r--r-- | sql/wsrep_applier.cc | 10 |
1 files changed, 2 insertions, 8 deletions
diff --git a/sql/wsrep_applier.cc b/sql/wsrep_applier.cc index 90c84f1c2cc..73a43185162 100644 --- a/sql/wsrep_applier.cc +++ b/sql/wsrep_applier.cc @@ -39,15 +39,9 @@ static Log_event* wsrep_read_log_event( const char *error= 0; Log_event *res= 0; - if (data_len > wsrep_max_ws_size) - { - error = "Event too big"; - goto err; - } - - res= Log_event::read_log_event(buf, data_len, &error, description_event, true); + res= Log_event::read_log_event(buf, data_len, &error, description_event, + true); -err: if (!res) { DBUG_ASSERT(error != 0); |