Change of recv_n_pool_free_frames default value in InnoDB patches has no effect

Bug #788070 reported by Alexey Kopytov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Fix Released
Medium
Unassigned
1.6
Won't Fix
Medium
Unassigned
2.0
Won't Fix
Undecided
Unassigned
2.1
Won't Fix
Undecided
Unassigned
2.2
Fix Released
Medium
Unassigned

Bug Description

In innodb51.patch and innodb51_builtin.patch we try to raise the default value of recv_n_pool_free_frames from 256 to 1024. I think it doesn't work as intended due to the following code in recv_sys_init():

 /* Set appropriate value of recv_n_pool_free_frames. */
 if (buf_pool_get_curr_size() >= (10 * 1024 * 1024)) {
  /* Buffer pool of size greater than 10 MB. */
  recv_n_pool_free_frames = 512;
 }

So if the buffer pool is larger than 10 MB (which is always the case these days) it is "adjusted" to 512, which in case of XtraBackup is actually lower than the re-defined default.

Tags: cr i16386
Changed in percona-xtrabackup:
status: New → Confirmed
tags: added: cr i16386
Stewart Smith (stewart)
Changed in percona-xtrabackup:
importance: Undecided → High
status: Confirmed → Triaged
Stewart Smith (stewart)
Changed in percona-xtrabackup:
importance: High → Medium
Revision history for this message
Alexey Kopytov (akopytov) wrote :

This was actually fixed as a part of the single binary refactoring in 2.2.1-alpha1.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-66

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.