Patch to remove excessive fcntl() calls was never ported correctly to 5.1
Bug #1061118 reported by
Laurynas Biveinis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Undecided
|
Unassigned | ||
5.1 |
Fix Released
|
Medium
|
Hrvoje Matijakovic | ||
5.5 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This patch -
http://
https:/
has always been a no-op in PS 5.1.
The reason is that the patch works by preprocessor, adding "... && !defined(NO_ALARM) " several times to net_serv.cc to disable the alarm code. But nothing in PS build process or official binary build scripts actually define NO_ALARM, it never gets defined, the alarm code never gets disabled.
Not a bug on PS 5.5, as CMake build sys starts defining NO_ALARM for us.
Related branches
lp:~hrvojem/percona-server/rn-5.1.66-14.1-5.1
- Laurynas Biveinis (community): Needs Fixing
- Stewart Smith (community): Approve
-
Diff: 133 lines (+55/-15)5 files modifieddoc/source/conf.py (+2/-2)
doc/source/index.rst (+1/-1)
doc/source/performance/remove_fcntl_excessive_calls.rst (+15/-11)
doc/source/release-notes/Percona-Server-5.1.65-14.0.rst (+1/-1)
doc/source/release-notes/Percona-Server-5.1.66-14.1.rst (+36/-0)
To post a comment you must log in.
I'm more in favor of keeping the status quo and just fixing the docs to remove the feature, because:
1. Even though the patch was there, the feature was never enabled in our official 5.1 binaries bugs.mysql. com/bug. php?id= 52633, or (if the fix is backported) to an unconditional change from the documented behavior in net_read_ timeout/ net_write_ timeout/ net_retry_ count in upstream 5.1.
2. Enabling the feature in our 5.1 binaries would lead to either http://
Either outcome doesn't look good to me. Let's change it to a doc bug?